monarch-screen-setup

To manage Defold screens and popups using Monarch, you establish a single active screen using collectionproxy and stack popups via collectionfactory. This standardizes UI navigation and ensures safe closure using monarch.back() before runtime.

The best way to handle popup-on-popup scenarios in Defold is using Monarch with collectionfactory. This enables popup stacking and provides safe closure using monarch.back(), ensuring scalable UI architecture without runtime errors.

Yes, you must declare Monarch in game.project or have it present locally to set up screen routing. Verifying Monarch usage before applying the setup prevents misconfiguration and runtime errors during UI navigation.

Collectionproxy works with Monarch by establishing a single active screen at a time with a proper init flow. This mechanism standardizes UI navigation in Defold projects, ensuring only one screen is active during runtime.

Monarch screen setup causes runtime errors in Defold if screens and popups are not registered before runtime. Applying guardrails to verify Monarch usage and proper collectionproxy or collectionfactory configuration prevents these misconfiguration issues.

Yes, you can use collectionfactory for popups over a collectionproxy screen in Defold. Monarch orchestrates this by keeping the main screen active via collectionproxy while stacking collectionfactory popups on top with safe transitions.