You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
combat processes actions in order from [auto_combat_default_stage1.ash] to [auto_combat_default_stage5.ash],
instakills and other instant combat enders are in stage2, most special combat actions are in stage4,
so if instakills are available, special actions can not be performed unless stage2 is skipped under the same conditions used in stage4, as of now this is only done for sniffing, not for other actions like copying.
Under the current combat structure stage2 would have to duplicate most of the code in stage4 to know when not to end combat, stage4 script can't just be run to check for returns because running it would mark skills and items as used
The text was updated successfully, but these errors were encountered:
Yeah it's a horrible "architecture". My suggestion when this was being worked on was to separate it into 2 chunks.
Chunk 1 would be stuff that doesn't end the combat like special actions. Chunk 2 would be anything that (potentially) ends combat such as insta-kills & spells or attacks etc.
Does anyone listen to me? I only have 2 decades of experience building systems. What do I even know about software anyway?
combat processes actions in order from [auto_combat_default_stage1.ash] to [auto_combat_default_stage5.ash],
instakills and other instant combat enders are in stage2, most special combat actions are in stage4,
so if instakills are available, special actions can not be performed unless stage2 is skipped under the same conditions used in stage4, as of now this is only done for sniffing, not for other actions like copying.
Under the current combat structure stage2 would have to duplicate most of the code in stage4 to know when not to end combat, stage4 script can't just be run to check for returns because running it would mark skills and items as used
The text was updated successfully, but these errors were encountered: