Conversation
| //class Extended_HandleDamage_EventHandlers {}; // Not implemented yet | ||
| //class Extended_HandleHeal_EventHandlers {}; // Not implemented yet | ||
| class Extended_HandleDamage_EventHandlers {}; | ||
| class Extended_HandleHeal_EventHandlers {}; |
There was a problem hiding this comment.
Last time I checked, they ignored the return value. It was better to add handleDamage via init class event.
Does it work now? If not, don't enable these. It will only cause anger and confusion.
There was a problem hiding this comment.
Should HandleHeal be kept in script_component.hpp and script_xeh.hpp, or removed there as well? It was previously enabled there, just not enabled in config.
There was a problem hiding this comment.
Remove it.
If you want support for HandleDamage and HandleHeal in addClassEventHandler:
- make sure the RV is still ignored in current version
- if yes, make addClassEventHandler add a retroactive flag set init event handler that uses the addEventHandler command
Those would be removable by removeAllEventHandlers and removeEventHandler with hard-coded ehids, but anyone who uses the former is a terrorist and the latter goes against best practices (hard-coded or not), so is on their own.
This is a lesson in writing good comments.
There was a problem hiding this comment.
I'm worried about adding HandleDamage now
it's going to take a ton of testing to make sure it doesn't cause problems with old mods that may have used this
and to make sure that the return value doesn't override existing code
|
I've commented out/removed all instances of |
When merged this pull request will: