WorldEdit

[NiLSPACE]

*sniff first time deciding for a license Any recommendations?
How can I move it to the mc-server organization though?
EDIT:
Ok moved to mc-server

[xoft]

In the repo settings there's the "dangerzone" controls, you transfer ownership of the repo to mc-server. If you have any changes on your computer commit them first, because it's rather difficult to change the remote repo address, it's much easier to delete everything locally and clone a new fresh copy from the new location.

[NiLSPACE]

Too late Well I didn't make any changes yet so it's alright

[bearbin]

On the command line it's actually very easy to change the address:

Code:

git remote set-url origin git@github.com:mc-server/newrepo.git

[xoft]

For some reason I can still push through the old URL

[NiLSPACE]

Well that's usefull

[bearbin]

For some reason I can still push through the old URL

That's a new feature github added. When you move repos the urls point to the new one. I think you can omit the .git on remote URLs too as well now.

[xoft]

What if STR decides to fork the repo back to himself? Will I push to his (new) repo? Messy...

[bearbin]

Yeah, if he forks it back to himself you'll push to his new one

[xoft]

The basic structure of the Info.lua file is more or less settled now, the InfoReg.lua helper library will register commands and even subcommands properly. I've added an InfoDump.lua script into the Plugins folder, it will document each plugin for which it can find the Info.lua file. The WorldEdit plugin on InfoDump branch Gallery plugin on master branch have been updated so that they both take full advantage of the new architecture. You mentioned that there are other multicommands, not only "//schematic"; you can now update those in the Info.lua table. Also I haven't created separate handlers for the "//schematic" subcommands, you might want to split the HandleSchematicCommand() function into the two separate handlers. It should be pretty straightforward, if in doubt, have a look at the Gallery plugin.

I'm considering making and actual API function that will provide the functionality of InfoReg.lua, so that the file doesn't have to be copied to all plugins. That way, we could simply call for example: cPluginManager:BindCommands(g_PluginInfo.Commands), and it would bind all the commands and subcommands and call the proper handlers. However, if that is ever gonna be done, it will be later on, for now take advantage of the InfoReg file.