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

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

  1. Offline

    Fluff

    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

    Source

    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

    ostepop2211

    I was just wondering:
    How can u write long commands (some commands take up more space than 1 line) on a command sign?
     
  3. Offline

    MG127

    Code:
    2011-08-31 10:35:31 [INFO] [CommandSigns] 0.9 enabled.
    2011-08-31 10:35:31 [INFO] CommandSigns: Integrated with Permissions v2.7.7
    ...
    
    2011-08-31 10:35:33 [INFO] Done (0,381s)! For help, type "help" or "?"
    2011-08-31 10:35:59 [INFO] ! CommandSigns Error: Couldn't find the permissions file!
    
    i'm using permissionsbukkit 1.2 with superpermbridge 1.2

    permissions.yml
    Code:
    server.mod:
        description: Advanced permissions
        children:
            dc.warp.*: true
    ...
    
    permissionsbukkit\config.yml
    Code:
    groups:
        Sign:
            permissions:
                server.mod: true
            inheritance:
            - user
    users:
        '&CommandSigns':
            groups:
            - Sign
    
    if the player has dc.warp.self.*: true the "/@warp blah" works, but if he doesn't have the permission it doesn't work
    every time i hit the sign without the permission to warp i get
    [INFO] ! CommandSigns Error: Couldn't find the permissions file!

    i looked through the source and can't even find this error xD
    does the plugin access the permission-file directly? ... bad idea

    it worked fine till now on cb1000 and permissions 3.1
     
  4. Offline

    wesmou

    hello

    I do not know what's going on
    but the plugin worked right
    but when a User of another group can not use the commandsign
    the admin group can use the commandsign
    put the permisao commandSigns.use
    but still not working

    Can someone help me?

    thanks
     
  5. Offline

    Showhung

    Hello i try to set permissions with this plugin and i have to ask
    /*command /permissions player setperm <NAME> ... ...
    or /*command permissions player setperm <NAME> ... ...
     
  6. Offline

    niugnip

    /*permissions player setperm...
     
  7. Offline

    Showhung

  8. Offline

    Imm0rt41

    i had an idea for this, how about adding to this the ability to activate commands by hitting levers or buttons or plates? like you can look at a button/lever/plate, type /commandsigns set *command* and then when ever the thing is activated, it also activates the command. i just think that would be a really kewl feature, thx
     
  9. Offline

    gsand

    A mix of this plugin and the "Annotate" plugin would be the best thing ever
     
  10. Offline

    Imm0rt41

    dunno what annotate is, but i just found out the plugin im looking for already exists. its called triggercmds
     
  11. Offline

    gsand

    This plugin is more powerful than that. That's why I use it. It's awesome.
     
  12. Offline

    Imm0rt41

    yea, but i cant use levers or pressure plates with this, now can i?
     
  13. Offline

    niugnip

    Yes. Use Annotate :D
    Read description!
     
  14. Offline

    Imm0rt41

    grrrrrrrrrrr
     
  15. Offline

    niugnip

    "grrrrrrrrrrr" thanks
    or
    "grrrrrrrrrrr" stfu?
     
  16. Offline

    Imm0rt41

    i dunno >.>

    rawr
     
  17. Offline

    gsand

  18. Offline

    fryedrice945

    please update to bukkit 1060 !
     
  19. Offline

    tehbeard

  20. Offline

    bastrian

    Please update to 1060 and add support for iConomy 6!
     
  21. Offline

    CraftLourens

    Decals can be activated with Redstone?
    (sorry for my bad english.I am from Russia =\)
     
  22. I have Permission 3.1.6
    And Default player has only the right to use the sign commands.
    I have give '&CommandSigns' all rights '*'
    And when i make

    [command]
    /@clear

    and a normal user will run the sign than he became a message that he have no permissions

    And when i make

    [command]
    /*clear

    than also work nothing and too for me
     
  23. Offline

    Joy

    Will you update this for 1.8? It is broken as it directly hooks into MC.
     
  24. Offline

    c_dric

    I hope there is a way to fix this one for 1.8

    The fork doesn't seem to work with plates/buttons at this time.
     
  25. Offline

    ladan208

    i don't know what to do with this just

    [command]
    /(command)

    ????
     
  26. Offline

    Jobi

    Yes it works like this, but i have an other question: How can I add costs for the signs? If I wont to have an /list command that costs 1$, what should I write?
    *sorry for bad english, i'm german*
     
  27. Offline

    niugnip

    Its like paying items, just with a "0" (Null) as itemid
     
  28. Offline

    Jobi

    can you write it as complete line of a sign with the command /list and 1$ cost
     
  29. Offline

    Jobi

    ok, now i know how to make it.
    Can someone say my why all of my command signs are klicked two times when i klick one time? (I dont know how to say this)
     
  30. Offline

    wolfen10

    any chance of this updating for bukkit 1185?
     
  31. Offline

    Danoth

    Fluff
    Last activity:
    Jul 14, 2011

    And his last commits to github were in June. This one looks dead guys :(
    Damn shame
     

Share This Page