server/project/assets/configs/hideout.json

{
    "runIntervalSeconds": 10,
    "hoursForSkillCrafting": 28800,
    "runIntervalValues": {
        "inRaid": 60,
        "outOfRaid": 10
    },
    "expCraftAmount": 10,
    "overrideCraftTimeSeconds": -1,
    "overrideBuildTimeSeconds": -1,
    "updateProfileHideoutWhenActiveWithinMinutes": 90
}
Add Repo 2023-03-03 15:23:46 +00:00			`{`
Added variable hideout update() check times when in and out of raid 2024-03-30 15:15:06 +00:00			`"runIntervalSeconds": 10,`
Add Repo 2023-03-03 15:23:46 +00:00			`"hoursForSkillCrafting": 28800,`
Added ability to override hideout craft times via config 2024-04-06 20:25:57 +01:00			`"runIntervalValues": {`
Added variable hideout update() check times when in and out of raid 2024-03-30 15:15:06 +00:00			`"inRaid": 60,`
			`"outOfRaid": 10`
			`},`
Added ability to override hideout craft times via config 2024-04-06 20:25:57 +01:00			`"expCraftAmount": 10,`
			`"overrideCraftTimeSeconds": -1,`
Added new service `ProfileActivityService` Maintains a timestamp of when each profile was last active on the server. Timestamp is refreshed on two events: `game/start and `game/keepalive` Timestamp is used to determine if a profiles hideout should be processed. If a profile has a timestamp older than 90 minutes, it is not processed. (could be set lower but its a conservative value) This has the side effects of not adjusting the `sptUpdateLastRunTimestamp` property, resulting in `saveProfile()` not running for every profile. My testing shows a 20x perf increase for every profile in SPT not in use. Service could likely be used in other scenarios to avoid doing unnecessary work 2024-04-13 12:46:43 +01:00			`"overrideBuildTimeSeconds": -1,`
Apply Biome Formatting This is the result of running `npm run format` which applies the Biome formatting rules. Rejoice! 2024-07-23 11:12:53 -04:00			`"updateProfileHideoutWhenActiveWithinMinutes": 90`
			`}`