WBML-0002 — addon state stays isolated between world saves
✅ Verified 🧪 WorldBox Modding Lab WBML-0002
WBML-0002 asked a different question from WBML-0001:
If two world saves use the same addon and the same logical data keys, does one world’s addon state appear in the other world?
Why this needed a separate probe
Section titled “Why this needed a separate probe”WBML-0001 verified:
same save + full process restart → values returnThat did not prove that the values were isolated from other worlds. A bad implementation could still have appeared persistent while actually leaking through static/runtime state.
WBML-0002 therefore used two different saves and two different current-run signatures.
Harness correction before the valid run
Section titled “Harness correction before the valid run”The first 0.0.2 harness had a methodological bug: a failed Step C did not prevent Step D from printing a final success line.
That run was rejected.
0.0.2-fix1 added:
strict A → B → C → D state machineunique run tokenstep flagsfinal gate requiring A=PASS B=PASS C=PASS D=PASSfailure lockoutThis matters because a probe is only evidence if its own verdict logic is trustworthy.
Verified environment
Section titled “Verified environment”WorldBox: 0.51.2build: 719git: build-719@5decNeoModLoader: 1.2.0.1PoliticalWorldAPI: 1.14.0Lab: 0.0.2-fix1Current-run token:
af599151c6daSequence
Section titled “Sequence”World A→ write A signature→ save→ load World B→ confirm A signature absent→ write B signature→ save→ load World A→ confirm B signature absent + A values return→ load World B→ confirm A signature absent + B values returnThe probe tested:
markerintUnicode stringboolfloataddon-private kingdom tagshared kingdom tagStep results
Section titled “Step results”A — write World A
Section titled “A — write World A”A-IMMEDIATE RESULT: 6/6 DATA PASS | marker=PASS => PASSSTEP A RESULT: PASSB — verify clean World B and write B
Section titled “B — verify clean World B and write B”Before writing B, the probe scanned 21 kingdoms:
WORLD B CLEAN CHECK: PASSno current-run WORLD A signature found across 21 kingdomsThen:
B-IMMEDIATE RESULT: 6/6 DATA PASS | marker=PASS => PASSSTEP B RESULT: PASSC — return to World A
Section titled “C — return to World A”RETURN A: current-run WORLD B signature absent => PASSA-RETURN RESULT: 6/6 DATA PASS | marker=PASS => PASSSTEP C RESULT: PASSD — return to World B
Section titled “D — return to World B”RETURN B: current-run WORLD A signature absent => PASSB-RETURN RESULT: 6/6 DATA PASS | marker=PASS => PASSSTEP D RESULT: PASSThe corrected final gate then required every step:
FINAL GATE: A=PASS B=PASS C=PASS D=PASSFINAL RESULT: WORLD ISOLATION VERIFIED FOR THIS RUN.Verified claim
Section titled “Verified claim”For the tested environment, PoliticalWorldAPI kingdom state used by the probe stayed isolated between the two tested world saves during the same WorldBox process.
The current-run A signature did not appear in B, the current-run B signature did not appear in A, and each world’s own values returned when that save was loaded again.
Evidence boundary
Section titled “Evidence boundary”This result does not by itself prove:
- party-private data isolation;
- the exact physical save file/database used by each value;
- isolation for every possible PoliticalWorldAPI data type;
- behavior across future WorldBox/NML/Political World versions;
- a full-process-restart isolation sequence.
Full-process persistence is a separate verified result from WBML-0001.
Methodology lesson
Section titled “Methodology lesson”A failed probe harness is still valuable research material if the bad verdict is rejected rather than promoted.
The corrected rule is simple:
final result = conjunction of every required stepnot:
last step passed → whole experiment passedThis rule now belongs to the Lab’s evidence methodology, not just this one test.