tehAon’s Player Beacon – Let Your Bot See Vehicles Claims and Traders

- First release. Publishes player state a server console cannot otherwise see, as `$pb*` CVars any
bot can read with `cvar get <name> -p <entityId>`: `$pbInVehicle`, `$pbInTrader`, `$pbInClaim`,
`$pbSafeZone`, `$pbGateOk` and `$pbSafeSecs`.
- `$pbSafeSecs` counts seconds continuously clear of all three gates and resets on the condition
rather than on its own value, so a bot polling on its own clock cannot miss a player who ducks in
and out of cover between polls.
- `$pbClaimsArmed` and `$pbTraderProt` publish whether the claim and trader checks are actually live
on this server, so a bot can tell "they are in the open" from "this server does not check".
- `$pbApi` is a contract version, currently 1. A missing CVar reads as 0, so it doubles as a
reliable "not installed" signal.
- Server-side, XML only, read-only. Adds no items, blocks, recipes or gameplay.

- **Fixed: `$pbInClaim`, `$pbSafeZone` and `$pbInTrader` were permanently stuck at `0`.** Caught on a
live dedicated server with a player standing inside a land claim. `$pbInVehicle` was never
affected. If you installed 0.1.0, three of the four things this mod exists to report were not
working — please update.
- The cause is in vanilla, not in the XML that used it. `BaseRequirement.Clone()` copies a
requirement's raw properties but never copies the `Invert` field and never re-parses it; a subclass
has to re-copy `Invert` itself. The operation-based requirements do, but `RequirementInSafeZone`
and `RequirementInTraderArea` — the two this mod needs — do not. Requirements attached to an
`<action>` are cloned on every firing, so `invert="true"` on those classes never survived to be
evaluated, and each polarity pair ended up running with the same polarity.
- Each polarity now gets its own action sequence with a sequence-level requirement, which is
evaluated before any clone exists and keeps its `invert`.
- **Removed a `WRN [PROPS] ActionTarget implicitly converted to Vector3` logged once per second per
online player.** Firing a game event from a buff always trips a failed implicit conversion inside
the game. Each sequence now also carries a "the value is not already what I would set it to"
requirement, so nothing fires in the steady state. Measured on a live server: 2 lines/sec/player
before, none at all while idle, a handful per real transition.
- Documented two measured caveats: `$pbApi` can read `0` for a few seconds on a player's *first*
join, so treat "just connected" as unknown rather than "not installed"; and the three reason flags
can disagree for about a tick mid-transition, while `$pbGateOk` and `$pbSafeSecs` stay correct
throughout.
- Verified on a dedicated server running V3.0.0 (b259) with Project Z 3.0 loaded, against a real
client: vehicle, land claim and trader area all confirmed on and off, land claim checked against
the claim blocks recorded in `…