The client contains multiple UI generations. Identify which framework owns the target screen before choosing hooks, resources, lifecycle events, or input behavior.
Primary ownershipThe active view or window instance
Readiness anchorFramework-specific view creation and destruction
Version sensitivityVerify private names per client build
Framework comparison
| Framework | Typical shape | Primary integration surface |
|---|---|---|
| Classic GUI / Scaleform | Older lobby and battle views | Python view classes, Flash resources, GUI roots |
| Wulf | Modern Python-driven windows | View classes, view models, windows and dependency services |
| Gameface | HTML/CSS/JavaScript interfaces | Resource maps, generated models, child views and browser DOM |
Identify the owner
- Find the view alias, route, window class, or visible DOM marker.
- Trace who creates it and which application owns it.
- Find the model or controller that supplies its data.
- Resolve the current route or layout identity from that owner; mode-specific surfaces can use a different layout from the default mode.
- Observe its destroy path and input ownership.
- Choose the smallest extension point beneath all desired entry points.
Read by topic
Choose a focused chapter. Complete examples and reference details are preserved on their topic pages.