Bukkit

@sammyturbo123

Sorry to hear that, the latest release of this plugin only officially supports CB 1.5.2 R1.0, but i'm working on updating/rewriting features/fixing bugs still right now.

I've almost got a working version, so I may update soon, but without the quest buttons and some mob related stuff implemented for now, I may just make my quest button idea into a whole-nother plugin. I have quite a few bugs to work out still, and some documentation to write for new features. Sorry for the long wait between versions lately, these bugs are hard to work out for me since I'm still a bit of a novice coder.

For those of you waiting for a 1.6.2 update, It may be awhile before it is released, i am in the middle of re-writing a majority of the features, as well as writing new features, i'm sorry for any inconvenience this will cause, but i assure you that ButtonsPlus 3.0 will have some very nice new features! Thank you! :)

@robbie0630

If you do not have more information than "It stopped working" I'm afraid i cannot help you. Sorry.

@TangoSucka_

It would be buttonsplus.alltypes.push or buttonsplus.alltypes.create

Most of the permissions have a .push, and .create permission node

@TangoSucka_

Permissions are working fine for me with group manager, and i use default bukkit permissions so any permissions plugin should work just fine.

First things first, if you want a player to be able to interact/create buttons, they have to have permission for each button type, such as buttonsplus.STONE_BUTTON, buttonsplus.WOOD_BUTTON, or buttonsplus.STONE_PLATE. You can also give them the permission buttonsplus.alltypes for any type of button.

Next, you need to give them push and create permissions for each action and button mode you want them to be allowed to use/create, so if you had a group for someone who just joined the server you would probably only give them something like this:

Newb:
    -buttonsplus.STONE_BUTTON
    -buttonsplus.info
    -buttonsplus.text.push
    -buttonsplus.command.push

And for a group that can create simple buttons:

Member:
    -buttonsplus.alltypes //allows all types of buttons[button/pressure plate/lever]
    -buttonsplus.info //allows a user to see info on a button
    -buttonsplus.push //allows a user to push any action or mode of button
    -buttonsplus.basic //allows a user to create basic buttons
    -buttonsplus.text.create //allows a user to create text action buttons
    -buttonsplus.cooldown.create //allows a user to create cooldown in buttons
    -buttonsplus.heal.create //allows a user to create buttons that heal

Hope that helps! :)

@TangoSucka_

Let me fire up a 2.4 test server and figure out whats wrong here, i think i may have messed up a couple of things in the plugin.yml

OK, so i have some awesome new ideas for new actions and button modes, and some of my features need to be rewritten in order for this to work.

Here is my todo/planning for beta v3.0 of buttonsplus:

• Fix item issues.
• Implement new config settings.
• Rewrite actions.
• Rewrite mob spawning for skeles/armored/baby mobs.
• Rewrite the way charge mode works, so that it asks what the player wants to charge, instead of a single way set in the config.
• Quest mode for buttons.
  • Quest button idea[s]:
    • type 'quest' for mode when making buttons
    • asks for button name, has to be specific to button [ex: if your 'quest' is to get some wood, then the name might be 'chopwood']
    • asks for pre-requirements [Money|XP|Items|Quest completed] [ex: if this is the first quest in a quest line, then no requirements, but if this is the quest button that comes after cutting down wood you would put in that 'chopwood' needs to be completed for this button to work.]
    • asks for 'pre-quest' actions [Actions that will happen if requirements are met e.g: text display that tells them to chop down 5 logs, then gives them an axe, and then tells them to press the button again to continue]
    • asks for quest completion requirements [Money/XP/Items/Quest completed] that the player needs in order to complete the button-quest. e.g: the completion req for 'chopwood' would require 5 logs to complete]
    • asks for quest completion actions(rewards) [e.g: after the player completes 'chopwood' he gets a promotion to 'player', or maybe gets some iron, and then the button tells them where to go next]
  • you should be able to chain quests together.
  • you will be able to have multiple req, actions, and rewards.
• Block action. Both protected and unprotected
  • Block action ideas:
    • This action will toggle a block in the world.
    • This will be an OP-only action, cause it has a lot of grief potential.
    • The Player who is creating this action will be given a tool to pick which block they want to toggle and the button will save the location and what the id of the block is.
    • Buttons,Levers,Pressureplates, and any block that has metadata will not be supported most likely.
    • When this action is called, it will check if the block is there, if it is it will remove it, and if it is not, then it will place it.
    • This will allow gates/walls to appear out of thin air, and will also allow for resetting of arenas[e.g: spleef arenas or mob trap quests.

I'm also setting up a small bug-test server for alpha/test versions of my plugins, if you would like to join me later when its all set up, PM me your MC username and i'll PM you when its up and running :)

If you have any comments or suggestions, please give them to me!

This update will probably be under development for quite awhile, so be patient, and bear with me.

Version Beta[2.4] awaiting approval

• Added a new scoreboard feature, /bpinfo [playername]
  • putting in the command /bpinfo will toggle the scoreboard for the player inputting the command, or a specified player who is online.
  • when bpinfo is enabled, any button that is a(n) buttonsplus button displays pushes and cost when looked at.
  • Permissions: buttonsplus.bpinfo
• Added protection to blocks that buttonsplus buttons are on. [Fixes: This ]

@soccerstrike917

First of all, you should not be able to break a button normally, second of all you have to crouch + break the button in order to delete it, I'll investigate further later when I get home.

Edit: I just realized you meant the block that the button is on. I'll figure something out