ServerSigns
Please check our Wiki before asking questions or submitting tickets
This project has not been abandoned completely - it's just been lacking some love & care for the past year; I plan to continue development and fix any outstanding issues in the new year. Thank you for your continued support of ServerSigns - Exloki
ServerSigns (SVS) provides the ability to bind player-dispatched and server-disptached commands, messages and actions to signs and every other block in Minecraft.
As soon as a player clicks on a ServerSign, the configured actions are executed in the order and with the settings you specified.
Source: https://github.com/serversigns/ServerSigns
Main Features:
- No limit: Unlimited commands per ServerSign
- Multi-role: Assign a variety of actions whenever a sign is clicked (even define different commands for right/left clicks)
- Messages: Send messages to the player
- Broadcasts: Send messages to the whole server
- Player commands: Executes commands as if the player typed it in chat
- Server commands: Executes commands as if it was executed from the server console
- Delayed actions: Any action can be delayed (from seconds to months)
- Looped actions: Any ServerSign can be converted to loop server commands with defined intervals
- Require permissions: ServerSigns can be set up to require permissions to use
- Grant permissions: Grants players temporary permissions to execute the commands
- Per-sign costs: Bind exp, money, and item costs to ServerSigns
- Protected: Automatically protects every ServerSign and any attached blocks.
- Basic scripting: Implement if/else and return statements in commands on ServerSigns
Please note that version 2.6 and above will notify you when a ServerSigns developer joins, this is so you're aware of who we are when we join, and we can help you with any issues you may be having with ServerSigns as quickly as possible. Version 4.1 and above will also send the developer a message stating the current plugin version.
This plugin utilizes an auto-updating feature that will check for the latest ServerSigns build and automatically download that build if it is newer than the currently installed one. This can be disabled by setting 'check_for_updates' to false in the config.yml
This plugin uses Metrics to gather basic non-identifiable statistical data such as the number of ServerSigns you are using, your plugin version, and other standard mcstats.org data. You can opt-out of this feature by setting 'metrics_opt_out' to true in the config.yml. A full list of gathered information can be found here: http://mcstats.org/plugin/ServerSigns
Click Here to view Tutorial Videos
Known bugs
- ALL VERSIONS: Spawn protection prevents non-ops using ServerSigns This issue cannot be 'fixed', as stated by md_5 - known sollutions include setting spawn-protection to 0, or clearing ops.json https://hub.spigotmc.org/jira/browse/SPIGOT-1112
Reporting Bugs / Requesting Features
When reporting bugs, requesting features, or providing any other constructive feedback that will require code alterations you must submit a ticket to have your voice heard and action taken (if required). Any topics of this nature that arise in the comments section will henceforth be ignored.
Before you raise a ticket, you need to make sure that the feature you are requesting isn't already implemented (read all of the help pages which show SVS features), or the bug you want fixed hasn't already been resolved in the latest development build (a rolling change log is kept on the development build page, use this for reference)
When submitting a ticket, please be as descriptive and informative as possible. If reporting a bug or flaw, then show all the steps required to reproduce the problem, also attach any and all related screenshots or other files to the ticket. If requesting a new feature, then please be as detailed as possible so we have a very clear idea of what it is you're suggesting - that way if we do implement your suggestion, this ensures it is exactly as you want it to be.
Once you have submitted a ticket, rest assured that it will be handled. We do not give a definite time frame for replies or actual alterations, but we try our absolute best to get tickets resolved as soon as possible. Please do not: bump tickets, raise multiple tickets for the same issue, send PMs to our developers, or discuss the ticket in the comments section. Tickets that do not meet the expectations outlined here will likely be declined without comment.
I've been trying to make a worldedit replacenear command to work, but i cant seem to get permissions working for the builder permissions group we have. The permissions group i want to use it has the serversigns.use and serversigns.builder
Its entirely possibly i'm just misunderstanding the plugin and have just messed up something while typing the sign commands.
Thanks in advance!
@CalibeR50
I indeed use 1.5. Ill give 1.4.1 a try now
EDIT: Still no luck, I keep getting the permission error while I am sure I am adding the permissions correct. I'll take a break from this and try 1.4 later
@Molenbouwer
Oh sure, Sorry. Are you using serversigns 1.5? Maybe i broke the setpermission Feature with 1.5, i didn't tried it. I'll Check it later.
@CalibeR50
I PM'ed you the IP yesterday, but it is still 1.8.1 :(.
@Genij
Alright, so now I am not getting the permission error anymore but they can use any sign, doesn't matter if there is a Permission for it or not. For example. Peasant can promote to Squire, but also to King. They should only be allowed to promote to Squire
@Genij
It should work with the serversigns.custom.X alone. Serversigns.use alliwes you to use EVERY sign. The serversigns.use.playercommands permissions let you use EVERY sign which is Not a sign with <Server>.
Molenbouwer, you can give me your serverip, i'll be back at home in One Hour so i can Take a Look in it.
@Molenbouwer
Well this is just a first test to make sure they can use it if you give them the permission.
As far as I always understood (never tried it myself they need the use and need the permission of the sign if you add permissions)
so for example you would need to make the admin signs have admin rights on it and only give the admin class the "serversigns.custom.admin"
might be wring on it tho seeing I havent used it myself
@Genij
Alright, will try now. I don't want them to use all signs though. I just want them to use the sign with the Squire permission attached. They do not have serversigns.use.playercommand perm
@Molenbouwer
So wait a second your peasant group ONLY has the - serversigns.custom.squire permission?
If so give them the "serversigns.use" permission aswell. and make sure that they DONT have the "serversigns.use.playercommand" permission
@Genij
The group Peasant has the following permission for Serversigns:
- serversigns.custom.squire
The command I add : /serversigns add <server> pex user <player> group set Squire
The permission I add: /serversigns setpermission squire
I says I don't have permissions to use the sign.
@Molenbouwer
Could you check if the message even goes to the console. Also I wonder what permissions the group have you are trying to let it execute.
Cause it is sounding like "serversigns.use.playercommand" is set to true.
This permissions does this "You can only use ServerSigns without Server Commands ".
@lawliet555
No error? Can you send me your Server ip? I'll take a look in it.
I can not get the redstone working for the server sign. The config has it set to true as well.
Thx
@TerraNetworkOrg
You can make a sign with /tppos X Y Z. If the player don't have the permission to execute this command, you have to use the new command to give the sign permissionGrant.
/serversigns addpermissiongrant <permission x>: The player who clicks the Sign get the permission x for a very short time
So you have to write /serversigns addpermissiongrant essentials.tppos
@Genij
Blegh this sucks, I was an OP when using the message. It now is whining about permissions again. This crap is starting to annoy me :P
@Genij
Aah never mind about the previous message. It did indeed work, but it didn't give me a message. Thanks a lot
@Genij
Somehow adding the <server> disables the command.
Added feature to let players execute commands without permissions
Does it mean i (as admin) can create a sign with /tp x,y,z and the user can use it without having the permission to use /tp ?
@Genij
thanks for you answer :P
@Molenbouwer
to make it work for the player clicking it.
the <user> was directly copied from PEX. to make serversigns fill in the players name you need to use <player>
So it would become:
/serversigns add <server> pex user <player> group set Peasant