Describe the bug
Objects can sometimes receive rpc calls (possibly other stuff to) from the wrong object because of reuse of networkId's.
One way to fix it would be to not reuse an networkId until a certain time has passed since it was last used.
To Reproduce
- Make sure to have some latency.
- Have an object spam rpc calls from client to server.
- Have server remove the object and quickly add a new object.
(Have not tested this)
Expected behavior
Don't get networkId's mixed up.
Environment (please complete the following information):
- OS: [Windows 10]
- Unity Version: [2018.3.7f1]
- MLAPI Version: [v8.5.1]
Describe the bug
Objects can sometimes receive rpc calls (possibly other stuff to) from the wrong object because of reuse of networkId's.
One way to fix it would be to not reuse an networkId until a certain time has passed since it was last used.
To Reproduce
(Have not tested this)
Expected behavior
Don't get networkId's mixed up.
Environment (please complete the following information):