[CoaPsyFactor]

Quote:

Originally Posted by Yashas Yes, that's an issue but it's extremely rare. For that to happen, all the following incidents need to happen: 1. The transformation process decided to generate a sample just before the player quits (it takes around 2-10s to generate a sample) 2. The detectors will return the data in less than a second. Hence, the next player must join pretty quickly. 3. The player who joins next should get the same player id You can add a check to ensure that the player has been in the server for at least 10 seconds. Even by remote chance it happened, it should be ignored. Only repeated warnings should be taken seriously. TLR: the cost of taking care of that extremely rare situation outweighs the benefits

You can always prevent vector check if processing id is disconnected in mean time esy fix