Build context
No build snapshot is attached to this visit.
Open workbench →A bounded experiment, not a buff simulator
This page tests independent weapon-switch removal predicates against disclosed hypothetical events. It does not activate a talent, remove a buff, calculate uptime, or change the existing build recommendations.
The target remains every build family: weapon, skill, status, hybrid, tank, healing, and team support. Live-patch availability is not established by the export.
Evidence snapshot
Loading verified session evidence…
Weapon-switch removal experiment
Choose an actual source declaration, then supply an example incoming switch. A true predicate is only one requirement, not permission to keep or remove a buff.
What is still unknown?
- Zero-valued parent polling: the schema does not say whether zero means every frame or something else.
- Omitted weapon-slot lists are not assumed to be explicitly empty.
- Event delivery, negative companion permissions, negation, combined groups, grace attribution and extra-frame order are not inferred.
- Actual removal, stacking, refresh and duration are not integrated into a complete combat simulator.