- Joined
- Sep 6, 2013
- Messages
- 6,742
I've spent today to read much dds threads, and as far as I can see I think lfh's is my favorite of approved ones.
As I haven't coded or reviewed a DDS system, I'm also not really familar with the edge cases I need to care about.
As I see bracers and locust work with lfh's, were the tequniques considered?
I'm honestly not sure, but it made sense to me when I saw the DamageEx function that won't execute new events again, instead of manualy turning off one trigger and then turning it on again. Wouldn't it be good if the internal call just doesn't fire new events, or is it really that you avoid a new custom function, or do I miss something?
I like your personal style though, very much, and all seems very intuitive and modular. I think it's good.
As you use no damage timer 0 anymore I guess the GetLife native should in no cases be broken?
The bucket strucutre seems good, I think that's definitly a pro, too.
edit: code damage seems not supported, but could someone explain me why it's exactly relevant to get it?
As I haven't coded or reviewed a DDS system, I'm also not really familar with the edge cases I need to care about.
As I see bracers and locust work with lfh's, were the tequniques considered?
I'm honestly not sure, but it made sense to me when I saw the DamageEx function that won't execute new events again, instead of manualy turning off one trigger and then turning it on again. Wouldn't it be good if the internal call just doesn't fire new events, or is it really that you avoid a new custom function, or do I miss something?
I like your personal style though, very much, and all seems very intuitive and modular. I think it's good.
As you use no damage timer 0 anymore I guess the GetLife native should in no cases be broken?
The bucket strucutre seems good, I think that's definitly a pro, too.
edit: code damage seems not supported, but could someone explain me why it's exactly relevant to get it?
Last edited: