Inactive [MECH] CommandSigns v0.9 - Issue commands using signs [953]

Discussion in 'Inactive/Unsupported Plugins' started by Fluff, May 5, 2011.

  1. Offline


    CommandSigns v0.9

    Tired of having to type out the same commands again and again? Want to allow your players to use commands only at certain places? Help is at hand!

    Feature Summary
    • Allows chat commands and chat messages to be send on right-clicking a sign.
    • Allows commands to be run on signs that players wouldn't be able to use through chat.
    • Sign usage can be limited to specific players or groups.
    • Supports 'variables' for player name and x,y,z position.
    • Won't allow users to gain access to forbidden commands without permission (secure).
    • Add a cost to use a sign, or a reward for clicking the sign!
    • Limit the number of times a sign can be used.
    • Enable and disable signs without destroying them.
    • Permissions-friendly
    • Developer API available
    User's Guide

    About The Developers

    Want to ensure your bug or suggestion isn't lost in the thread? Post it on our issue tracker.

    Command Summary (open)

    • /commandsign enable - Enables the next command sign you right-click on.
    • /commandsign enable <x> <y> <z> - Enables the command sign at x,y,z in the current world.
    • /commandsign enable <x> <y> <z> [w:]<world> - Enables the command sign in world <world> at x,y,z.
    • /commandsign enable [a:]<alias> - Enables the command sign at the alias.
    • /commandsign enable <uses> - Enables the next command sign you right-click on with a number of uses.
    • /commandsign enable <uses> <x> <y> <z> - Enables the command sign at x,y,z in the current world with a number of uses.
    • /commandsign enable <uses> <x> <y> <z> [w:]<world> - Enables the command sign in world <world> at x,y,z with a number of uses.
    • /commandsign enable <uses> [a:]<alias> - Enables the command sign at the alias with a number of uses.
    • /commandsign disable - Disables the next command sign you right-click on.
    • /commandsign disable <x> <y> <z> - Disables the command sign at x,y,z in the current world.
    • /commandsign disable <x> <y> <z> [w:]<world> - Disables the command sign at x,y,z in world <world>.
    • /commandsign disable [a:]<alias> - Disables the command sign at the alias.
    • /commandsign alias - Right-click on a block to get the alias of its location.
    • /commandsign alias <x> <y> <z> - Get the alias of the location x,y,z in the current world.
    • /commandsign alias <x> <y> <z> w:<world> - Get the alias of the location x,y,z in world <world>.
    • /commandsign alias [a:]<name> - Right-click on a block to set the alias of its location.
    • /commandsign alias <x> <y> <z> [a:]<name> - Set the alias of the location x,y,z in the current world.
    • /commandsign alias <x> <y> <z> w:<world> [a:]<name> - Set the alias of the location x,y,z in world <world>.
    • /commandsign alias remove - Right-click on a block to remove the alias of its location.
    • /commandsign alias remove [a:]<name> - Removes the alias.
    • /commandsign alias remove <x> <y> <z> - Remove the alias at location x,y,z in the current world.
    • /commandsign alias remove <x> <y> <z> w:<world> - Remove the alias at location x,y,z in world <world>.
    • /commandsign alias [a:]<name> [a:]<newname> - Set the alias of the location at <name> to <newname>.
    • /commandsign config - Lists all the configuration nodes.
    • /commandsign config <node> - Lists the configuration node.
    • /commandsign config <node> <value> - Sets the configuration node to the value.
    • /commandsign exec [a:]<alias> - Executes the command sign at the location pointed to by the alias.
    • /commandsign exec <x> <y> <z> - Executes the command sign at location x,y,z in the current world.
    • /commandsign exec <x> <y> <z> [w:]<world> - Executes the command sign at location x,y,z in world <world>.
    Syntax Summary (open)

    • [command] - use on the first line of a sign to define a command sign.
    • **[title] - use on the first line in place of [command] to customise the title of the sign
    • /command - runs a command as the player using the sign
    • /*command - runs a command as the fictional user &CommandSigns
    • /@command - elevates the player's permissions (using the permissions assigned to &CommandSigns) if necessary to run the command
    • @player/group - commands following (up to the next @) are limited to that player/group.
    • \message - prints the message to chat
    • \\message - prints the message to the player
    • <NAME> / <X> / <Y> / <Z> / <I> - replaced with the using players name/x/y/z-coord/current held item id on running.
    • $;<cost1>[;<costN>] where cost is <item id>,<item number> or <item id>:<item data>,<item number> - adds a cost to the sign
    • $$ - break evaluation of a command sign
    Permission Nodes (open)

    • commandSigns.use - Use a command sign.
    • commandSigns.create - Create, enable, or disable a command sign.
    • commandSigns.super - Create, enable, or disable a command sign using /*command, /@command, @player/group, or $.
    • commandSigns.super.cost - Create, enable, or disable a command sign using $.
    • commandSigns.super.elevated - Create, enable, or disable a command sign using /@command.
    • commandSigns.super.fakeuser - Create, enable, or disable a command sign using /*command.
    • commandSigns.super.restricted - Create, enable, or disable a command sign using @player/group.
    • commandSigns.default.<default group name> - A flag stating that the group is the default group.
    • commandSigns.config - Allows a user to manage the configuration.
    • commandSigns.alias - Allows a user to manage aliases.
    • commandSigns.exec - Allows a user to remotely trigger command signs.
    Reporting a Problem (open)
    The following bits of information are helpful to include when reporting a problem:
    1. Bukkit and plugin version.
    2. Excerpt from server log of the failed command usage, preferably with the debug configuration option set to true.
    3. Complete command sign text.
    4. Command sign configuration file.
    5. Name of plugin that the failed command comes from, preferably with a link to the plugin's forum thread.

    Recommended Plugins
    • With Annotate, you can have CommandSigns on practically any block with an almost unlimited amount of room for commands! They can even activate when pressing a button or a pressure plate!
    • With ScrollingMenuSign, your signs can look even nicer while allowing your users to scroll through a menu of commands!

    Download Latest Version
    MD5: 7f4076eea7198f2c0f17cde3f62f7c1f
    Download 0.8.1i - RB 803 and previous
    MD5: 72a60e16bfd775b3d15a03aca70e86e0


    To Everyone Asking For Redstone Support (open)

    Yes, I also think redstone support would be very cool. Unfortunately, there are some major limitations on what you can do with a redstone-controlled sign. You can read about those limitations in this post, and you can read a rationale about why those limitations exist in this post. Given those two limitations, I don't think redstone support is currently a useful feature to add, especially given what Annotate can do for you. (If you disagree, please post on the issue tracker on how you would use redstone support.) In the (not too distant) future, redstone support may will be added in a separate plugin due to the different nature of redstone command signs.

    Change Log
    version 0.9 - See Post
    • If PEX permissions work, this plugin supports it.
    • Economy redone; added Essentials Economy.
    • Localization support added.
    • Added new command: /commandsign exec
    • Events properly unregistered when plugin is disabled.
    version 0.8.13
    • Default groups should work for real.
    Older Entries (open)

    version 0.8.12
    • Added handling for default groups.
    • Added support for command aliases.
    • Added /commandsign config.
    version 0.8.11
    • Fixed @ directive.
    • Fixed '/commandsign disable' bug.
    • Added aliases.
    version 0.8.10
    • Fixed /@ permissions error.
    • Added exception handling for removing permissions from users.
    version 0.8.9
    • Added PEX and Permissions 3.0 support.
    • Added new placeholders: <N> and <I>
    • Fixed bug with regular / commands.
    • Added new directives: $$ and \\
    • Added additional debug messages.
    version 0.8.8
    • Fixed /* and /@ working without permissions support.
    • Fixed Permissions creating new users with the wrong casing.
    version 0.8.7
    • Fixed command sign creation permissions.
    • Added debug configuration option.
    version 0.8.6
    • Added Permissions checks to developer API.
    • Fixed enabling bug with /* and /@.
    • Updated to work with GroupManager and fake Permission plugins.
    version 0.8.5 - See Post
    • Fixed multi-world Permissions bug.
    • Changed @ group directive
    version 0.8.4
    • Removed support for Permissions 3.x
    • Updated to 818
    version 0.8.3
    • Fixed API bug
    version 0.8.2
    • Updated for Permissions 3.x
    version 0.8.1
    • Fixed GroupManager integration
    version 0.8
    • Added /@ to temporarily elevate a user's permissions.
    • Added developer API.
    version 0.7.1
    • Fixed item data bug - for real, this time.
    version 0.7 - See Post
    • Removed SignReadMore support.
    • Added Annotate support.
    • Added more granular permissions for advanced sign creation.
    • Removed a debug message that looked like an error.
    version 0.6.2
    • Fixed enable bug on sign creation.
    • Fixed item data bug.
    version 0.6.1
    • Fixed berating of users who can't create command signs but were just innocently putting up a sign.
    version 0.6
    • Added SignReadMore support.
    version 0.5.1
    • Can no longer place blocks directly on enabled command signs.
    • Fixed @ directive.
    • Changed fake user network code.
    version 0.5 - See Post
    • Added /commandsign commands.
    • Added finite-use signs.
    version 0.4.10
    • Fixed BOSEconomy support
    version 0.4.9
    • Supports BOSEconomy
    version 0.4.8
    • Trimming commands in hopes it fixes some problems.
    version 0.4.7 - See Post
    • Added cost signs.
    version 0.4.6
    • Hackish solution to 'items not showing up in inventory' bug.
    version 0.4.5 - See Post
    • Updated support for GroupManager.
    • Added configuration option to change the display name of the fake user.
    • Added configuration option to allow command parser to understand // commands.
    version 0.4.4
    • Fixed numerous bugs when not using Permissions.
    • Beginnings of an API for other plugin devs.
    version 0.4.3
    • Added configuration file.
    • Fixed chat command bugs.
    • Rearranged code for simpler maintenance.
    version 0.4.2 - See Post
    • BREAKING CHANGE - The fake user is now named &CommandSigns.
    version 0.4.1
    • Fixed for 740
    version 0.4
    • Bukkit team trying to break everything again
    version 0.35
    • Fixed conflict when using <NAME> in commands overriding permissions.
    version 0.3
    • Added NAME, X, Y and Z variables
    • Added permission filter
    • Allowed creation of signs that call commands user would not usually have access to
    • Allowed customisation of [command] to other text.
    version 0.15
    • Bugfix ("Insufficient Permissions" annoyance bug)
    version 0.1
    • Plugin Released
    Dimochka, c_dric, Flipp and 5 others like this.
  2. Offline


    -.- i need this updated! the newer one doesnt work with annotate and doesnt support permissions 3.0
  3. Offline


    i use permissions 3.0 and it works fine for me!

  4. Offline


    He probably means the other one which is being actively maintained.

    To be honest though, it's probably for the best to start the process to change permissions provider. Permissions 3 is now unsupported and you'll be stuck in the future when it's relegated as a relic of history. You can use PEX which provides an excellent compatibility layer for the older plug-ins that only understand Permissions 2/3 and it's got a lot of native support as well as being able to provide SuperPerms bridging.
  5. Offline


    i dont think you understand, the new plugin doesnt even support annotate plugin and he has no plans of adding support. -.- its a total rewrite designed to work strictly and specifically for signs
  6. Offline


    And you're misunderstanding why I was talking only about Permissions. I understand that the other fork doesn't have the API which allows Annote to work. However, it's probably for the best if Permissions 3 is dropped from your server if that point is a sticking point in plug-ins. The sooner you get off Perms 3 the better and if you're worried about legacy plug-in support, PEX has that covered with its compatibility layer.
  7. Offline


    Ugh, looks like this finally died. An updated version is urgently needed as the "new" CommandSigns just doesn't work the same way as it stores all it's data in text files not on the sign itself (a pre-req for Movecraft).
  8. Offline

    Codex Arcanum

    Not sure if this is already known, but CommandSigns is broken in 1.8.
    Show Spoiler

    10:31:09 [SEVERE] Could not pass event PLAYER_INTERACT to CommandSigns
    java.lang.NoSuchMethodError: net.minecraft.server.ItemInWorldManager.<init>(Lnet/minecraft/server/WorldServer;)V
    at com.edwardhand.commandsigns.CommandSigns.runCommandString(
    at com.edwardhand.commandsigns.CommandSignPlayerListener.runCommand(
    at com.edwardhand.commandsigns.CommandSignPlayerListener.onPlayerInteract(
    at org.bukkit.plugin.RegisteredListener.callEvent(
    at org.bukkit.plugin.SimplePluginManager.callEvent(
    at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(
    at net.minecraft.server.ItemInWorldManager.interact(
    at net.minecraft.server.NetServerHandler.a(
    at net.minecraft.server.Packet15Place.a(SourceFile:57)
    at net.minecraft.server.NetworkManager.b(
    at net.minecraft.server.NetServerHandler.a(
    at org.getspout.spout.SpoutNetServerHandler.a(
    at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
    at net.minecraft.server.MinecraftServer.h(
  9. Offline


    @Fluff please update your great plugin, my server heavily relies on it :). The new one by some other guy is really not the same as your plugin. I miss ya Fluff, your plugins are sooo good!

    Jaiph likes this.
  10. Offline


    i will pay someone to update this, i am in desperate need of this plugin as soon as possible! i use it on my server to issue commands on blocks for guests to use to get out of the rules and into the word they can build in =/ but at the moment they are stuck in the rules and cant get out. my rules are very long and uses a series of commands attached to buttons to get the player to their destination
    Clem likes this.
  11. Offline


    How can I use annonate with this plugin to create signs with more commands?
  12. Offline


    you use /ann line1 [command]
    then /ann line2 /yourcommandhere
    then /ann line3 /yourothercommandhere

    etc, but this doesnt work in 1.8 because theres no update
  13. Offline


  14. i'll update this...give me a day or 2
    Clem, Linkolas, Jaiph and 1 other person like this.
  15. Offline


    You sir are awesome!
    Thanks for picking up this project!
  16. Offline


    I second this notion.
  17. Offline


    That's really awesome, I really need this plugin for our server! :)
  18. seems that this plugin needs annotations...CS got all bunch of errors when i look at the source and that goes for annotations too...its too advance for me but its doable if i try harder(still a bit noob myself)...and it also uses perms3 by yeti. i want to recode this and make it use the latest permissions such as PEX or the PermissionsBukkit or the bPerms(or i can use superperms, so it will hooked to all latest permissions plugin...but the problem with superperms is this will not support @groups, i think). i'll update the annotations too if it really needed(i think its needed). reply to this if you like the idea...if not...then tell me whats wrong with it
  19. Offline


    Please do update annotations, its awesome to make buttons that work like commandsigns.
    If you update this ill donate you some $
  20. Offline


    it will still be compatable with permissions 3 right? remember that i am still using this right now because pex doesnt seem to work properly at the moment for me due to some rather odd conflicts, and annotate is very much needed for the ability to create commandsigns on any block which is one of the main functionalists of my server, i am still willing to donate what i promised for this!
  21. Offline


    I'm similarly interested in Perms 2 compatibility. I refuse to update to broken, newer plugins.
  22. Offline


    Anyone that can update this? We would really be grateful!
    Our server really depends on it. :/

    I only need the commands on signs to work and add a fee on use to them (items, no iconomy coins)
  23. Offline


    Hello, everyone !
    I have made a Plugin that regroup Annotation and something like CommandSign in one plugin !
    I have totally rewrited it... so don't expect having you're old configuration file working with this...

    Also you'll certainly need to update to permissionsbukkit or PEX ! Perm3 is NOT supported and won't be supported !

    I will release it this week certainly ! it looks like everything is working, I just need to adjust some little things !

    Edit: I actually named it ScriptBlock... but if you have a better idea for the name ! feel free to submit it to me ; )
  24. Offline


    @Shereis Will this work with Groupmanager as this is my servers main way of ranking people, it also comes with essentials which makes it popular.
  25. Offline


    Actually not, first I have to release it be sure there is no issues, then release two another plugins i'm working on... maybe after that... sorry for that, but having "multi-permission" plugins support is not my first priority for now !
  26. Offline


    Where could I find this release?
    We really need a commandsigns plugin...
  27. Offline


    Well it's not really a Commandsign plugin ! it's, I think, better than that... because you can bind text, any command , or MANY commands !!(with, if you want, bypass permission system for the user ) to any blocks (signs, buttons, and levers includes !!)This will allowing you to write anything you want on the sign attached to the command !

    This plugin won't support economy plugins, but it will support script so, if you want a player to buy a Diamond for money with iconomy plugin just write "/sbcreate [@money grant <PLAYER> -75] [@give <PLAYER> diamond] " !
    then click on a block and voila !
    you can add another commands to a block with the "/sbadd ["commands"]"

    I will explain all of that better on the BukkitDev page !

    Actually i'm testing it. If everything is ok... I will post it on BukkitDev today or tomorrow, I think ... !
  28. Offline


    Thats what I really need actually!
    Im awaiting the release of this plugin!
    Thanks so much, and I think lots of people who miss this type of plugin do.
  29. Offline


    shame it wont support permissions 3, because i cannot get pex to work, bukkit refuses to enable pex and i have had no solution to the problem so far >.>
  30. Offline


    Permission 3 is no longer updated and future will certainly not support it... Have you tried permissionBukkit ? ( not the one include in bukkit, but this one : )
    if you add the plugin SuperPermsBridge, most of perm3 plugins will be supported by this one !

    Anyway, I will try to help you get PEX work, after I released ScripBlock ...
  31. Offline


    that will bridge my perm3 with permissions bukkit? do i have to edit perm3 in any way? which was why i wanted pex, if you can solve my pex issue then i would be very greatful

Share This Page