2.2 KiB
OpenBMH Classic 1.0.3
Release candidate. Platform package and integrated QA results will be recorded before publication. Extended development lives separately in OpenBMH-Extended.
Changes under verification:
- Football Limited date setup and prepared-image cache; case-insensitive paths for Original CD data.
- A static Original title with its own palette, no loading balls, and a complete left/right click to enter setup.
- Ordinary dialogs preserve the scene behind them.
- Scores remain at the previous result during goal scenes and update at reveal.
- A complete right-button release belongs to the dismissed table/overview.
- Original preferred-position swatches and colored pitch cursor are restored.
- Own transfer listings expose existing offers early. Viewing/canceling does not alter the listing. Failed or refused listings can be listed again.
- Fresh arrivals do not inherit a previous occupant's contract-refusal flags.
- Saved wide player counters and title archives outlive native counter/window boundaries; old lost history cannot be reconstructed.
- Interest/dividend intermediate arithmetic and Bank aggregate display use wide values. Individual native account fields still have their documented limits.
- Bank robbery remains at the original threshold/amount but occurs at most once per manager and calendar month, with a saved latch. An unknown older history receives a grace month to avoid another deduction just after upgrading.
- Standard stadium blocks can reach144,000 places with edition-owned unit prices and size-aware build periods. Existing saves retain their native capacity bytes.
Known limits:
Calendar and rescheduling opened in the verified Classic datasets; the reported failure remains an open Human-QA item. Some supplied saves (including a supplied Diamond3.7 autosave) are rejected as damaged/unsupported before gameplay and are not claimed repaired by unrelated transfer fixes. Histories are preserved only from information available when this version starts. Older programs can discard OpenBMH's optional save extensions. True multi-billion single-account storage and every corresponding financial writer remain a separate unresolved issue.