-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Probable bug with RuinGenerateEvent #86
Comments
After doing more tests, I noticed that the coordinates are actually correct. |
It does get called before the chest is generated. |
Is that intentional? Would it be possible to fire the event after the chest is generated? |
I suggest that you run a task after catching the generation that will then mess with the contents of the chest, using BukkitScheduler. |
That would be a possible solution, yes. Though I still think it is weird how |
Yeah, it is weird. |
When listening to RuinGenerateEvent to edit the loot inside the chests, I encountered some trouble. So I added some debug messages and I noticed how:
event.getChest().getType()
returnsMaterial.AIR
, I'd expect that it would returnMaterial.CHEST
So it would appear that event.getChest() is getting the wrong block.
Using Jenkins dev build: https://diabloplugins.ci.cloudbees.com/job/DiabloDrops/7/
The text was updated successfully, but these errors were encountered: