Change package name of register, or use Register.jar as plugin about chestshop-3 HOT 4 CLOSED

That's not a ChestShop's problem, I use
com.nijikokun.register.payment.forChestShop
:)
And I'd rather recommend you to keep it in code.
BTW. Do you want to make some "linker" together? So the Showcases could be tied to ChestShops?

from chestshop-3.

Hmm maybe I'll switch it over again.
I'm currently doing Showcase 2 and I could also do a ShowcaseChestShopBridge which allows placing showcases on chestshops (the item would then spawn on the actual chest, no slab required).

from chestshop-3.

Yeah, this would be awesome :)
BTW, if you haven't read this, you should do now:
http://forums.bukkit.org/threads/43043/

This would mean that, for example, showcases/chestshops wouldn't need ANY database (even the flatfile) to work.
(I am rewriting the ChestShop too - it'll use custom events instead of hard-coded actions)

from chestshop-3.

I read that too. But I already switched to using YAML for persistence which is really easy and not buggy at all. I implemented the whole persistence within 30 minutes.
I always was against databases because they usually bog the cpu performance (h2 for example), or are hard to setup for users, also they make the server crash after 20 reloads (really!).

from chestshop-3.