Bukkit

Any deposit chest I create in a different world than the main world, gets reset to normal chest on a server restart.

All chests on the main world (the one in server.properties) persist. Any deposit chest in any other world just stops being a deposit chest.

Any ideas?

CB 1337, newest webshop, and Multiverse for multiworlding.

Exote, did you get a chance to look at this?

Do they work until the restart as normal?

@Exote: Go

Yes.

Mailbox signs also persist through a restart, only the chests stop 'being'

Do they get added to the database?

@Exote: Go

Allright, that's what I did:

1. Go to secondary world, place chest, /wa deposit set
2. Check phpmyadmin - the chest was in the database
3. Try to deposit things in chest - works
4. Restart server
5. Chest is still in database (!)
6. When using the chest - no message about it being a deposit chests appear. It behaves like a normal chest
7. When destroying the chest, it gives the WA removed message (!)

So for some reason on a restart, the chest stops working like a normal deposit chest, despite being in the database. All other chests in the spawn world work normally.

Could it be that the world is loaded after WebAuction?

@Exote: Go

Checking my startup logs - WebAuction does start before Mutiverse.

Now, I either edit the plugin.yml myself to make it depend on Mutiverse-Core, or you include sth. like xWarp has and other plugins, that it 'reloads' itself when new worlds being loaded are detected (xWarp disables warps if it doesnt detect the according world on startup, but once its loaded it enables the warps).

This would stop WebAuction from 'disabling' deposit chests in secondary worlds, or?