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.
19.08 01:21:35 [Server] INFO Server returned HTTP response code: 504 for URL: http://mcstats.org/report/ServerSigns
?? :-/ I don't get it..
Need to add support for altering specific signs WITH another sign IE: Use an SVS sign to reset the cool-down of either: Specific signs /w co-ordinates, &/or signs in a specific region (worldgurad), &/or signs within a radius. Ability to reset specific player's cool-downs, or global cool-downs [within specific range/region/defined X,Y,Z]
useful for dungeon designs with SVS. a timed cool down can be bypassed by simply waiting for the cool-down to expire (player needs 5 of an item, can only get 1 per sign, cool-down set for 24h) with this you can set a command the re-sets the cool-down for those 5 signs so they can't 'camp' for more of the item. (clear inventory on entry to dungeon& reset specific cool-down) -reset global cool-down per player would reset every svs sign in every dungeon. not what we want.
is there a way to do this with (IE:) /svs resetcd <player> <[X,Y,Z]|region|range> ? [doesn't appear to be listed on the commands pages]
Thank you.
-other specific sign altering code would be using "/svs modify <[X,Y,Z]|region|range> <command>" to alter another sign remotely. -shorthand: "/svs m" -add support for multiple worlds "/svs m <world:[X,Y,Z]|region|range> <command>" (if no world specified, current world co-ordinates will be used)
-add ability to set a sign to have already be in cool-down mode before a player clicks it for the first time. (IE: good for keeping people on-track in a quest) "/svs cooldownlock" | "/svs cdl" locks the sign untill [previously discussed] remote altering of the sign's cool-down per-player/global -add "/svs listplayers" | "/svs listp" | "/svs lp" lists all existing player-specific data associated with the sign [ie:cool-downs, active permissions, queened events; recommend adding "/svs lp <cooldown|permissions|que> <player>" | "/svs lp <cd|p|q> <player>" to narrow results/self-spam add additional fields as needed, theses are a few i thought of off the top of my head.] -also alias "/svs info" with "/svs list"
(i think that's all i have for now... just a few thoughts to further fine-tune svs's abilities)
@Exloki
Sweet, I can't think of any other ideas for the plugin, honestly. Thanks for being so responsive.
@jawsh95
Hey there, we aim to be as fast we can! :D
I've pushed a build to the dev branch that fixes the confirmation bug (thank you!) and also adds a couple new features: Any empty strings in the languages.yml should now be ignored (as in no message will be sent there) and any whitespace and the start/end of a string will be trimmed before sending, so that should solve the empty prefix issue.
In regards to making it so you don't need commands to create a ServerSign - I'm going to have to decline at this time due to the way the plugin is operated at such a core level. You could very easily just have the server do a blank command though, like "/svs add <server> /notACommand" if you don't mind the occaisonal console print for unknown command.
@Exloki
Wow, I wasn't expecting such a fast reply. Thanks!
I've tested it out and the only bug I seem to be having is that I can't bind the /svs confirmation [true/false] [message] to blocks.
I'm happy this plugin is staying updated because it's easily one of my favorite plugins ever due to the limitless amount of things you can do with it. Thanks again.
I know you asked me to use the ticket system and I'll do that from now on but since I'm already making this comment I'm going to post a few more suggestions that I hadn't thought of asking about earlier.
1) If it was possible to set up a server sign without having to add a command, this would be useful. For example, with the function I was talking about earlier you could set an enderchest which costs 1 exp level to open and has the setcancel option at fail_only. With this set up, you don't even need to attach any commands, so it would be great if you could attach things like /svs xp, /svs setcancel, /svs confirmation and so on to blocks without having to add commands in order for it to work.
2) Under the languages.yml file, it would be great if you could enable/disable certain strings and customize everything further because many functions of server signs end up sending multiple messages to the player. For example, the confirmation "/svs confirmation true This will cost one experience level. Are you sure?" will come out with "This will cost one experience level. Are you sure?" followed by yet another message containing the string in the languages.yml file. One more example of this is if you did "/svs pi am.1 id.1" which would set the requirement to use a server sign at 1 stone block, if you don't have one stone block and you right click the sign two messages pop up, one saying "The following items are required..." and another saying "1x Stone" Another matter somewhat related to this is when you remove the prefix for server signs, all messages will have a space before them, so you can't really disable the prefix.
I hope my feedback is useful for you. Thanks again for keeping the plugin updated.
@jawsh95
Hey there. In the future, please use a plugin's Tickets page (located at the "Tickets" tab at the top of the plugin's page).
I can definitely see the use for your suggestion, so I've added a feature to the dev branch that should accomplish what you're looking for. It's basically a change to the current cancel system from a boolean (true/false) value to an enum (type) value - the current types are ALWAYS, NEVER, FAIL_ONLY, SUCCESS_ONLY. These indicate when the event should be cancelled; so for your purpose you would want to use the FAIL_ONLY mode.
Give it a try from the dev branch (http://dev.bukkit.org/bukkit-plugins/serversigns/pages/development-builds/) and let me know if it meets your requirements.
Suggestion:
Add a new option for the /svs setcancel command that allows a player to interact with the block only after the server sign has been successfully activated, such as after experience removal or funds removed. The command could be something like /svs setcancel initial or /svs setcancel confirmed just for a few ideas off the top of my head.
The thing I'm trying to do is set an enderchest which costs one experience level, and after the player's experience is removed and the server sign is activated it allows them to interact with the block, which opens the enderchest.
I know I could just do /svs add *enderchest but first of all that doesn't cause the enderchest to have the opening animation which isn't quite as slick, and third I don't like having commands pop up from users under socialspy when I know they have no access to them, it's a bit suspicious. This would also be useful for entry access, such as a charge to press a button to get through a door or activate a command block or whatever the case may be.
I'm not sure if it would be possible to add something like this, but if not I believe there are plenty of ways around it. Perhaps server signs could keep an eye on how much experience/money a player has, so it knows when it can and can't allow certain players to interact with the block.
I would really appreciate it if you added something like this, and thank you for reading my long message.
@stefanfce
You have 4 possible solutions to your problem:
/svs add *pex user <name>.... /svs grant add [p:permissions.manage.*]
right clicking on sign, nothing happens
newest version 4.1.2
What i do wrong? :/
@stefanfce
Step 1. Update to v4.1.1 or v4.1.2 if it's approved by the time you read this. Step 2. Read http://dev.bukkit.org/bukkit-plugins/serversigns/pages/commands/
/svs grant add .... dont work @ 1.8.7 with v4.0.1
Hey Guys,
can u add a command like /svs destroy to destroy the function btw the sign after one use? Or a setting like configuration as destroy true/false?
Thanks.
@Exloki
Woah, nice work. Didn't know you started working on the plugin again
@scabbed6982
You can have a ServerSign message the player a URL which they can click in chat, yes.
hello, sorry for my english, i didnt found the answer
is it possible to open an url when clicking on a sign, like signurl ??
thank you
Can I also remind everyone we have a TICKET SYSTEM for plugin ISSUES
@DeltaForce658 @EncryptedPixel @hereami321
Please compress (.zip) your plugins/ServerSigns folder and PM it to me so I can investigate your issue properly.
@Smiling2death
Unable to reproduce locally; also the ClassCastException you're encountering is only typically encountered when you /reload ServerSigns instead of restarting the server for a new build. As you can probably see yourself - it's stating that the SVSMeta cannot be cast to SVSMeta (which indicates there are multiple instances of SVSMeta, which indicates a /reload has occurred).
@EncryptedPixel
Maybe try to download the latest version of serversigns? and dont edit any config and check out if it works ?
@Smiling2death
I've tested it when I remove ServerSigns the server starts fine.
@hereami321
Use Bukkit or Spigot :D