GSC X TWS Garbage Collector

1.0.40

1.0.39

1.0.38

1.0.37

1.0.36

1.0.35

1.0.34

1.0.33

1.0.32

1.0.31

1.0.30

1.0.29

1.0.28

1.0.27

Added Translations for all languages

1.0.26

1.0.25

Added Defensive Guards

1.0.24

- Optimized (performance review):
* The "is there an Arsenal nearby" check no longer runs a spatial world query. Every arsenal now
registers itself when it initialises and unregisters when it is deleted (new GSC_ArsenalRegistry.c,
a small modded SCR_ArsenalComponent), and the check is a plain distance test against that short list.
The old query visited every entity inside the radius and ran a slot/parent/child component search on
each - costly per drop, and repeated for EVERY vehicle in a single frame by the abandoned-vehicle sweep
(a visible hitch on servers with many vehicles every sweep, and every minute while Dynamic Mode is
under pressure). The short-lived result cache it needed is gone with it.
* The prefab whitelist match is computed once per distinct prefab and remembered (cleared whenever
the whitelist is (re)loaded) instead of lower-casing the prefab name and every whitelist entry on every
drop, death and every entity the game's own garbage system tracks or deletes.
* Clients no longer do any work for deaths and inventory events: both hooks now return before the
whitelist match / before scheduling the follow-up check unless running on the server.
* The "is a player nearby" test reuses one buffer instead of allocating an array per call and compares
squared distances.

1.0.23

"Dynamic Min Lifetime (%)" (5-100, default 20) sliders in Scenario Properties, right after Enabled and
  Seeding Mode as it affects every category; the sliders are greyed out while the checkbox is off).
  The configured Corpse/Wreck/Ground Item lifetimes and the Abandoned Vehicle

1.0.22

- By default ("Vanilla Default Behavior" on) the game's collector behaves exactly as it always
    does - only the prefab whitelist is enforced on it. Untick "Vanilla Default Behavior" to also
    give it a player-distance rule: "Vanilla Min Player Distance" (its own slider, separate from
    the per-category ones). When it is about to delete something with a player closer than that,
    the deletion is postponed. If you would rather have a single rule set, switch

1.0.21

- Added: "Reset Timer When Player Near" checkbox (JSON key "resetTimerNearPlayer", OFF by default), one
  setting for every cleanup category and for the game's own garbage system. It switches the "player
  nearby resets the timer" behaviour described in the next entries on or off - so out of the box a
  nearby player only postpones a removal, as in earlier versions:
  * ON: a player within the Min Player Distance resets the timer, and it only starts over once nobody
    is that close.

1.0.20

- Added: "Vanilla Min Player Distance" slider (0-500m, 0 = off; JSON key "vanillaMinPlayerDistance",
seeded from the old single value on upgrade). It is the Min Player Distance used by the game's own
garbage system, nested under "Disable Vanilla Garbage System" and greyed out while that is ticked
(the game's system does nothing then). It replaces picking a category's distance by what the
game's system is about to delete, which could not always tell what an entity was.
- Changed: Scenario Properties order. Under each cleanup category the options now read Lifetime ->
Min Player Distance -> Max Tracked (Abandoned Vehicles: Delay -> Min Player Distance -> Check
Interval), followed by Retry Delay, then Disable Vanilla Garbage System with its Vanilla Min Player
Distance, then Debug Logging, Prefab Whitelist and Reload Config From File.

1.0.19

- Changed: the same applies to corpses, vehicle wrecks and ground items. Their lifetime used to be a plain
one-shot timer: if a player was nearby when it expired, the removal was merely retried every Retry
Delay and happened the moment the player stepped away - even if they had stood there the whole time.
Now a player within Min Player Distance pauses the clock (re-checked every Retry Delay), and once
nobody is near the full lifetime starts over from the last moment a player was seen close, so time
spent with a player around never counts towards it. Note the lifetime is still checked only when it
expires (the addon stays event-driven - no continuous scanning), so a player who was near only in the
middle of the lifetime and gone again by the time it expires is not noticed. Min Player Distance 0
turns this off.

1.0.18

- Changed: the abandoned-vehicle clock no longer runs while a player is near the vehicle. Previously the
"empty since" timer started and ran regardless, and a nearby player was only checked at the moment it
expired (the removal was merely postponed). Now a player within Min Player Distance resets the
clock at every sweep, and it only starts counting once the vehicle is empty AND nobody is within that
distance - so a vehicle that has had players around it never counts the time they spent there as
"abandoned". Min Player Distance 0 turns this off.

1.0.17

- Fixed: with the addon switched off ("Enabled" unchecked) its whitelist veto over the game's own
garbage system, and the blacklisting of whitelisted entities, stayed active. The addon is now fully
inert when disabled.

1.0.16

1.0.15

- Added: "Disable Vanilla Garbage System" option (checkbox in Editing: Scenario Properties, and
"disableVanillaGarbage" in GSC_Settings.json; off by default). When on and the addon is enabled, the game's own built-in garbage

1.0.14

- Added: the whitelisted-item watch now also records how far the nearest player was at its last check
and prints it with the "GONE" line, to show whether something only vanishes while a player is close.

1.0.13

- Fixed: whitelisted prefabs could still be deleted by the game's own garbage system, even after being
blacklisted from it, because that blacklist can be bypassed and an entity can be tracked at any
later point. The addon now hooks that system directly (OnInsertRequested / OnBeforeDelete) and
refuses to track, or to delete, anything on the Prefab Whitelist - for items, vehicles and corpses
alike. With Debug Logging on, each refusal is logged ("Vanilla garbage system: refused to track /
PREVENTED deletion of ..."). The earlier "withdrawn from the vanilla garbage system" log line also
never fired because the check ran after the blacklist call had already withdrawn the entity; fixed.

1.0.12

- Fixed: "Reload Config From File" now fully applies the reloaded settings. Before, the values were
copied in but the abandoned-vehicle sweep kept its old interval/on-off state and a newly disabled
addon kept its pending timers until the next restart; the settings-changed notification also
wasn't fired on the server itself.
- Fixed: when the tracking cap forced an early eviction, the oldest tracked entity was deleted without
re-checking it still qualified - a queued item that had since been picked up (or a wreck that had
been repaired) could be deleted out of someone's inventory/hands if Min Player Distance was 0. It
is now dropped from tracking instead, and the next-oldest is considered.
- Fixed: an item picked up and dropped again had its timer reset but kept its old (oldest) position
for eviction, so it could be evicted while freshly dropped. It now moves to the newest position.
- Fixed: an entity already waiting on its cleanup timer when it became whitelisted (config reload) or
when Seeding Mode was switched on was still deleted when the timer fired. Whitelisted ones are now
dropped from tracking; with Seeding Mode on they stay tracked and are re-checked later instead.
- Fixed: reloading the config could, depending on how the JSON reader fills an existing array, append
to the old whitelist instead of replacing it; it now starts from an empty list.

1.0.11

- Added: persistent log file. The addon's log lines (removals, queued/re-dropped entities, whitelist
decisions, cap evictions, the whitelisted-item watch below) are now also appended, timestamped, to
$profile:GarbageCollector/GSC_Log.txt, in addition to the console. Written in batches every few
seconds (not once per line) and on mission end; once the file passes 5 MB it is rotated to
GSC_Log_old.txt, so it can't grow unbounded. Follows Debug Logging (off = nothing written apart from
one "Started" line per mission start). The very chatty per-drop "Main base check"/"Arsenal proximity"
diagnostics stay console-only so they don't bury everything else in the file.