moe-battle

name

moe-battle

description

Use when editing the 14th_ua MoE Calculator's IN-BATTLE live-MoE overlay — how it is hosted as a registered Gameface window over the HUD, its arena lifecycle, the Alt-key peek mode, the BattleMoEVM channel, the combined-damage/EWMA math, the Counted Assistance third row, the MoEBattle.js/.css/.html DOM, its colours/font/checker backdrop, or the window placement/anchors. Overlay visibility is settings-gated — see moe-settings. For the hangar bar see moe-garage. For the two OTHER centre-screen transient battle windows — the Progress Bar (Moving Average) and the Damage Efficiency bar, and the shared MoEBarTransient.js/BarHost they ride — see moe-progress.

MoE Calculator — in-battle overlay (feature)

A live combined-damage / projected-MoE readout floated over the battle HUD. Reusable patterns: wotmod-gameface-widget (front-end), wotmod-architecture (Python + references/game-api.md "Battle HUD / efficiency"), wotmod-debug-repl (live probing). All paths under src/res/.

Hosting model (the hard-won part)

You cannot gf_mod_inject a garage-style sub-view overlay into the battle HUD: there is no shared full-screen Gameface document — each WG battle Gameface view is Flash-composited at its own placeId. Instead the mod registers its own view and opens it as a window:

• Register — src/res/mods/configs/res_map/MoEBattleView.json (itemID "MoEBattleView", impl "gameface", points at MoEBattleView.html). Ships inside the .wotmod. Adding it triggers a one-time client restart the first time OpenWG's ResMapManager rebuilds res_map.json.
• Resolve layoutID — bridge/battle_view.py via (deferred; until validated at client start, resolved before any battle).