add-frontend-component

To wire UI overlays into a React game engine frontend, you route them through the engine to adapter to stores path, ensuring components render strictly from engine-provided state and dispatch actions correctly.

Gating UI overlays by playerId in multiplayer sessions requires routing the WaitingFor data shape through GamePage, ensuring overlays only render for the correct player based on strict game state derivation from the engine.

Adding a card choice modal to a React TypeScript game frontend involves integrating the overlay component with the engine-driven action flow, following documented patterns to ensure it receives proper WaitingFor data and avoids client-side data derivation.

Frontend overlays show inconsistent game state in multiplayer when components perform client-side data derivation instead of strictly rendering engine-provided state and adhering to exact WaitingFor data shapes.

Yes, you can use custom modals with engine-driven game state derivation by applying reusable component patterns that route through the adapter and stores, ensuring overlays dispatch actions without local state mutation.

Yes, you need a WaitingFor data shape to render targeting overlays in React, as it provides the exact structure required to gate rendering by playerId and ensure the overlay displays correct engine-derived state.