Command Signs

Useful links: - Scripting - Task scheduling - Placeholders - Script commands

Why is this better than other command sign plugins?

- virtually database free, meaning...
- There shouldn't be any performance issues from having lets say, 1 billion signs.
- Updating is a breeze
- Making pre-configured signs is really simple
- You can safely allow your users to create specific command signs. e.g. an elevator sign
- Per sign permissions! (Yeah, you have custom permissions per sign)
- You never have to use a single command (players hate having to learn new commands)


- Custom signs are located in the folder "Signs" within the SignRanksPlus folder.
- By default there should be a couple command signs located there.

enabled: true
elevation: operator # This means the commands will be sent as op.
- '{arg1} {arg2} {arg3}'
- all &9Example Public Broadcast
- player {player} &cExample Private Message
- '\Force the player to send this message'
- 'if {}'
- 'player {player} this is an if statement'
- else
- 'player {player} you lack build permission :('
- endif
- \just ended an if/else block.
text: '[CMD]'

To use this sign put [CMD] on line 1 with the command you want to execute on the following lines.

If you look, there are also 3 other example commands:
- "all" causes a broadcast to show up to all players
- "player" will show a message to just one player
- \<text> will force the player to send a chat message.

Create your own:

Copy the default "command.yml" sign in the "Signs" folder - Remember to change the text to something other than "[CMD]"
Change the commands that are executed, see below for {PLACEHOLDERS}
- signranks.create.<name>
- signranks.use.<name>

Placeholders (uses squiggly bracket)

- {line1}
- {line2} or {arg1}
- {line3} or {arg2}
- {line4} or {arg3}
- {player}
- {world}
- {itemid}
- {x}
- {y}
- {z}
- {gamemode}
- {health}
- Please click here for a the full list.


Posts Quoted:
Clear All Quotes