Votes by users: 1
Sat 07 December 2024 13:32
13th Gen Intel(R) Core(TM) i5-13600K (x64)
NVIDIA GeForce RTX 3060/PCIe/SSE2 4.6.0 NVIDIA 566.36
65536MB RAM
Windows 10 Enterprise 10.0 64bit
Stormworks 64-bit
v1.13.1
Closed (No Reproduction)
Defect
In my server config, despawn_on_leave is set to true, and it works for almost all players that join my dedicated server, except some random ones. The player in the image has been kicked ~ 1 second after he joined and didn't despawn, could have been the issue causing it, but I did not find a precise way to replicate it yet.
Tue 17 December 2024 06:20
Thank you for the report, but we need a way to reproduce it. Can you try to kick a player right or shortly after the join and see if it causes this issue?
Wed 18 December 2024 00:33
It seems very rare, and i cannot find a method to reproduce this with manual kicking. But the thing i can say is that it has to do something with players that recently joins. This bug happened to me ONLY on players that are banned from the server, and those players get kicked using server.kickPlayer() in function httpReply ~1 second after join because of my custom ban system.
Sun 12 January 2025 18:08
https://cdn.discordapp.com/attachments/1328059952614477897/1328060262426611772/Stormworks_1_12_2025_11_56_55_AM.png?ex=67855400&is=67840280&hm=d6806bb6795761f988ab79eec76a680114c10a5942389b691505609765909c4a&
There it happened again, same logic, those players get kicked almost instantly after they join, but the bug seems random. It could or could not happen when players get kicked almost instantly. Happens more since i made the kick system more quick
Thu 13 February 2025 05:33
We've tried a script that kicks right after join with that option on and it worked just fine. We even simulated a packet loss for both client and server sides and that also didn't cause that issue. We will close this ticket, but you can leave a comment if there will be an easy way to reproduce the issue.
Issue closed
