Jump to content

Swayl

Member
  • Posts

    121
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Swayl

  1. @8yf, If you're gonna make an RPG server, you're gonna need a massive amount of staff to look over the server (unless it doesn't have much of a playerbase)... But still, you have to require something before applying, Maybe like 3 hours of playtime, or a mic (for interview). Either way, Goodluck.
  2. Swayl

    Story

    But the turtle already had a spy, and so he already knew, so
  3. Swayl

    Making scripts

    Wouldn't that need skVault, if I'm correct?
  4. I am actually having a hard time choose on this
  5. Swayl

    IQ = 0

    nyehehehehe
  6. Better Numbers I'd say this is a pretty useless script, but it may help some other player mostly those who are fancy and stuff. Script (14 lines) The script is not mine, I forgot who owns it function regex(n: object) :: text: if "%{_n}%" contains ".": set {_s::*} to split "%{_n}%" at "." set {_n} to "%a({_s::1})%.%last 2 characters of {_s::2}%" return "%{_n}%" else: set {_n} to a("%{_n}%") return "%{_n} ? 0%" function a(b: text) :: text: if length of {_b} > 3: return "%a(first length of {_b} - 3 characters of {_b})%,%last 3 characters of {_b}%" return {_b} ######## It can be used like this ############ # # # send "Balance: %regex(balance of player)%" # # # ##############################################
  7. cant u just make the lockdown like toggleable?
  8. Swayl

    Skript

    I think something is wrong with my skript... c command /yeet [<text>]: trigger: if arg-1 is set: broadcast arg-1 if arg-2 is not set: broadcast nothing
  9. Swayl

    Staff Needed

    I mean, open applications, But you need a certain amount of playtime to apply. That's what I did
  10. format slot 15 of player with wooden axe named "&6&lSet Player 2's Position" with lore "&7[&b*&7]&r &aPlayer 2's Position: &b%{*.player.pos2}%" to run format gui slot 15 of player with wooden axe named "&6&lSet Player 2's Position" with lore "&7[&b*&7]&r &aPlayer 2's Position: &b%{*.player.pos2}%" to run Should work.
  11. Bounty System Using this script, you are able to put "bounties" on players. Once they die, the player who killed them gets the bounty that you placed on them. I've also included a death system here. Bounties can't be complete when there's no death system. I've also included bounty list. Once page 1 is full, Page 2 will be created and the bounties will be continued in there. Commands /bounty <player> <amount> - The minimum amount is 500. /bounties - Check the players with bounty. Pictures Script (74 Lines Without the #) options: min: 500 # Minimum bounty amount pre: &3&l(BOUNTY) # Prefix for messages command /bounty [<offline player>] [<number>]: trigger: if arg-1 is set: if arg-2 is set: if arg-2 >= {@min}: if {balance::%uuid of player%} >= arg-2: # I use {balance::%uuid of player%} as money. feel free to change it to "player's balance" # arg-1 is not player (If you don't want players to put the bounty on themselves, remove the # at the start of the line.) add argument 1 to {bounty::list::*} if {bounty::list::*} does not contain arg-1 add argument 2 to {bounty::%uuid of arg-1%} remove argument 2 from {balance::%uuid of player%} send "{@pre} &7A bounty of &b%arg-2%$ &7has been placed on &b%arg-1% by &b%player%" to all players else: send "{@pre} &7You do not have enough money to place a bounty." else: send "{@pre} &7The minimum bounty amount is &b{@min}&7." else: send "{@pre} &7Please provide an amount." else: send "{@pre} &7Please provide a player." on death of player: if attacker is a player: if {bounty::list::*} contains victim: set {_bounty} to ("%{bounty::%uuid of victim%}%" parsed as number) add {_bounty} to {balance::%uuid of attacker%} broadcast "{@pre} &b%attacker% &7just claimed &b%victim%&7's bounty of &b%{_bounty}%$&7..." remove victim from {bounty::list::*} delete {bounty::%uuid of victim%} # Kill System add 1 to {kills::%uuid of attacker%} # Assuming {kills::%uuid of attacker%} is your kills variable... (Change if you want..) add 1 to {deaths::%uuid of victim%} # Assuming {deaths::%uuid of victim%} is your deaths variable... (Change if you want..) # KDR System (Remove if you want..) set {KDR::%uuid of attacker%} to KDR(attacker) # Assuming {KDR::%uuid of attacker%} is your variable for KDR (Change if you want.) set {KDR::%uuid of victim%} to KDR(victim) # This KDR Function is not mine. This is BennyDoesStuff's KDR Function. function KDR(p: player) :: number: set {_u} to uuid of {_p} if {kills::%{_u}%} != 0: if {deaths::%{_u}%} != 0: return {kills::%{_u}%} / {deaths::%{_u}%} else: return {kills::%{_u}%} else: return 0 # Bounties (See the players with bounties!) command /bounties [<text>]: trigger: page(player, 0) function page(p: player, page: number): set {_pageStart} to 45*{_page} set {_i} to 1 set {_a} to 0 open virtual chest inventory with size 6 named "&b&lBOUNTY &7List &f&oPage %{_page} + 1%" to {_p} wait 2 ticks loop {bounty::list::*}: (loop-index parsed as integer) > {_pageStart} set {_player} to loop-value set {_u} to uuid of {_player} format gui slot {_a} of {_p} with skull of ("%{_player}%" parsed as offline player) named "&7%{_player}%" with lore "&7Bounty &8- &b%{bounty::%{_u}%}%" to do nothing add 1 to {_a} if {_a} = ((45*{_i})): exit loop format gui slot 49 of {_p} with book named "&eMain Page" to run: page({_p}, 0) if (amount of {tuber::videos::%{_u}%::*}) > {_pageStart} + 45: format gui slot 53 of {_p} with arrow named "&9Next Page" to run: set {_page} to {_page} + 1 page({_p}, {_page}) if {_page} > 0: format gui slot 45 of {_p} with arrow named "&9Previous Page" to run: set {_page} to {_page} - 1 page({_p}, {_page})
  12. Post one of your greatest scripts here
  13. Good idea. I'll be making it soon, But right now, I have some things I'm more focused on! Sorry
  14. make me a script that does my homework for me it'll really help pls
  15. Anti-Bot A simple way to prevent bots from joining your server or spamming on your server . You have to type a given text to verify that you are not a bot. Those texts are randomized and cannot be the same. Players with the permission "Staff" does not have to go through verification. Pictures ^ I also included a welcome message, so feel free to edit ^ Script (24 lines) options: pre: &3[Anti-Bot] on join: loop 100 times: send "" wait 1 second set {antibot::%player%} to random 5 char string from `a-zA-Z0-9` send "{@pre} &7Please type out &b%{antibot::%player%}% &7to confirm you're not a bot." on chat: if {antibot::%player%} is set: if message does not contain "%{antibot::%player%}%": send "{@pre} &7Please type out &b%{antibot::%player%}% &7to confirm you're not a bot." cancel event else: delete {antibot::%player%} send "{@pre} &7Thank you for the verification. Enjoy playing in Promise! /tut to learn the basics." cancel event on command "msg": if {antibot::%player%} is set: send "{@pre} &7Please type out &b%{antibot::%player%}% &7to confirm you're not a bot." cancel event
  16. Item Display (Skript) Be able to display your item on the chat by typing [item]. If the tool does not have a lore and no enchants, It'll say "No Enchants" and "No Lores". If it has an enchant, but does not have a lore.. It'll say the enchant but say "No Lore"... Stuff like those. Script (17 lines) on chat: if message contains "[item]": cancel event player is not holding air set {_count} to amount of player's held item in player's inventory if player's tool is enchanted: if line 1 of lore of player's tool is set: replace all "[item]" in message with "&8[<tooltip:&e%tool's name ? type of tool% &8(&f%{_count}%x&8)%nl%&7%tool's enchantments%%nl%%tool's lore%>&f%{_count}%x %name of tool ? type of tool%&8]&7" else: replace all "[item]" in message with "&8[<tooltip:&e%tool's name ? type of tool% &8(&f%{_count}%x&8)%nl%%tool's enchantments%%nl%&7No Lores.>&f%{_count}%x %name of tool ? type of tool%&8]&7" if player's tool is not enchanted: if line 1 of lore of player's tool is set: replace all "[item]" in message with "&8[<tooltip:&e%tool's name ? type of tool% &8(&f%{_count}%x&8)%nl%&7No Enchantments.%nl%%tool's lore%>&f%{_count}%x %name of tool ? type of tool%&8]&7" else: replace all "[item]" in message with "&8[<tooltip:&e%tool's name ? type of tool% &8(&f%{_count}%x&8)%nl%&7No Enchantments.%nl%&7No Lores.>&f%{_count}%x %name of tool ? type of tool%&8]&7" replace all "||" with "%nl%" in message send "%player's displayname%&f: &7%message%" to all players
  17. Rename (Skript) This script is really simple. With this script, you are able to rename your items with colors! Horay. The permission to have access to this command is "rename", It's good for donor perks on your server. Script (17 lines) options: perm: rename no-perm: &3Insufficient Permissions pre: &3[Rename] command /rename [<text>]: permission: {@perm} permission message: "{@no-perm}" trigger: if arg-1 is set: if player's tool is not air: set name of player's tool to "%colored arg-1%" send "{@pre} &7You have set the name of your tool to %colored arg-1%" else: send "{@pre} &7Sorry but you have to hold an item" else: send "{@pre} &7Please provide a name"
×
×
  • Create New...