GUI Creator
Anyone who has been active on the main forums in the last few days must surely have already heard the news.
I'm not going to comment on why and how, but the short version is that Bukkit is almost certainly not getting passed this.
Consequently, the future of BukkitDev is very uncertain. Even if the legal matters were resolved tomorrow there isn't really anybody left to deal with file submissions anyway. There's no indication about how long the site will stay up and what will happen to the files.
Anyway, while I will continue updating and developing my plugins you will need to look for updates somewhere else, namely the wiki. I will be updating this wiki in the next few days to facilitate better communication (forums, email, etc.) and adding any documentation that's missing.
I will also, of course, be looking into porting the plugins over to whichever API emerges from the ashes!

GUI Creator
This is the successor to Admin GUI, featuring a simpler config but offering more powerful customisation!
How it works
Each screen is divided into ten rows, each having four columns (by default). Controls can be placed into any of these cells, and can span multiple rows and columns. It's also possible to set the exact x, y, width, and height values if needed. See the tutorial for more information.
Video overview
Tutorial
Available controls
- buttons
- text boxes
- checkboxes
- radio buttons
- textures (for images)
- sliders
- gradients
- labels
- spacers
- link buttons
Requirements
- SpoutPlugin
- Spoutcraft
Both of these can be downloaded here
Config
- open_screen
- set this to the id of a screen to have that screen automatically open when the GUI does
- make_player_skins
- set this to no to stop the plugin creating skins when players join the server
The rest of the config is used to change the default colours of things. Each value must be a string in the format r,g,b or r,g,b,a. Note that you can override these colours on any particular control.
Commands
- /reload_gui_creator or /rgc
- this will refresh the layout files if they have been changed since the plugin was started. The new screens will be visible the next time the GUI is opened
- /open_screen or /os
- this is an alternative to pressing the C key
- use on its own to open the GUI like normal
- use with a screen id to open the GUI directly to that screen
Permissions
- gui_creator.can_open_gui - controls whether the user can access the GUI. Default is false.
- gui_creator.can_reload_screens - controls whether the user can reload the screen files. Default is false.
Mac users
I've been informed that Macs have a very unfriendly behaviour of treating remote folders like local folders and creating hidden files on them. This has been causing the problems that I've seen come up a few times where the plugin is trying to read this hidden file.
I've fixed this from 1.6.7 but it you don't want to update, or you're seeing problems with other plugins, there are a couple of things you can do. One is to delete the file .DS_Store from any remote folders that are giving you trouble. Second is to follow the instructions here and stop the behaviour altogether.
Issues
- there are a couple of controls that are hard-coded in Spout so resizing them won't work as intended (mainly check_box and radio_button)
- this plugin is intended to be run full-screen, with GUI scale set to auto (see the previous point)
Like this and want to show appreciation? Send any unwanted TF2 items my way! id: coldandtired
-
View User Profile
-
Send Message
Posted Nov 25, 2012@jelliton All plugins show the loaded message so unless there was an error it must have loaded.
If you can't see the GUI there could be three possibilities - either there are no files in the screens folder; you don't have permission to see the GUI; or you're not using Spoutcraft.
-
View User Profile
-
Send Message
Posted Nov 25, 2012Doesn't Show any errors and I'm just assuming when it would load one it would say "blalalal Loaded" and it won't open with "c"
-
View User Profile
-
Send Message
Posted Nov 25, 2012@jelliton How do you know it doesn't load? Paste a full startup log please.
-
View User Profile
-
Send Message
Posted Nov 25, 2012It still doesn't load, I was using the example just to test it, and it didn't load.
-
View User Profile
-
Send Message
Posted Nov 25, 2012@jelliton Anything you like.
-
View User Profile
-
Send Message
Posted Nov 25, 2012I'm not understanding how to do this? What does the file have to be named in the screen folder?
-
View User Profile
-
Send Message
Posted Nov 19, 2012@yurikoma
I am very familiar with the mmo suite but thats not what i am looking for. there is also a plug-in for spout where yuou can move any of the default bars around on the screen. and for the custom objects Kaynide is the shit xD
-
View User Profile
-
Send Message
Posted Nov 19, 2012@Q2Lummox In that case the best way is to use permissions.
Give players who haven't made a choice yet a permission.
Create a screen with the required controls, and only show the controls (or the whole screen) to players with that permission.
When they have selected an option, remove that permission from them and they won't see the control again.
-
View User Profile
-
Send Message
Posted Nov 19, 2012@coldandtired
But what I want is that the user can only use the button only once, ie you press a button, and you can not push it back ever.
Continuing with the example I gave before, I want the player, when he joins the server for the first time, be able to join a job, pressing a button (actually "auto-moving" group). My intention is that once pressed the button for the job he has chosen, and can not ever go back to press that button (and therefore not be able to change your job).
This is possible with "radio_buttons"?, If so, can you give me an example "practical"?.
Thanks and regards.
-
View User Profile
-
Send Message
Posted Nov 19, 2012@Q2Lummox You should be able to accomplish this with radio buttons.
-
View User Profile
-
Send Message
Posted Nov 16, 2012Now that you've added this new option:
use_console: true/false
command: <command>
It would be possible to create a "group" of buttons the player can only push them just a number?, For example.
Button_groups:
max_selection_for_each_group: 1
groups:
Group_A:
- button A1
- button A2
- button A3
Group_B:
- button B1
- button B2
- button B3
Thus a player can press a single button for each group, for example:
jobs_primary:
- pex user ^gc_player_name^ group add miner
- pex user ^gc_player_name^ group add lumberjack
- pex user ^gc_player_name^ group add builder
jobs_secondary:
- pex user ^gc_player_name^ group add priest
- pex user ^gc_player_name^ group add farmer
- pex user ^gc_player_name^ group add fisherman
If you can make this possible, I would be very, very grateful.
A greeting.
-
View User Profile
-
Send Message
Posted Nov 15, 2012@Beatkidz
sounds like http://dev.bukkit.org/server-mods/mmoinfo/
this is how i made it look on my server, but it is completely customisable
NOTE: this pic was taken while showing my players some of the custom items i added, so ignore them :P
i shrank it so you could view it all, but if you want to see the full pic goto
http://i48.tinypic.com/347wndi.png
but yeah the top of the screen if how you can make it look. the possibilities are up to you.
also to the author of this plugin, maybe you could use that as a reference to making something awesome
-
View User Profile
-
Send Message
Posted Nov 14, 2012@Beatkidz Probably doable. This plugin tends to not need much maintenance (compared to Mobs!) so I always have to reacquaint myself with the code every time.
Shouldn't be too hard to divert a screen from the menu to the main screen and set a timer to update it.
-
View User Profile
-
Send Message
Posted Nov 14, 2012Would it be possible to make a "Screen" that was up all the time? I mainly just want to put graphics on it. maybe this "Screen" could possible update on damage/heal events. This would make it possible for us to create our own HUDS. our own currency displays, Health, possible damage to mobs. there is a lot of events that could update this screen. not sure if it would be stressful to server with all the updating or not. Thanks again
This man makes some of my favorite and best plug-ins for minecraft servers. His plug-ins are more of a tool. Great job and keep up the great work
-
View User Profile
-
Send Message
Posted Nov 12, 2012Update to b2.
Changes
-
View User Profile
-
Send Message
Posted Nov 7, 2012I installed "bPermissions" and have tried the following ways:
temp_permissions: [- bPermissions.admin]
or
temp_permissions: - bPermissions.admin
or
temp_permissions:
- bPermissions.admin
or
temp_permissions:
bPermissions.admin
or
temp_permissions: bPermissions.admin
or
temp_permissions:
[- bPermissions.admin]
or
temp_permissions:
[bPermissions.admin]
command: ^minero_u^;/world world;/user ^gc_player_name^;/user rmgroup Jugador
I says I have no permission to do that, or I get an error on the console (depends what you put).
Can you explain a practical example of how it should put this permit, so you can remove the player to press the button, a group "bPermissions"?.
And another thing....The alignment of the text does not work
Thanks;)
-
View User Profile
-
Send Message
Posted Nov 6, 2012@Q2Lummox Use ^gc_player_name^ to add the current player's name into a command/label, etc.
As for the temp permissions, it should be a list so temp_permissions: [1, 2, 3, etc.] or
<<code>>temp_permissions: - 1 - 2 - 3 - etc. <</code>I suspect the reason it doesn't work is because PEX is hacky. Bukkit doesn't use the wildcard for permissions so it very likely doesn't recognize it. Try switching to a better permissions plugin (like bPermissions).
-
View User Profile
-
Send Message
Posted Nov 6, 2012I'm trying to do, that when you press a button on the GUI, run a command to delete the player, that presses the button, of a group it belongs.
I want to run this command:
/pex user <user> group remove Test
I wonder if there is some variable to use where I wrote <user> to self-fill this field with the name of the person running the command.
e.g.
The player "Lummox" press the button "Delete Group". Then run this command:
/pex user {player} group remove Test
{Player} It should autocomplete the name of who runs the command, to delete it from the group.
Another thing:
I tried to take a temporary permit (/pex user {player} group remove Test) to a button like this:
temp_permissions:
- Permissions. *
I've also tried like this:
temp_permissions: [permissions. *]
And so:
temp_permissions: - permissions. *
---
temp_permissions: permissions. *
And I always say I have not permission to use that command.
Use the PEX plugin for permissions.
-
View User Profile
-
Send Message
Posted Nov 5, 2012Awesome plugin! .... will be updated?.
-
View User Profile
-
Send Message
Posted Oct 14, 2012@coldandtired
a few features (the GUI) dont work but thanks for spending youre time on it ;) it helped alot