Inactive [MECH] CommandSigns v1.2.0 - Issue commands using signs[1317]

Discussion in 'Inactive/Unsupported Plugins' started by HansAnderson, Aug 26, 2011.

  1. Offline

    HansAnderson

    CommandSigns:
    Version: v1.2.0

    This plugin is a complete rewrite of CommandSigns based off the original by Edward Hand. With CommandSigns, you can add invisible text or commands to signs. When the sign is right clicked, the command runs and/or the player gets a message.

    The /* feature of this plugin will not work properly with PermissionsExtended (PEX).
    There is a small issue where PEX doesn't utilize the permissions.yml from the root server folder.
    It has been tested with PermissionsBukkit and bPermissions.

    Features:
    • Run commands from signs
    • Signs can have any other text on them, the commands are linked to the sign behind the scenes
    • Uses a new permissions node so that players can use commands they wouldn't normally have access to!
    How to use:
    1. Place a sign, add any writing you want
    2. Add lines to your clipboard with /commandsigns line<number> <text>
    3. Right click a sign to make it a CommandSign
    Commands:
    Code:
    /commandsigns line<number> <text>
      - Add a line with one command (see Command Formatting). Number may be 0-9
    
    /commandsigns read
      - Read a CommandSign (the command lines associated with it)
      - Note: You need permission to create a sign in order to read
    
    /commandsigns copy
      - Copy a CommandSign to clipboard (the command lines associated with it)
      - Note: You need permission to create a sign in order to read
    
    /commandsigns clear
      - Clear your CommandSigns clipboard
    
    /commandsigns remove
      - Remove a CommandSign
    Command Formatting:
    In the place of <text> for a line, you may write a single command or sign formatting (such as @group). There are 10 total lines for separate commands or sign formatting. See Examples.
    Code:
    /command
      -  Runs a command from the player who clicked the sign
    /*command
      - Runs command with elevated permissions from the 'CommandSigns.permissions' node
      - Doesn't work for OP commands like /stop
      - (For WorldEdit //wand, use /*/wand)
    @group
      - Limits the sign use to only that group
      - **Check the permissions section below for usage!**
    \message
      - Print the message to the player's chat
    <NAME>
      - Replaced in the command by the player's name
    <X>/<Y>/<Z>
      - Replaced in the command by the player's x, y, or z coordinates
    Examples:
    examples (open)
    Code:
    /commandsigns line0 \say Hello server! <NAME> just logged on.
      - "Hello server! <playername> just logged on."
    
    /commandsigns line0 \You just clicked
    \commandsigns line1 \a sign!
      - "You just clicked
          a sign!"
      - (Message sent to the  player who clicked)
    
    /commandsigns line0 /*warp point1
      - Warps the player to point1
      - (If the /* nodes are set up correctly)
    
    /commandsigns line0 @mods
    /commandsigns line1 /*warp point1
      - Warps the player to point1 only if they have the 'CommandSigns.group.mods' permission node
      - (If the /* nodes are set up correctly)

    Permissions:
    permission nodes (open)
    Code:
    'CommandSigns.*'
      - All permissions
    
    'CommandSigns.create.*'
      - All create permissions
    
    'CommandSigns.create.regular'
      - Create signs without /* commands
    
    'CommandSigns.create.super
      - Create signs with /* commands
    
    'CommandSigns.remove'
      - Remove CommandSigns
    
    'CommandSigns.use.*'
      - Use all signs
    
    'CommandSigns.use.regular'
      - Use signs without /* commands
    
    'CommandSigns.use.super'
      - Use signs with /* commands
    
    'CommandSigns.group.<group>'
      - Replace<group> with the group name from @group
      - Allows use of signs with the matching group name
    
    'CommandSigns.group.*'
    - Allows use of all @group signs

    In your permissions.yml (in main server folder) create parent node 'CommandSigns.permissions' and attach children nodes from plugins you want to give permissions for when using the /* prefix.
    permissions.yml example (open)
    Code:
    CommandSigns.permissions:
        children:
            warp.go: true
    Now using /*warp <somewhere> on a sign will allow a player who doesn't normally have access to the /warp command to use the sign.

    Download CommandSigns
    Source

    Changelog:
    Version 1.2.0
    • Only one command per line now (commands can have many more syntax options)
    • Added ability to copy a CommandSign text to 'clipboard'
    • Fixed 'CommandSigns.group.*' permission node
    Version 1.1.0
    • Now supports all superperms permissions plugins!
    Version 1.0.1
    • Fixed a missing permissions node from the plugin.yml
    Version 1.0.0
    • Initial release

    I wanted the functionality of the old plugin, but the /* feature was broken. After becoming frustrated trying to figure out and update Fluff's version, I went back to the original and completely rewrote it. This is really my first plugin and Java experience.

    If this is not an acceptable submission, that is fine. I wrote it for my server and don't have time to go nuts adding features we don't need. However, I saw many people also wanted the /* feature, so I shared my work.

    I'm open to changing the name to something different, or withdrawing the submission. My main goal was to make this available to anyone who wants to use it.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 19, 2016
  2. Offline

    HansAnderson

    @desht
    I use a similar technique for elevating permissions. When I saw how to use the new permissions api, I immediately though of how much easier it would be (vs the method of creating a fake player). Just looked at your parser though, it's intense; lots of options. Nice work!

    @Seinna
    Costs are in the near future.
     
  3. Offline

    ItsQ

    Please add:
    That you can add a command on a button/presureplates/and levers.
    Like the old commandsigns.
     
  4. Offline

    MintTheFox

    any help with my issue?
     
  5. Offline

    NotYetRated

    I am using PEX, but with the permissions bridge. So all of my permissions are stored in PEX "permissions.yaml. file in the PEX directory... Does this work?
     
  6. Basic functionality works fine. There was a problem with the elevated commands being run (using /*), but I don't know if it's been fixed in the last few revisions of the plugin or not.
     
  7. Offline

    mrvertigo27

    @HansAnderson I have not tried this yet but im on the go and wondering if multiple commands are executed in seperately or in a manor that would let me do something like

    /money pay herobrine 50 (if true next)
    /*warp newplace
    /*i woodaxe

    and only isssue the whole sign if all conditions are met or execute as expected. I know im (borderline) talking about scripting but just wondering what current behavior is for multiple commands and if i could do something like this without scripting the command through sk89Q's commandHelper
     
  8. Offline

    NotYetRated

    Any chance on getting elevated commands working with PEX? I would love that functionality for my server...
     
  9. Offline

    UltraFaceguy

    So yeah, everything works great (mostly) and all and this is one of my favorite plugins... but...
    everything only works great until I close the console...
    For whatever reason the plugin doesn't save my commandsigns when the console is restarted! Anyone else getting this error? Any possible fixes? Help me as I am oblivious lol!
     
  10. Offline

    josip1

    Yeah this works fine for me but it does not like save the sign configuration when server is restarted etc

    Anyone know the issue?
     
  11. Offline

    waythm

    I'm having the same issue. All commandsigns lost on server reset.
     
  12. Offline

    jaboy

    since /* dont work whit PEX ... could you make a /! that means the console is doing the command ?!
     
  13. Offline

    S4h4rk

    You may want to check out http://dev.bukkit.org/server-mods/scriptblock/ for that kind of functionality
     
  14. Offline

    UltraFaceguy

    Three people with the same problem... MY GOD IT'S AN EPIDEMIC!
    But seriously, any word on a possible fix for the commandsigns not saving upon server reset?
     
  15. Offline

    waythm

    Would be wonderful if it could be fixed. I love this plugin.
     
  16. Offline

    UltraFaceguy

    I'm so lost without this...! ANY news on a fix..? Please..?
     
  17. As I understand the problem, it's not the character that is the problem, it's the method used to enable the command to run in an elevated state.

    However, according to the latest comments from the dev of PEX in the ticket I opened on this problem, it's been fixed (and supposedly confirmed) in the current dev version of PEX.
     
  18. Offline

    jaboy

    im not talking about "the character" or "elevated permissions" .... but letting the console/pulgin make the command
     
  19. Offline

    CalibeR.50

    Check Out "serversigns". I made this Plugin with support for commands in the console. I am going to add iconomy Support and custome permissions for choosen signs. More Features will be added on request


    http://dev.bukkit.org/server-mods/serversigns/
     
  20. Offline

    Brvtvs

    I like this plugin, it would be nice to have an alias for /commandsigns, it takes forever to type that in 90 times.

    maybe something like:

    /cms l0
    /cms l1
    /cms remove
    etc.
     
  21. Offline

    ElgarL

    This should work natively with the dev version of GroupManager. I've not tested it, but I did recently improve the bukkit perms integration within GM.
    http://palmergames.com/downloads/gmdev/EssentialsGroupManager.jar
     
  22. Offline

    Clockwork

    Escalated commands are not working.

    Contents of permissions.yml:

    CommandSigns.permissions:
    children:
    permissions.*: true

    Command issued for the sign:

    /commandsigns line0 /*permissions player setperm <name> FN:permissions.build

    The users are still getting "You do not have permissions to do that".

    CommandSigns.use.* is set in their group permissions too. We're using PermissionsBukkit.
     
  23. Offline

    SFXcraft

    Can you add economy v7 support and add a command to activate it or maybe a line n the sign saying the cost
    please
     
  24. Offline

    eHAce

    I need some help with power commands
    were do i put CommandSigns.permissions:
    children: warp.go: true
    ? in the main server file you say so is that just ur server file or server>\plugins>bukkitpermissions ?
    in that permissions .ym?
    allso in the permission file what is a parent?
     
  25. Offline

    Nexot

    permission node dont work on PEX, any solution :C? btw, very nice plugin!!
     
  26. The only thing that the 1.2 version of command signs has a problem with under PEX 1.16 is running an elevated command. Otherwise it's working fine (I use it).
     
  27. Offline

    Knorke

    To enable commands on other Blocks change SignClickEvent.onRightClick() method to take BlockStates instead of Signs and in the onPlayerInteract decide which Blocks are allowed. (See my fork of Commandsigns)

    Feel free to integrate this into your Plugin, maybe configurable through a config file.
     
  28. Offline

    hiro24

    Is there any chance that you can make it so commandsigns can be activated via redstone?
     
  29. Offline

    Kosyne

    I requested this feature to the other commandsigns author (and it got implemented), but as it's no longer updated, I'll ask again here:

    Can you add support for 'variables'?

    Example: The text on a sign reads as follows: /*warp <playername>_bank
    If the player 'Fred' clicked the sign, it would execute this command: /*warp Fred_bank
    Therefore, it takes 'Fred' to his bank, and if 'Bob' were to click it, it'd take him to his, all in one sign.


    Thanks for taking the time to read this, and hoping you'll consider implementing it. My bank needs it :p
     
  30. Offline

    bitWolfy

    I've got this really weird issue. I am using PEX for permissions, and I tried to set up an automated promotion sign using the following syntax:
    Code:
    /commandsigns line0 /pex user <NAME> group set Member
    It did not work, obviously. Instead of looking like
    Code:
    [Member] bitWolfy
    my username looks like
    Code:
    [world]<bitWolfy>
    Any ideas?
     
  31. Offline

    Magge

    How is this with bPermissions elevated commands?
     

Share This Page