zinc-ui-async-separation

To prevent War3 UI logic from mutating game state, enforce strict separation between presentation and data layers, bridging local UI events to asynchronous syncing via a central bus instead of writing state directly.

onClick/onEnter/onLeave handle local UI interactions without data binding, whereas spClick/spEnter/spLeave manage asynchronous payloads by binding through eventdata to safely sync with the game state.

Bridge local UI events to asynchronous game state in War3 by routing them through a central sync bus using a mock payload contract, ensuring validation occurs during the onDataSync transition.

No, War3Lib UI async separation requires no external dependencies. It provides a reusable pattern with static async parameter slots and clear destruction rules built directly into the UI modules.

Mixing UI updates and state mutations in War3 creates blocking and non-deterministic behavior. Strict separation rules are required to keep the UI layer safe and ensure synchronization happens exclusively through a dedicated bus.

You need onDataSync validation for War3 UI components whenever bridging local events to the asynchronous sync bus, ensuring the payload structure is correct before any game state mutations occur.