5 Commits

Author	SHA1	Message	Date
DrakiaXYZ	5ab3ee722e	Fix issues caused when having NewSpawn enabled (!430) ... - When NewSpawn is active, clear spawn waves sent to the client - Copy `maxBotCap` to both BotMaxPvE and BotMax, as the client only reads BotMax These changes cause bots to abide by the NewSpawn parameters when NewSpawn is enabled, as previously it was combining bot waves and dynamic spawning resulting in bots instantly respawning Co-authored-by: DrakiaXYZ <565558+TheDgtl@users.noreply.github.com> Reviewed-on: SPT/Server#430 Co-authored-by: DrakiaXYZ <drakiaxyz@noreply.dev.sp-tarkov.com> Co-committed-by: DrakiaXYZ <drakiaxyz@noreply.dev.sp-tarkov.com>	2024-11-20 09:20:59 +00:00
Dev	a98696bfca	Split raider spawn chance override into 2 values, triggered and non triggered	2024-10-29 09:39:00 +00:00
Dev	7964d8ef5a	Added minReserveRaiderSpawnChance to location.json config, set to 72 by default, wired up to adjust reserve values on server start	2024-10-28 16:02:47 +00:00
Dev	9f6ec573d6	Removed fixEmptyBotWavesSettings - Doesnt seem necessary for 3.10 ... Disabled `rogueLighthouseSpawnTimeSettings` Same as above	2024-10-22 16:38:32 +01:00
Dev	9eba62d5e2	Moved code from gameStart() into server start via new class PostDbLoadService ... Fixed player adding their name multiple times to PMCs inside `addPlayerToPMCNames()` Updated `enableSeasonalEvents()` to not require a session id, moved player-specific code into new function `givePlayerSeasonalGifts()`	2024-10-22 13:33:07 +01:00