I affirm:
OS / platform the server is running (if known)
All - Server-side
Branch affected by issue
base
Steps to reproduce
I believe this break statement in the special dispel logic for the RDM Automaton is preventing all over enfeebles from occurring. When using the RDM head, notice ONLY dispels are used (when monster has something disableable active) and no other enfeebles are cast when their conditions are met (skill level, maneuvers, etc.)
Expected behavior
Stormwaker automaton is able to cast bio/dia/slow/paralyze/addle/distract/frazzle/blind/poison... etc. as on retail.
Fix
The break statement prevents additional logic from being run, so to maintain both the priority dispel AND the normal enfeeble list, I would suggest using a [[fallthrough]] statement instead.
I affirm:
OS / platform the server is running (if known)
All - Server-side
Branch affected by issue
baseserver/src/map/ai/controllers/automaton_controller.cpp
Line 751 in 19a6b35
Steps to reproduce
I believe this break statement in the special dispel logic for the RDM Automaton is preventing all over enfeebles from occurring. When using the RDM head, notice ONLY dispels are used (when monster has something disableable active) and no other enfeebles are cast when their conditions are met (skill level, maneuvers, etc.)
Expected behavior
Stormwaker automaton is able to cast bio/dia/slow/paralyze/addle/distract/frazzle/blind/poison... etc. as on retail.
Fix
The break statement prevents additional logic from being run, so to maintain both the priority dispel AND the normal enfeeble list, I would suggest using a [[fallthrough]] statement instead.