Problems with 3.0

I found a bug/problem in version 3.0 of GoldBank in that when Mojang's servers were slow, GoldBank would be slow/broken. So, I removed it from BukkitDev, and immediately realized it was a mistake. Here's why: GoldBank's autoupdater will sometimes downgrade GoldBank to version 2.6.0 upon reloading if 3.0 is missing from BukkitDev when the plugin is enabled. Since 3.0 makes changes to the data structure, using 2.6.0 after updating would cause the plugin to pretty much stop working entirely.

If you've been experiencing severe problems and think your server may have downgraded GoldBank, please disable GoldBank until it is possible to update to 3.0 again. Additionally, it may be a good idea just before updating to delete data.db from the plugin's data folder (SERVER_ROOT/plugins/GoldBank) and rename data.old.db to data.db. This will eliminate any problems that may be caused by data inserted by 2.6.0.

In regard to the bug in 3.0: I'm working on it. but it requires that I execute any requests to Mojang's servers in an asynchronous (parallel) thread. This is really hard, because I can't make any calls to Bukkit's API in said async thread, or it might act up. So, I need to do a lot of tricky threading to make it work properly. It could take a while.

Anyway, I'm really sorry for any inconvenience caused by my screwup. I promise it won't happen again.

- Maxim


Comments

Posts Quoted:
Reply
Clear All Quotes