Bukkit

@nathanaelps Better late than never :)

Your suggestion as is unlikely to be included as I really only wanted this plugin to be a bridge between the user and other plugins. It is (in my opinion) up to the other plugins to decide under what circumstances players can use their commands, and to check whether certain requirements are met, the command is correctly structured, etc.

What this means is that GUI Creator only runs one real line of code, which is player.chat(command); I.e. it just simulates the player typing the command in the chat window. If I start adding bits of code I run into problems when other plugins update, or I could let players access commands that they shouldn't, etc.

This also means that in your example, your economy plugin should do that for you if the player doesn't have the money to perform the command.

However, I did today add the possibility to hide screens and controls if the player lacks the funds which should at least give a visual indication that the screen/command is currently unavailable. Although now I think of it it would probably be better to disable the buttons rather than hide them.

@Heartless49 I should be updating the tutorial later on tonight. I don't actually use the plugin myself so I tend to forget what I added recently :)

The reason your temp_permissions doesn't work is that it needs to use the YAML list syntax (as more than one permission can be added). So it should look either like this

...
command: /command ^variable^
temp_permissions:
- bukkit.command.op

or like this

...
command: /command ^variable^
temp_permissions: [bukkit.command.op]

I prefer the second myself but YAML parsers understand them both.

Additional permissions can be added like this

...
command: /command ^variable^
temp_permissions:
- bukkit.command.op
- second.permission

or this

...
command: /command ^variable^
temp_permissions: [bukkit.command.op,second.permission]

This is the same for all plugins, by the way, as it's built into YAML.

1.3 is up - direct link

Changes

• Fixed the error caused by kicking yourself (or any player) while the GUI is open
• link_buttons will now not link to screens the player doesn't have permission to see
• Added a new key to screens and controls - show_funds
  • Set this to the minimum funds a player must have to see the screen/control
  • Requires Vault installed to work
  • Must be an integer
  • Will be overridden by show_permission and hidden
• Added a new key to command buttons - cost
  • Set this to have this much money taken from the players account when they click the button
  • Must be an integer
  • Can be a minus number to give players money for using it
  • There's no way for the plugin to tell if the command was successful so money will be taken even if the command fails

@burtthaman I don't quite understand what you're asking. I think you mean that you would like to use the GUI screens created but not the GUI plugin itself?

95% of this plugin deals with auto-layout and hiding/showing controls. If you want to create a static GUI for another plugin it's far easier to just make your own with Spout.

@Seweiwer Thanks. I know what's causing that. I'll fix it later tonight.

@ZeroX4 It will be the default value (whichever is set to selected in the screen file). There's no easy way to get the information from the server to decide which radio_button to select when the GUI is opened.

@ZeroX4 Sorry, I misunderstood your earlier post.

There's no way for the radio_buttons (or any other controls) to reflect the actual state of the server so it wouldn't be able to tell you what you were disguised as.

In usage it's the same as other controls. The button gets the value from it and adds it to the command - clicking the radio_button doesn't execute a command.

@ZeroX4 Yes, that's how it works. /md ^0^ (or ^1^, etc.) Probably easier with a slider though.

The order of the buttons at the top of the screen is taken first from the filename and then from the order within the file.

If you want to enforce a specific order you can either rename the files (as suggested below) or move all the screens into one file, in whatever order you want

screens:
- text: Nr 1
  controls:
  ...
- text: Nr 2
  controls:
  ...
- text: Nr 3
  controls:
  ...

As for radio_buttons, an explanation is here. The group key is what ties the radio_buttons together (as they can be placed anywhere on the screen), and is used to ensure that only one radio_button from each group can be selected at any one time.