Skip to content
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

TnT Blows Up signs attached to memory stones. #16

Open
ryantheleach opened this issue Oct 15, 2011 · 5 comments
Open

TnT Blows Up signs attached to memory stones. #16

ryantheleach opened this issue Oct 15, 2011 · 5 comments

Comments

@ryantheleach
Copy link
Contributor

tnt will blow up signs attached to memory stones, but not blow up memory stones.

I was expecting the memorystones and signs to be protected from non permission players and all other forms of destruction.

@ryantheleach
Copy link
Contributor Author

All explosions destroy any part of a memory stone, not just the sign.

@CmdrDats
Copy link
Owner

Strange - StructureBlockListener:49 should handle protection for the structure itself, cancelling the explosion. I can see the sign being affected though, if the explosion doesn't touch the actual stone structure though - will have to fix that.

I'm also not entirely happy with having to cancel the entire explosion, would prefer everything else around it to blow up, just not the structure, but I don't know of a workaround - I can't just replace the structure after the event because it might yield the materials for the structure, not great :P

@ryantheleach
Copy link
Contributor Author

I've been looking around the java docs and I believe all we would have to do is edit our blocks out of the blocklist of the explosion.

The real trick is to make this listeners priority really really early, so plugins like creeperheal don't freak out.

@CmdrDats
Copy link
Owner

oh, nice :) that's handy to know! ye - hope that no one puts theirs really high :P

@ryantheleach
Copy link
Contributor Author

High as in early or late? that's always confused me, I prefer to think of it as being called early on or late as events can be cancelled and even un-cancelled several times if there is enough plugins :S

I personally hope CreeperHeal is using the MONITOR lever priority as that's supposed to be read only and happens last to see the results of anything before it however I don't know enough about how the bukkit events work to see where the priority is set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants