# Compatibility decisions OpenBMH aims to preserve the familiar game while handling malformed input and unsafe edge cases explicitly. A reconstruction can remain faithful without reproducing a crash or pretending to implement an unknown path. - Names, text, graphics and compatible data tables come from the user's installation. The common gameplay implementation follows the documented Diamond 3.7 engine policy; original programme instructions are not executed or selected as separate engines. - Safety checks reject transactions that would exhaust required return capacity, use stale identities or lose a valid state. Unsupported operations report their limitation rather than inventing an outcome. - Calendar progression handles boundary days and seasonal transitions without relying on unsafe fixed-day assumptions. - Saves are written from the committed session state. Saving does not deliberately replay unrelated game actions. - The reconstruction uses two deterministic random generators with explicit integer semantics. This supports reproducible runs, but is not a promise of complete bit-for-bit equivalence to every original edition or across changed engine versions. Intentional changes in code should use the marker `OpenBMH deviates from the original:` and explain their purpose. Adding a new behaviour or balance change requires a concrete description and relevant tests; this page is not permission to substitute guessed rules. The [generated differences catalogue](DIFFERENCES.md) lists these markers with links to their source files. ## Application exit confirmation Closing the window, exiting with Escape or confirming the desktop's exit control opens a native confirmation dialog. BMH data uses German text and Football Limited data uses English. Enter, Escape and closing the confirmation cancel the exit; only the explicit Quit/Beenden button permits normal shutdown. Cancelling keeps the current dialog or match owner alive without a turn or implicit save. An unavailable native message box also cancels the request. This applies to voluntary application exits, including quit events received during animations; normal completed-career handling remains separate. ## Common engine and source data Loaded executable images retain their own rule tables. Career strength ranges are read from all nine pairs of the supplied original table. The common engine uses the Diamond 3.7 six-budget monthly environment model for every supported source-data edition, including Diamond 3.6 and Football Limited. Original programme instruction fingerprints do not select another engine or block compatible data. The six numeric budget increments are read from the supplied table and installed together only when all are present and nonzero; malformed layouts remain rejected. Existing saved lump-sum academy contracts retain their established accounting until edited. English translation supplies the actual English geometry, steps and suffixes for this common model. The old floppy executable remains unsupported, and Football Limited remains experimental. Football Limited's data distinguishes five internal domestic slots from four player-visible levels. Fresh manager selection cycles those four levels and hides the internal fifth picker group; confirmation rejects hidden targets and clubs before changing options or consuming RNG. Additional club pages remain separate. Internal sizes, squads, rankings and fixtures are retained, and saved internal league values do not cause a general load rejection. Release acceptance of individual editions is recorded separately from their recognition. Source compatibility and automated tests do not establish full original-game or platform validation. OpenBMH deviates from the original: graphical startup shows the supplied static 137.VGA title with its embedded palette, without the DOS loading animation. It waits for a complete left or right mouse click before the game options. The title does not advance on a timer; its confirming press and release are consumed so they cannot also change a setup option. Setup restores ordinary scene-backed manager dialogs before a career is created or loaded. The executable's boot-only black dialog mode is process state and is not restored from native save files. Football Limited's translated data includes its own verified calendar year and weekday operands; German epochs are not used as a substitute for the English edition. ## Diamond 3.7 foreign crests The supplied edition controls whether foreign league clubs use individual original crests or the original neutral crest. OpenBMH recognizes the verified Diamond 3.7 drawing gate and uses its database/save selectors and W atlases. Older drawing gates retain their own behaviour; no external crest pack is needed. The automatic lineup installs the supplied foreign-player rule switch alongside the career tables. Where enabled, it restores the original three/two-player limit, reserve swaps with board-coordinate preservation and the short-lineup outcome when domestic reserves are unavailable. This does not consume additional random draws. New careers correct the original all-zero EM qualification placeholders to the original national-team placeholders. Supplied nonzero seeds and restored savegame state are not rewritten by this initialization. ## Stadium size: the edition's limits (extension of 1.0.3 withdrawn) The stadium blocks A–H use the limits, unit prices and construction periods of the supplied edition unchanged. Diamond 3.6/3.7 allows 8/18/8/14 thousand places per block, twice, so 96,000 places in total; its 14k stands take 25 weeks, the 8k stands 30 and the 18k stands 37 (original data, not a mistaken timer). Contractor shortening remains unchanged. The UI validates quotes against the actual edition. Versions 1.0.3 to 1.0.12 raised the standard maxima to 14/24/14/20 thousand (144,000 in total) with longer construction periods. That extension is withdrawn: the match broadcast of the original has no room for attendances of 100,000 and more and showed them wrongly. A savegame whose stadium is already larger than the edition's limit keeps its places (the capacity bytes are unchanged), but such a block cannot be extended any further. ## Daily interest at large native balances OpenBMH deviates from the original: daily debt and deposit interest uses 64-bit intermediate arithmetic before the original integer divisions. The balance-plan preview uses the same calculation. Original rates, division order and random consumption remain unchanged. Account balances and accumulated statistics retain the native 32-bit save representation; this change does not add unlimited account balances or change the original high-cash deduction policy. OpenBMH deviates from the original: the legacy transfer market allows an owned listing to open incoming offers before its weekly expiry. Select the player and use the sale action (or Enter). Cancel keeps the listing and offers unchanged; acceptance uses the existing buyer eligibility, player salary qualification and transaction rules. Human-buyer loans still require their separate consent and allocator context and are unavailable in this early review. Viewing/canceling consumes no RNG. The weekly auction remains unchanged. The transfer overview processes one selected player per action and renders action feedback in its footer. A cleared unsuccessful listing can be listed again immediately; there is no additional cooldown. The manager listing action refuses a full ordinary market without allocating a reserved special-offer row. These are explicit application outcomes instead of the Original's destructive overflow/dialog paths. OpenBMH deviates from the original: a newly initialized squad board entry clears retirement, refused-negotiation and month-processing flags left by its previous occupant. The Original leaves that byte intact when reusing the row, so purchases and academy arrivals can inherit a refusal to renew. Existing players' genuine retirement/refusal flags remain effective. The initial academy contract remains two years; a young arrival can immediately negotiate any supported renewal term. This corrects the reused-row mechanism; it does not establish a fixed 200–300 season threshold or repair ambiguous refusal flags in existing saved careers. Bank finance-overview totals and gains use 64-bit read-only projections and currency formatting, including values beyond a signed native account word. Saved cash, deposits, loan fields and holdings retain their original widths. This prevents a positive combined portfolio from appearing negative; it does not recover amounts that have already overflowed inside a native saved field. Live ball, set-piece and shot animations retain visible scoreboard digits at the chance-preview value until the result view. The simulation still commits goals, statistics and random draws at their existing boundaries. Post-match overview dismissal owns its full mouse gesture, including release after pointer movement, before the following calendar decision can open. The pitch uses each edition's original position-distance tables, atlas swatches and pointer bitmap for placement feedback; this display state is not serialized. OpenBMH deviates from the original: cumulative human-club appearances, goals and assists have optional 64-bit counters. Original byte/word fields keep their modulo representation for gameplay/layout compatibility; roster projections use the wider values. Tracking begins with the surviving legacy values, so high bits already lost in an imported save cannot be recovered. A new arrival clears the previous squad occupant's totals. Club promotion remaps counter ownership. Title-holder and cup-winner lists retain all observed seasons in the same optional OpenBMH save extension. The Original nine-by-fifty table remains a rolling window. The archive captures that window before it shifts, and the title list can page through the archived rows. Late legacy imports start with their surviving fifty seasons; earlier winners are unknown and are not fabricated. Stored winner names are historical snapshots, so later renaming and promotion cannot change them. The separate manager-achievements graph retains its Original fifty-season view. These records use a versioned `OBMHEXT1` extension after the Original name pools; see [save format](formats/LONG_CAREER.md). Original programs and older OpenBMH writers do not preserve this archive. Keep an OpenBMH backup when exchanging careers with those writers. The native calendar still has its existing signed 16-bit season limit; this patch does not claim an unlimited calendar. ## Monthly high-cash loss limit OpenBMH deviates from the original: the high-cash bank robbery can occur at most once per manager and calendar month. The original threshold above 100 million and random loss of 10–20 million remain. A blocked repeat consumes no random draw. Month boundaries follow the same source calendar used by daily processing, and the guard is stored in the optional BRM1 section of OBMHEXT1 saves. An older save has no record of past robberies. Its first qualifying high-cash month receives a grace period without a loss or random draw; subsequent saves retain that guard. The next calendar month can trigger the ordinary loss. Import cannot infer whether an event already occurred before this feature. Fresh histories receive the same initial grace month. OpenBMH deviates from the original: monthly fund/property dividends multiply unit price by the dividend factor in 64 bits before the existing integer division. The monthly and annual previews and weekly offers use the same widened product. Per-unit rounding and the selected legacy/typed recipient policy are unchanged. This corrects intermediate overflow for representable dividends; account, deposit, property book value and monthly totals still use their native 32-bit storage and can overflow. It is not a complete large-balance finance fix. Release-driven incoming-transfer presenters require a matching press observed inside that modal. An orphan or repeated release from the preceding result table cannot decline an offer or dismiss its confirmation. Repeated presses while a button is held still form one gesture; fresh left/right clicks keep their actions. ## Host file overwrite confirmation The file picker reuses the Original overwrite question and Ja/Nein button layout. A separate Yes click or Enter confirms; repeated double-clicks do not. OpenBMH deviates from the original: host file operations use the shared dialog's system identity because the picker does not own a live manager portrait projection.