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.
-
View User Profile
-
Send Message
Posted Dec 11, 2011I've tried all the commands and it still doesn't work...
How can I get it so, when someone right clicks a sign they get promoted?!
Sorry, thanks.
-
View User Profile
-
Send Message
Posted Dec 11, 2011@craftopia
Could you pm me your server info so I can check out if it works or not?
and what might be the issue if it isn't working
-
View User Profile
-
Send Message
Posted Dec 11, 2011@cr0ssbreed
Next time don't post your request here and only reply on the tickets.
and just a note to everyone
We won't look at feature requests through the comments
We use comments for support issues
-
View User Profile
-
Send Message
Posted Dec 11, 2011@RowdyKingDippy
There is a straight forward tutorial. and the commands you need to add depend on the permission system you use.
Commands
check there for the commands to create a sign
-
View User Profile
-
Send Message
Posted Dec 11, 2011How do I create a sign, when right-clciked will promote players from Guest to Member?
There's no straightforward tutorial here (I've ended up using PEX)
-
View User Profile
-
Send Message
Posted Dec 11, 2011@Dockozel
It is meant to give a player the permission for it not a group. After all it is just a short time permission grant. So it wouldn't be useful to give it to a group.
And well for permissionsbukkit it would look like: permissions player setperm <player> <permission> true
and
permissions player unsetperm <player> <permission>
-
View User Profile
-
Send Message
Posted Dec 10, 2011There are so many commands with different formats in permissionsbukkit. The "permission_console_command_add: " and the "permission_console_command_remove: " look like a general command format, but the format is different whether you're talking about a group or a player, so I could only do group commands or player commands? You designed this for permissionsbukkit correct? If so, what did this section look like before you had the pex format in there?
-
View User Profile
-
Send Message
Posted Dec 10, 2011Any chance this will get Register or EssentialEco/BOSEconomy support?
-
View User Profile
-
Send Message
Posted Dec 10, 2011Does this work with Permissions3?
It's extremely confusing (and I'm not a noob, been running a server for half a year) I know what I'm doing..
Does this even use a permissions plugin? :S
Thanks,
-
View User Profile
-
Send Message
Posted Dec 10, 2011I dunno what im doing wrong, but i have it set to true in config and cannot get redstone to activate a sign. Is there a specific position the sign must be in?
-
View User Profile
-
Send Message
Posted Dec 9, 2011@Dockozel
Well considering you are u are using /svs add "bla" you dont need the [scommand].
If you want it to be executed by the server which you apparently want seeing you put scommand on the sign. You can just use "/svs add <server> commandhere
seeing this command has a console version you wont need to grant permissions. Also if you look at the "permission_console_command_add: " and the "permission_console_command_remove: " configuration they have the pex commands chance them to the permissionsbukkit ones
-
View User Profile
-
Send Message
Posted Dec 9, 2011So, I feel like an idiot. I've never used a sign to execute a command. I'm using CB1560, Serversigns 1.5.2 and permissionsbukkit 1.2. use console perm grant=true. Problem: I want to make signs that promote people to another rank (aka group). Here's what I'm doing: Placed a sign that said "[scommand]". Then I typed "/svs add "whatever permissions command to add user to group". Then I have to addpermgrant whatever node that command needs. My users still can't use the sign. What am I doing wrong?
-
View User Profile
-
Send Message
Posted Dec 8, 2011@TerraNetworkOrg
Well then there might be an issue with the config you have please back up the serversigns folder you have now and the jar. download 1.5.2 again. and let it boot clean. Then check the config.
That line should be there then. Just put it on true.
-
View User Profile
-
Send Message
Posted Dec 8, 2011I'm sry, next time :-)
The is no "use_console_permission_grant:" inside my config, so no i didn't changed it.
-
View User Profile
-
Send Message
Posted Dec 8, 2011@TerraNetworkOrg
Please use the ticket system next time.
Also did you alter the config to let "use_console_permission_grant: false" say true?
-
View User Profile
-
Send Message
Posted Dec 8, 2011@IrcCat
Please use the ticket system and also give a link to the plugin you use for the permissions
-
View User Profile
-
Send Message
Posted Dec 7, 2011Legacy perms please?
-
View User Profile
-
Send Message
Posted Dec 7, 2011Genij literally helped me for 5-6 hours today and another minimum of 5 hours helping me previous this week. He/we finally got it the way it should be set up.
Props to him
-
View User Profile
-
Send Message
Posted Dec 4, 2011@Molenbouwer
The example line you have given us is normal that it doesn't work with <server>.
That command you are trying to use. Is a command that gives the user feedback. By using <server> you are telling it to let the console run it. Which means the player will never see any feedback. Cause the player wasn't the one using the command.
Please make sure that the commands you are trying to use in the console are also useful to let the console execute. Cause feedback commands will not work for players. Use the grand permission feature to give them the temp rights to the command you want them to use and let the player execute it.
-
View User Profile
-
Send Message
Posted Dec 4, 2011@DarkMinecrafter
That is already implemented. We are busy with updating the documentation. But if you open the config.yml you have a line with block_ids: 68;63
Those are the sign ids. you can either add the button/pressure value or remove the sign ids and only use the button/pressure plates