KnightOps

Version 1.3.4

Fixed an older raid subgroup enforcement system that could still re-apply imported RaidHelper group assignments after officers manually rearranged players during live raid setup.

KnightOps now fully respects human raid pivots after a player has been initially placed into their planned group from the imported composition. Initial JSON placement behavior remains intact, so players will still be automatically placed into their intended subgroup when first joining the raid.

Rejoin behavior has also been preserved intentionally. If a player fully leaves the raid and later returns, KnightOps will treat that as a fresh join cycle and place them back into their planned subgroup from the imported comp.

This resolves cases where players could unexpectedly snap back into their original imported groups during roster updates, reconnects, or late-raid adjustments.

Internally, older continuous subgroup enforcement logic was removed in favor of the newer one-shot placement system already used by Tractor/listening mode behavior.