赞了0个文件
写了2个评论
上传了0个视频
上传0个文件
0个跟随者
5mods on Discord
@thalilmythos Sure, if you look at line 2 for example, the uneven commas should be dots.
-304802106
0,7865754,542,2526,173,84
306,4945
01VDG053
-1692214353
111
132
-1
111
156
0
156
0
0
2,038848
0
1,2,3,4,5,10
0:-1,1:-1,2:-1,3:-1,4:-1,5:-1,6:-1,7:-1,8:-1,9:-1,10:-1,11:-1,12:-1,13:-1,14:-1,15:-1,16:-1,23:-1,24:-1,25:-1,26:-1,27:-1,28:-1,29:-1,30:-1,31:-1,32:-1,33:-1,34:-1,35:-1,36:-1,37:-1,38:-1,39:-1,40:-1,41:-1,42:-1,43:-1,44:-1,45:-1,46:-1,48:-1
0
0
-1
0
0
156
0
111
156
0,0,0,0
255,255,255
0
255,255,255
@thalilmythos The reason some players get the "saved but no blip/spawn" bug is actually a Windows regional formatting issue. Outside the US, Windows uses commas for decimals (like 17,411), so when the script saves coordinates and later splits that string by commas, it completely shatters the location data. I verified this by manually changing the commas to periods in my bugged .dat file, which instantly fixed the blip and made the car spawn correctly. To fix this permanently, you just need to force your script's thread to use the invariant/US culture format so it always writes decimals with periods regardless of the user's region. Thanks for the awesome mod!