gpb-debug-repl

name

gpb-debug-repl

description

Live in-client introspection for the Garage Progress Bar WoT mod via its debug TCP REPL — the specific debug package, tools, and probe snippets for THIS mod. Use whenever you need to inspect live game state, force a widget refresh, or debug why the bar isn't loading/updating in the running client. (For the generic probe technique and decompiled-source navigation, see the wotmod-debug-repl harness skill.)

Live introspection for the wgmod

Generic technique (bytecode arg-name probing, slim debug package, decompiled-source navigation, the general "isn't loading" checklist): see the wotmod-debug-repl harness skill. This skill is this mod's concrete REPL + snippets.

The debug REPL

A separate debug package runs a TCP REPL on 127.0.0.1:2223 inside the client (the sibling MoE Calculator's debug REPL uses 2224, so both mods' debug servers can run simultaneously).

# Build/deploy the debug package (Py 2.7, client CLOSED)
& "C:\Python27\python.exe" tools/dev/build_debug_wotmod.py "D:\Games\World_of_Tanks_EU" 2.3.1.2
# Drive it from the host (Py 3.13, client RUNNING, in Garage)
& "<py3>" tools/dev/repl_client.py "<expr>"
& "<py3>" tools/dev/repl_client.py --file cmds.txt

• One command per line; state is shared only WITHIN one run, so put interdependent commands in a single --file. For multi-line code, write a .py and send execfile(r'<abs path>').
• Keep the debug package SLIM (only mod_wgmod_debug.pyc). If it also ships wgmod_research it conflicts with the real mod and the client ignores BOTH.
• The debug package and the real mod are DISJOINT — rebuilding one never updates the other. build_debug_wotmod.py packages ONLY the REPL entry module (mod_wgmod_debug.pyc); it never touches wgmod_research. A source fix only reaches the client via build/deploy_wotmod.py <install> <ver> (the real com.14th_ua.garageprogressbar_<ver>.wotmod) + relaunch — see gpb-build-deploy. Mixing these up mid-session silently re-tests stale code.

Handy snippets

# current vehicle -> snapshot -> model
from CurrentVehicle import g_currentVehicle
from wgmod_research.adapter import engine_adapter
from wgmod_research.domain.builder import build_model
m = build_model(engine_adapter.build_snapshot())
(m.mode, m.scale_min, m.scale_max, m.fill_vehicle, m.fill_free, len(m.ticks))

# force a refresh of the mounted widget
from wgmod_research.bridge import gameface_bridge as B
B.refresh()

The deployed wgmod_research the REPL imports is the LAST BUILT one — a source edit you haven't deploy_wotmod'd + relaunched is NOT reflected. To sanity-check new pure logic against LIVE data without a redeploy, read inputs via the deployed adapter, then apply the new formula inline in the probe.

Inspecting settings WITHOUT a live client (on-disk MSA store)

Aslain's MSA persistence lives at %APPDATA%\Wargaming.net\WorldOfTanks\mods\aslainmenu.dat as UTF-8 JSON (decode as UTF-8 — a naive Windows open() fails at byte 0x81). Two keys matter for this mod:

• settings["com.14th_ua.garageprogressbar"] — the LIVE stored values (e.g. scale, posX…).
• templates["com.14th_ua.garageprogressbar"].settingsVersion — the STORED template version (what the client will compare the mod's bumped settingsVersion against on next launch).

Editing this file with the client CLOSED lets you stage a precise pre-state (e.g. set settingsVersion back to a pre-update number while forcing a value) to reproduce update-path bugs deterministically. The sibling izeberg store modsettings.dat does NOT contain this mod's linkage. (Used to root-cause the Large-after-cold-launch bug — see gpb-architecture "scale path fails safe" + TASKS/scale-large-after-update-cold-launch.md.)

Reading real XP prices with the client CLOSED (packed BigWorld sections)

res/packages/scripts.pkg holds item_defs/** as packed (binary) BigWorld sections, so the XMLs aren't greppable — but the format is trivial enough to read in ~40 lines of Python, which is how you answer "what does X actually cost" without launching the game (companion technique to the .mo parse in gpb-architecture). Per section: u16 nChildren, then u32 selfDesc where type = selfDesc >> 28 and cumEnd = selfDesc & 0x0FFFFFFF, then nChildren x (u16 keyIdx, u32 desc) pairs (same type/cumulative-end packing), then the data block — each child's bytes are [prev cumEnd : cumEnd]. Key strings come from the file's own dictionary. Figures established this way (EU 2.3.1.0, not re-measured on 2.3.1.2 — re-confirm live if a price looks off):

• Field modifications — post_progression/prices.xml unlockBaseModificationCost, per tier: t6 3500 / t7 7000 / t8 11500 / t9 20000 / t10 28000 per level.
• Tier-XI skill tree — 325000 for ALL 22 trees: 26 nodes = 20x10000 + 5x20000 + 1x25000 (node price groups from each veh_skill_configs/*_tree.xml, prices from the same prices.xml).
• Prestige / Elite Level XP is SERVER config and is NOT in the client files — don't hunt for it here; read it live (ILobbyContext…prestigeConfig, see references/game-api.md) or use the repo's recorded fixture figures.

Reading a write-only VM property back

The bridge exposes the mounted pair as gameface_bridge._active = (host_vm, rvm). VM properties are write-only (there's no getScale), but you can read any back via the generic Wulf accessor on the ViewModel: rvm._getNumber(<index>) — e.g. scale is prop index 33, so gameface_bridge._active[1]._getNumber(33) returns what the bridge last pushed. Useful to prove the push value is correct vs. what the widget renders (splits a delivery bug from a Python bug). Property indices are hand-numbered in bridge/view_models.py.

"The bar isn't loading / not updating" — this mod's specifics

Beyond the generic checklist in the harness skill:

1. Listener dropped after a battle — the bar stops updating only after entering/exiting a battle → a listener didn't re-arm. See the re-arming convention in gpb-architecture; check python.log for the [wgmod] ... (re)armed and [wgmod] push ... LOG_NOTE markers the bridge emits.
2. OpenWG missing — the entry point raises if openwg_gameface is absent; confirm the dependency .wotmod is in the same mods/<version>/.
3. Special/event hangars don't expose the params sub-view, so the bar won't mount there — expected.

The decompiled source for locating symbols: EU = the 2.3-series branch; cross-check against the live res/packages/scripts.pkg. Exact clone command + caveats: tools/dev/README.md.