- Server version
- 2.1.2
- Game client version
- 12.11.15680
- Client log file
- codepaste.sp-tarkov.com/?10b09…UKCj5uF4ceho9x7sgrFz2w8nc
- Server log file
- codepaste.sp-tarkov.com/?21514…cvJ1wasqaaGFaSooEAHU3no5L
- Have you read the FAQ?
- Yes
- Where did you download your game from?
- Battlestate Games
- List of used mods
- ACOG4Life-OpticRework
CoreMod
Faupi-HideoutArchitect
Faupi-MunitionsExpert
Fin-AutoBalanceLevels
Kiki-CameraRecoilRemover1.0.5
Kiki-FenceTweaks1.1.2
Kiki-MysteriousKeys2.1.2
Kiki-ZaryaKiller3.0.2
KMC-Core
KMC-Gear
Lua-PlayerBossScav
MakesSense
Operator
Questor
Revingly-FoodDrink-Redux
Revingly-LPA-Redux
SamSWAT-FAMAS
SamSWAT-M1014
SamSWAT-SCARH
Thunderbags-ResponsiveFence
ServerValueModifier
ThatGuyXIV-RandomLooseLootGenerator
SPT-EFT-ProfileEditor
As the title suggests, I've had an issue where, after roughly 7-8 raids, the time displayed on a time sync will not be the actual time when the raid starts. It's usually about 5-6 in-game hours earlier than the selected time.
This does not happen gradually. It is very sudden where I might go in at what I think is a 10am time and it turns out to actually be 4am.
I've used mods that restart the timer at a certain time after each successive raid, effectively "freezing" the clock (through FAIT I believe) and never experienced this issue when doing that.
When this issue occurs, I am forced to shut the program down and restart the entire server in order for the time syncs to match up with their displayed time again when selecting it.
I don't believe these most recent logs will show this as I only started the program, had to do something else, then shut it down when I came back without ever entering a raid. If it is necessary for me to cause the bug to happen and then share new pastebins of the logs when it occurs, I will do so.