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.
In reply to skyhighspirits:
*Problem Fixed**
For future reference, the issue was caused by the Serversigns plugin, which enables signs to work as a command block.
The problem was:
1: Creating a sign by typing /svs create <signname>
2: Restarting the server before right clicking the sign to execute the command
3: Logging back into the server, now in a non-interractive mode induced by the command
4: This removed all options for interacting with blocks on the entire map.
The fix was:
1 find an unused sign
2 type /svs create <signname>
3 right-click the sign to create the serversign
4 type /svs remove
5 right-click the serversign
6 All interaction with server restored.
In reply to skyhighspirits:
An easier solution, the command /svs void is designed for these specific cases.
It will remove pending commands like your /svs create
The command /svs import is way to dangeuours... U can see every root file of the server, need urgently a remove or only to plugin folder. Right now.
In reply to im2g0d:
I was fixed in v4.6.3, sadly I broke the command. The v4.6.4 will fix the command and all should be ok.
Hello,
Not sure if this is the correct way to ask questions. Please direct me if there is another way.
I am creating a sign with multiple commands and plugins in use. Luckperms, Essentials and of course Serversigns.
I have 5 lines of commands: 1: /lp user <player> parent set member (I'm moving player from default to member group)
2: /kits member (giving players the member group kit)
3: /add addperm |p essentials.eco (giving temp permission to use eco command)
4: /eco give <player> 500 (giving player money)
5: / add removepermission essentials.eco (removing essentials.eco permissions)
I have tried different combinations but I get errors about unknown commands... I've tried to add and remove the eco permissions. In this last one I tried, I tried the temp use |p, but I am not sure if I am using it correctly. Line 5 I would not need if it was set for temp use... also, I need the players to only use the sign once. So I was doing a setuse line, but it appears that that is for set uses for all time, instead of uses per player. How do I set it up for uses per player, that way they can't just click until there finger is tired getting free tools and money?
Thank you,
Dragonclaw103
In reply to Dragonclaw103:
Hello,
If the player doesn't have the permission to use /eco or /lp you must use <server> it will execut the command from the console.
i.e. : /svs add <server> lp user <player> parent set member
For the unknown command, which are you writing in your chat ?
In reply to epicanard:
Hey, Yeah, I figured it out plus more. the /lp command was good as is. The eco command is done by <server> as you stated. but I still had an issue with the player using the sign many times.. I solved this in Luckperms by adding the permission restriction to the default group on the serversign and in Luckperms I removed the inherited permission in member. That way once they were any other group than default, they could not use the sign... works perfectly now.
my end result
/svs add /lp user <player> parent set member
/svs add /kits member
/svs pgrant add essentials.eco
/svs add /eco give <player> 500
/svs setpermission default
ty
Dragonclaw103
In reply to Dragonclaw103:
Hello,
I think it's dangerous to let the permission to use lp to players. Personaly I would do this :
/svs add <server> lp user <player> parent set member
/svs add kits member
/svs add <server> eco give <player> 500
/svs setpermission default
Hey Guys,
any ideas how I can get a command longer the chat allows onto a server sign?
It's a specialised /give command I would like to use!
Thank you for any suggestions!
In reply to JanJB99:
svs import <commands file>
In reply to JanJB99:
write it out in notepad, then copy and paste
Hello!
I have a problem. Non-Ops could not use the server-signs. Which permission is needed to fixx it?
Thanks if you could help me.
In reply to derschredder05:
serversigns.use i think, check the wiki
Hey there, I'm trying to make it so when you right click a sign it assigns you a group. I've got it working, however it only assigns the group in the world and not globally. I'm using luckperms. Is there a way around this to make it assign the group globally?
In reply to inygma_:
Hello :)
The permission set with luckperms is available for all the worlds.
By globally you mean in the worlds of current server or you are using bungeecord and all worlds are split between multiple servers ?
In reply to Forge_User_91135652: I just mean the worlds on the current server, I am not using bungeecord. Like they don't apply in the Nether or End, only in the overworld(or whatever world the sign is in).
In reply to inygma_:
Which command did you try with serversigns to achieve the group assignment ?
When you do the luck perms command yourself all works as expected ?
In reply to Forge_User_91135652:
/svs add <addgroup> GroupName
assigns a group ONLY in the world they are currently in
and when I do
/lp user username parent add groupname
it assigns it globally.
In reply to inygma_:
Hum after searching in code it is a normal behavior, the plugin use vault to add a player to a group and vault use per world groups. Maybe an evolution to allow to choose the world can be a good idea.
For a quick solution, you can maybe do :
/svs add <server> lp user <player> parent add groupname
In reply to Forge_User_91135652:
Thank you so much.