MantisBT - Soldat
View Issue Details
0000411SoldatMultiplayerpublic2013-09-08 13:202015-04-17 22:33
IzzyRosePL 
 
normaltweakrandom
confirmedopen 
x32Windows VistaHome Basic
1.6.5 
 
0000411: Packetloss: team-assignation bug
The client assigns player to choosen team but spawns gostek with white shirt.
- Spectator becomes white-shirted gostek spawned in random spawnpoint. Not sure if, as spectator, his gostek is visible for other players
- Assigned to alpha or bravo, player spawns in his team spawnpoint, but has white shirt and his nickname under F1 is white, but figures in proper block - for example player joined red - there is his white nickname between red teammates.
For other players everything is OK. It's local bug for client.
Randomly while changing team (happened mostly on INF, but also once on CTF).
Reporter plays with a radio internet connection and a wi-fi router (sitting with notebook just next to the router). Connection is good, there are no lags.
No tags attached.
related to 0000200confirmed  Packetloss of important informations 
? 2013-09-02_19-51-15_inf_Messner.sdm (2,636,287) 2013-09-08 13:20
https://bugs.soldat.pl/file_download.php?file_id=480&type=bug
Issue History
2013-09-08 13:20IzzyRosePLNew Issue
2013-09-08 13:20IzzyRosePLFile Added: 2013-09-02_19-51-15_inf_Messner.sdm
2013-09-08 14:43BistouflyNote Added: 0001899
2013-09-08 14:44BistouflyStatusnew => confirmed
2013-09-09 18:38SquiddyNote Added: 0001905
2015-04-17 22:32homerofgodsRelationship addedrelated to 0000118
2015-04-17 22:32homerofgodsRelationship addedrelated to 0000021
2015-04-17 22:33homerofgodsRelationship addedrelated to 0000200
2015-04-17 22:33homerofgodsRelationship deletedrelated to 0000118
2015-04-17 22:33homerofgodsRelationship deletedrelated to 0000021

Notes
(0001899)
Bistoufly   
2013-09-08 14:43   
Confirmed 1.6.5.

I also experienced this in climb server.
When it happened, I was immune to deadly polygons and unable to grab flags. For the other players I was in team5 (spectator team)
(0001905)
Squiddy   
2013-09-09 18:38   
I can also confirm this, it happens when too many people request at the same time (I got a lot this bug multiple times in that scenario).