tehAon’s ScoutMap – MiniMap That Knows the Buildings (Client-Side)

### Fixed
- **Heading-up no longer freezes while you drive.** The map took its heading from the player entity's
own yaw, and `EntityPlayerLocal.updateTransform()` opens with `if (AttachedToEntity != null) return;`
— the early return skips the line that assigns that yaw. So the moment you sat in a vehicle the
entity's rotation stopped updating and the map stopped turning with you, while the camera kept turning
perfectly well. The heading now comes from the player camera, which is the same source vanilla's own
compass uses (`XUiC_CompassWindow` binds `compass_rotation` to
`localPlayer.playerCamera.transform.eulerAngles.y`).
- **Hostiles now appear on servers.** Aggro mode asked `GetAttackTarget()`, which reads the field the
*server's* AI writes. A client only ever learns a target through `NetPackageSetAttackTarget`, which
calls `SetAttackTargetClient` and lands in a different field — so on every dedicated server the aggro
test was permanently false and the map drew no zombies at all, however many were hitting you. It now
asks `GetAttackTargetLocal()`, the accessor that picks the right field per `isEntityRemote`.
- **Hostiles also appear when the target packet never arrived.** That packet is only sent when a target
*changes*, and only to players already tracking that entity, so something that locked on before it came
into view could be mid-swing with no target recorded on your machine. Aggro now also accepts "awake,
within 24 blocks, and pointed at you" — body yaw is interpolated on every client because the model has
to face the right way at all, so it is a signal the client always has.
- **Animals that can hurt you are no longer invisible.** `EntityEnemyAnimal` derives from `EntityEnemy`,
not `EntityAnimal`, so a bear, dire wolf or zombie dog matched neither the animal test nor — because
aggro mode dropped every animal unconditionally — anything else. Wildlife is now read as both: hostile
enough to pass the aggro test while it mauls you, and animal enough to be drawn…

CHANGED
THE SQUARE BORDER IS GONE. "Circle mask" used to mean painting the corners dark, because an overlay
can only add colour, never remove it - so what you actually got was a dark square with a circle
drawn inside it. The map layer is now CLIPPED to a circular alpha mask (UIDrawCall.Clipping
.TextureMask feeding UIPanel.clipTexture), so the corners are never rasterised at all. The square
backing plate is off by default too (showFrame="false"), and a thin rim outline (rimPx, colorRim)
replaces it. Set hardCircle="false" to force the old look; if a build turns out to have no
Hidden/Unlit/Transparent Colored (TextureClip) shader, ScoutMap detects that at startup, says so in
the log, and falls back on its own.
circleMask="false" NOW MEANS A GENUINELY FULL SQUARE. The terrain quad is drawn root2 oversized in
square mode, because a same-size quad rotated 45 degrees has its own edges cutting across the
window's corners - heading-up mode used to sweep two empty corners round the map. Pixels per block
are unchanged, so markers still line up exactly.
WIDER ZOOMS. zoomSteps gains 400 and 528 blocks across, and maxSpanBlocks is now a ceiling (800)
rather than a size - the buffer is still only ever built as big as the widest step needs.
Marker placement and edge-pinning use a RADIAL bound on a round map. A tracked waypoint pinned to
the bounding square would land in a corner the mask cuts away.
FIXED
NO MORE DARK BARS ACROSS THE MAP WHEN YOU FLY. The soft edge that feathers the boundary of explored
ground is baked into a tile's pixels, using the neighbours that existed the moment that tile was
drawn - and a drawn tile was then never touched again. Standing still that is invisible, because the
ground beside you loaded long ago. In a gyrocopter every chunk gets blitted AHEAD of the one in
front of it, so each one bakes a fade towards ground that arrives a moment later and keeps it
forever: a permanent dark seam on every chunk line in the direction of travel, which reads as eve…

### Fixed
- **Two player arrows, one of them stuck pointing north.** The player's own nav object was being
drawn like any other marker. On the big map that nav object *is* the player arrow — vanilla has no
separate widget for it — but this map draws its own arrow at the centre and turns it to your
heading, so you got both: ours rotating, and a marker-pool sprite that cannot rotate sitting on
the same spot pointing north for ever. The player's nav object is now skipped. Reported in game.
- **The map buffer started fully transparent.** `MiniMapCanvas`'s constructor clears the texture
before the style has been applied, so it painted with a default `Color32` — transparent black —
and every pixel stayed see-through until the tile owning it was first blitted. Unexplored ground
is meant to be paper, not a window. The style pass now repaints the buffer with the configured
blank.
### Changed
- **The opacity diagnostic is logged after the map has drawn, not at startup.** At startup it always
said `mapPixel=0`, because no tile had been blitted yet — a diagnostic that lies in a fixed
direction is worse than none, since it points at the one layer that was innocent.

- **Claims game 3.2.0.** `GAME_VERSIONS` widens from `V3.0.0-V3.1` to `V3.0.0-V3.2.0`.
Verified in game on a real V3.2.0 b10 client, not inferred: see `VERIFIED` for what was
actually exercised. No behaviour changed — this release is the claim and nothing else.

- Claims game 3.3.0. No code changed. Game 3.3 is the stable release now and this mod already works on it, so the supported range widens from V3.0.0-V3.2.0 to V3.0.0-V3.3.0. Checked, not assumed: every game member the DLL binds to resolves against the 3.3.0 (b18) build, every Harmony patch target is still there, and the mod loads on a 3.3.0 dedicated server with no errors. It has not yet been played on a 3.3 game: no 3.3 client was available when this was cut.