-
Notifications
You must be signed in to change notification settings - Fork 737
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
Explosive events, fix #3104 #3106
Conversation
defuse and explodeOnDefuse
👍 Looks good |
👍 |
shouldn't it be placed/defused/explodedOnDefuse ? 😄 |
It appears some listenable events are listed here this would probably need to be added there. But there is both past tense and current tense words used in the events listed there so probably either naming scheme is fine but we might want to be consistent at some point. |
@CorruptedHeart This list is generated with a script, events should be added to module-specific framework page, they get pulled into one big list on events framework page then. |
Alright, I guess we still need to have a discussion about whether to keep them named like they are now or past tense. |
I was always thinking that those that are there to signal that something happened (listenable) are named in past tense, and those that can be used to perform a certain action (callable) are like those in this PR. |
Agree with @jonpas. |
Is it possible to provide that event that @Cuel was speaking about? |
It would be tricky, cause it would work with explosives detonated by remote control, but not for those that explode because of proximity, being damaged, etc. IMO it's not worth it with this limitations. |
When merged this pull request will:
defuse
andexplodeOnDefuse
_unit
to place eventCan be tested with: