Vault 1.2.26 VS Bukkit 1.5.2 R1.1
Dimantchick opened this issue · 9 comments
Use many plugins. Have Essentials (economy not used) and CraftConomy3
In this build vault hook Essentials Economy. Downgrade to 1.2.25 vault find CraftConomy and use it (normally as later)!
you're saying CraftConomy is not being chosen over Ess eco? Also what version of CC3 are you using? @greatman updated the hook and it may require an update.
Yeah. Didn't release 3.1.4 yet (Soon tho!) so the new Vault version won't hook with current Craftconomy (3.1.3)
@greatman - I thought it was still linked? did you patch something out?
Use craftconomy 3.1.3 last from bukkit.org
I view you already understand what wrong and fix it. Thank you for support.
15.07.2013 0:06 пользователь "Nick Minkler" [email protected]
написал:
@greatman - I thought it was still linked? did you patch something out?
—
Reply to this email directly or view it on GitHub.
@Sleaker It's because of my new method loading that I had to change some stuff.
@Dimantchick Just run 1 version earlier of Vault for now. Should be fine until I officially release the 3.1.4 version.
@greatman - did you change something in 3.1.3? cause the whole point of having a seperateCraftConomy3 economy class was to still allow the old version to load properly.
I already use vault 1 version earlier.
For more information. Last vault loading first (start server, loading some
plugins, loading vault, another some plugins, craftconomy ...) Maybe vault
not see craftconomy because it not loaded yet, and think that I use
essentials economy. Don't check later (then server fully start).
Sorry for bad English. Write max information as can.
15.07.2013 6:01 пользователь "Nick Minkler" [email protected]
написал:
@greatman https://github.com/greatman - did you change something in
3.1.3? cause the whole point of having a seperateCraftConomy3 economy class
was to still allow the old version to load properly.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/434#issuecomment-20945687
.
@Sleaker It's just my JavaPlugin class that changed path so Vault weren't detecting it properly. Did that because I externalized all my whole server wrapper stuff.
@greatman - ugh. :-/