tehAon’s Vanilla Fixes – Six Base-Game Bugs Patched

**Renamed from Item-Started Quest Fix, and widened from two repairs to four.** The two bugs this mod
already fixed are base-game bugs, not any mod's; so are the two it absorbs. Keeping them in separate
downloads meant four pages, four changelogs and four install decisions for one answer: *the base game
is broken here, and here is the patch.*
Absorbed:
- **Treasure maps read at or below y = 10 never get a location** (new). `CalculateTreasurePoint`'s
low-altitude guard reads `vector.y`, which is `startPosition.y` — the player's altitude — because
`GetTreasureOffset` always returns `y = 0`. It was meant to test the candidate point's own height.
Below the line every one of the 750 draws behind a request fails, the server never answers, and the
map item is consumed for a quest that can never resolve. Measured on V3.1.0 b14, stock Navezgane:
**0/20 placed at y ≤ 10 across 15 000 draws; 20/20 at y = 10.5 in ~70.** Three blocks of altitude.
- **The modded-forge smelting panel** (was a separate mod). With Smelter Type on craft-from-backpack,
any forge not literally named `forge` keeps a panel the game already switched off; the no-smelting
twin window is generated by learning the delta from vanilla's own `workstation_forge` pair.
- **The server-side Stay Within repair** (was a separate mod), as `Config/quests.xml`. It selects on
the shape of the bug rather than on quest ids, so it repairs whatever is broken on your server, and
fixes every player from one server install with EAC left on.
New in the bundle:
- **A startup manifest.** One line per repair, every start: name, ARMED/OFF, the side it acts on, and
what it does. Four silent fixes are unsupportable without it — a repaired quest is indistinguishable
from one that was never broken.
- **Per-fix switches** — `fixStayWithin`, `fixTreasureMap`, `fixForgeWindow` — so one repair can be
disabled without giving up the rest.
- **Compat guards extended** to every new member the added patches bind to.
**Why a bundle does not rot.**…

**Now claims V3.0.0-V3.2.0.** No behaviour changed; the four repairs are the same code. What changed
is that the 3.2 claim is now backed by a playtest instead of a guess.
Verified on a real V3.2.0 (b10) dedicated server, joined from a V3.2.0 (b10) client — the same build,
because a client can only join a server of the same build and a mismatch hangs it silently:
- The bug is **still present in 3.2**. The server logged `NullReferenceException` at
`NetPackageQuestGotoPoint.ProcessPackage`. TFP has not fixed it; all six patched types are
byte-identical 3.1 -> 3.2.
- The repair **fires and works**. The client re-asked at 10s, 20s and 30s and then showed the travel
prompt, and the server logged one fresh NullReferenceException per retry — four in total for the
original request plus three retries. That one-to-one match is the proof the request really is
being re-sent rather than the client only logging to itself.
- The DLL resolves against every version it claims: 3.0.0, 3.0.1, 3.1 and 3.2.0.
Built against V 3.0.0 (b259), the oldest version claimed, so no reference can bind to a type newer
than the oldest supported build.

- Works on game 3.3. On 3.3, 1.1.0 switched itself off completely: 3.3 renamed the one game method the forge-window repair sits in front of, the startup check saw it missing, and the mod refused to patch anything, so the other three repairs went with it.
- All four repairs work on 3.3. The forge-window repair now fronts whichever method the running game has.
- A repair the game outgrows no longer takes the others with it. Each one is checked on its own at startup; one that cannot run says so in the log and shows as UNAVAILABLE in the fix manifest, and the rest are patched in as usual.
- All four bugs are still in game 3.3: the vanilla code at each of the four sites is unchanged from 3.2.
- The repairs themselves have not been exercised in a 3.3 game yet.