Need help? Ask on the forum, ask a fellow user or developer (join us on IRC), or contact sk89q.
Contribute to the wiki, edit this page! Register an account, or login with Facebook first.
HEY! Do you integrate (or want to) a plugin into yours? Do you help work on WE/WG/etc.? Please subscribe to our mailing list!
As a general rule, I will seriously attempt to NOT break your scripts from release to release. This is one of the reasons I wrote Command Helper to begin with, so there would be an abstraction layer on top of other less stable plugins, and bukkit itself. Having said that, sometimes a task was implemented sloppily, or inconsistently, and so the best course of action is to actually break a few things, in order to fix others. Having said that, any known breakages will be listed here, so that when upgrading, you can be aware of what things will break.
Upgrading from < 3.2.0 to 3.2.0
You will need to delete the persistance.ser file one last time. This feature has been relatively unstable in the past, but is now fixed permanently. For more information about this, see the Persistance page. This feature is very stable now, and it will be very unlikely to change in the future.
Upgrading from 3.1.0 to 3.1.1
The repeat command "/." now requires the user to have permission (commandhelper.repeat). This gives the server admin finer grained control of the plugin, and in fact allows all functionality of the plugin to be removed, through settings and permissions, making this a fully configurable plugin.
Upgrading from 3.0.2 to 3.1.0
All user aliases and stored values will break. :( The only solution to this is to delete the entire storage database. Unfortunately, there was no way around this. In future versions, I will make it so this will never happen again. To do this, simply delete the persistance.ser file in the CommandHelper directory.
Upgrading from 3.0.1 to 3.0.2
There should be no issues upgrading your scripts.
Upgrading from 3.0.0 to 3.0.1
The run function was changed, so that commands are input the same way as the runas function, i.e., there is a slash at the front of the command. If you have scripts that look similar to the following:
/... = run('give user 1 1')
you must update them to look like this:
/... = run('/give user 1 1')
This change was done to standardize commands, so that run behaves the same way as runas.
Upgrading from 2.* to 3.*
As the plugin was completely reworked, all scripts defined with the old syntax will completely break. 3.* series is essentially a new plugin, and support for 2.* will end after Bukkit 1.5.