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.
@Phibedy
Cooldowns right now aren't on player level. So the Cooldown isnt able to say only that user cant use it anymore.
@MufinMcFlufin
Well it is possible but I would kinda need a more details of your idea cause for example after claiming do you want someone to be able to unclaim.
The not claiming by any one else is a protection worldguard should be having. As for letting the person not buy others thats easy. You will just need to add a permission to the signs give those to the people. Then you just need to add the node serversigns.custom.claim (example) to the group(s). Then when they click the sign you need to add a line to the player that the dont have the node anymore.
Shortly as far as your idea goes as you stated down there it is possible.
I'm trying to use this as a method to allow people to claim a WorldGuard region, then once said region is claimed, the owner cannot claim another region, and no one else can claim said region. Do you think this is possible with ServerSigns?
Everything works fine. Is it possible to block the sign for the user after the user have used it once?
Best plugin-support I´ve ever got ;)
update: atm it isn't working I know why. But can't say if/when it might be implemented I aint the coder just support could you make a ticket for the feature request?
@TichoCZ
Never used those so can't give you a straight answer right now. I will go test it in a bit.
Is it possible bind MCDocs or CommandHelper commands on ServerSigns sign?
@Phibedy
Read the page of vault and you will see which economies are supported
ps. I dont run a server so I have none
Ok thx :)
@addemod
If you would read the documentation you will see that there is a tag called player. So using pex adding a person to a group would be.
/svs add <server> pex user <player> group add nether
if you need to set the group it would be
/svs add <server> pex user <player> group set nether
I fixed that, but how do I do so if someone uses that sign I want HIM to go in that group? Not have to make a specified user? do you get it? because if I do /serversigns add pex group nether user add
it will be: "Error in command syntax. Check command help."
But if I do /serversigns add pex group nether user add addemod
It says: "User addemod joined nether"
But I want everyone that uses this sign joins this group...
I get: Error in command syntax. Check command help.
in console I get this
Now I got it. I thought about the red text, and in my opinion, the word "vault" hadn´t made sense. Vault is a plugin, never heard of this. Thx for your support :-D Nevertheless which conomy plugin do you use?
@Phibedy
As I said read the red text. And check what "vault" might be.
Sry, I used econ but now I switched to iconomy, I just mixed it up. Which Economysystem do you prefere? I am using permissionsex. Is it possible to add Iconomysupport?
@Phibedy
Well you say you have iconemy 6 but I wonder did you read the red text on this page?
"As of Serversigns v1.6 you need vault to use economy systems"
Cause I dont see you listing it
I use Iconomy 6 the latest rec. bukkit Serversigns 1.8 Commandbook Need sth more?
You could test it on your own at my server. We use your Plugin in a absolutely amazing way. Just write your ingame-name and I will whitelist you.
best regards Phib
@Jns20
Did you alter the config to make it possible to use permission grant?
@Phibedy
hmm could you give me the server info phibedy and also which version of bukkit you use?
Hi, I got a problem, if I use /svs setprice 60 and rightclick on a sign it says "Der Preis wurde erfolgreich gesetzt". But I don´t have to pay if I rightklick on the sign.
Yes I read the commands and the permission grant didn't work. I had to use pex user <player> add CommandBin.warp and then warp prison, and then pex user <player> remove CommandBin.warp
Not sure why the grant wouldn't work (I made sure to put it before the warp)
@Jns20
Well the reason that it isn't working with <server> is because it teleports the user of the command with <server> you let the console teleport I dont think he can go anywhere.
And it works for you because YOU have the permission. and if you read the documentation you can see we have a permission grant system so you can give them temporarily the permission to use the command.