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.
@Ghabryel05
have you added a second question with answers?
you have to do the first part for every menu on the sign.
then add the if statements for each menu and option.
1. add question.
2. add answers.
-repeat 1&2 for additional menus
3. display menu
4. check menu for answers (if statements, gets lengthy) (the checks for the second menu should not be nested in your first menu if statements, just add them after your previous menu checks)
-repeat 3&4 for multiple menus
@leasoncre
i have try this for fun but dont work, will be fun to call a new displayoption to make a quizz
- adding the commands to execute/ "IF" statements--///svs add <if> checkOption MenuName=Yes
/svs add <displayoption> NewmenuName
/svs add <endif>
i Love u dude thx :p
<<reply 2759815="">>
example with exact syntax: (as you would type it in)
i do not believe the answer is case sensitive, but it must be spelled correctly.
/////--- setup the menu itself: ---/////
/svs opt MenuName question Question: Yes or No?
/svs opt MenuName add Yes Desription: You answer with 'yes'
/svs opt MenuName add No Desription: You answer with 'no'
/svs add <displyoption> MenuName
////--- adding the commands to execute/ "IF" statements ----////
/svs add <if> checkOption MenuName=Yes
/svs add <msg> You selected 'Yes'
/svs add <endif>
/svs add <if> checkOption MenuName=No
/svs add <msg> You selected 'No'
/svs add <endif>
////---- example of several options doing the same action in one check (good for menus with quite a few options needing the same action) ---////
/svs add <if> checkOption MenuName=Yes|No
/svs add <msg> You selected 'Yes or No'
/svs add <endif>
Hi, I need to use option with some signs. But the signs display correctly the question answer and i dont understand how attribute a command for the YES and another command for the NO. I want when the player say "Non" ( fr ) the signs execute for exemple /warp spawn and when a player say "Oui" the signs execute /warp start
i hope its possible thx !
Thank you for support! Sorry about the unneeded report. Will be sure to check in future.
@CeIebrimbor
This has been fixed in the latest development build already - please check the Dev builds page before reporting issues :)
http://hastebin.com/jasawizapi.avrasm
This seems to happen when signs have an item cost. Latest on Spigot 1.9
@TitanKingX
The 4.5 update only adds new features and bug fixes - all previous signs should be loaded as usual. There are thousands of servers using the latest update already with no issue, so please double check it's not an issue on your end (did you accidentally move the ServerSigns folder? Are the worlds loaded? Etc.)
If you still think there's a problem please submit a ticket and include a copy of your plugins/ServerSigns folder and I will investigate it first thing tomorrow morning.
Does the 1.9 update require you to make new signs, My old signs from 1.8 don't work!
I tried to edit en_language
Once I was done I press save and did /svs reload
It did not work and notepad kept saying: "Update? Reload svs" something like that
Is language editable?
http://serversigns.de/wiki/Configuration#Custom_Translation_Files
@Exloki
Thanks man, after the rebuild everythings works fine!
Thumbs Up!
@waoler
This plugin does not use an NMS code so it should be compatible with any changes to the API made for 1.9 - but I'm building the Spigot 1.9 jar now to double check.
Could you update this to 1.9 ? I would like to use it on my server.
@leasoncre
Working, thanks for fast support!
<<reply 2726035="">>
console cannot teleport. you're useing the /tp command incorrectly. what you want is: /tp <player> x y z
@leasoncre
I wanted to add this:
/svs add <server> both tp -158 17 1064
and not working for me
<<reply 2726030="">>
nope.
unless you're having problems with a released version. then try the latest dev version before submitting a bug report/ticket.
@leasoncre
So I have to use the dev build?