tehAon’s Status Buffs (Project Z) – Let Your Chat Run the Meters and the Bosses

- Fixed: on a dedicated server every add/subtract command moved its meter by twice what it moved in
single player - `buffPZBotFilth`, `buffPZBotOverheat` and `buffPZBotChill` shifted 50 instead of
25, as did `Exhaust`, `Dread`, `Irradiate` and the three `Boost` restores, and all eight `Ticket`
commands banked 10 minutes instead of 5. The set-based restores, guards and cleanses were never
affected because writing the same value twice is the same as writing it once, which is why the
report only ever named a few commands.
- Cause: `buffplayer` does not add the buff on the server. It tells the target CLIENT to run
`buff <name>` on itself, and that add is relayed back to the server, which rebroadcasts it
WITHOUT excluding the client that sent it (`_allButAttachedToEntityId` is the instigator id, and
the console passes -1). The client re-adds a buff it already has, takes `stack_type="replace"`'s
stacking path and fires `onSelfBuffStack` - so one redeem ran both the Start and the Stack
handler. Single player has no client to broadcast to, so only Start ran.
- Every one-shot relative write now lives in a hidden `stack_type="ignore"` worker buff that the
entry buff adds. AddBuff's Ignore branch fires no event, so the echo is swallowed and the write
happens exactly once on both server and single player. Entry buffs keep their name, their icon
and their 8 second HUD dwell, so no bot command changes.
- `tools/check_double_apply.py` fails if a relative `ModifyCVar` is ever put back on an entry
buff's Start or Stack trigger.