Search Issue Tracker

By Design

Votes

0

Found in

5.5.0b2

Issue ID

830419

Regression

No

NetworkConnection.Disconnect() does not remove connection from NetworkServer.connections

Networking

-

Steps to reproduce:
1. open attached project
2. build and run 3instances
3. host with one and connect as client with others
4. disconnect the first client instance
5. try to connect new instances

Expected: successfully connects
Actual: NetworkServer.connections never gets updated after the first call of NetworkConnection.Disconnect()

Reproduced: 5.2.5f1, 5.4.0f3, 5.5.0b2

Comments (4)

  1. herrenderschoepfung

    May 29, 2018 09:23

    This still exists and there's no reason why the sever can't just remove the connections, instead of making them null...

  2. spacefrog

    May 29, 2017 08:54

    Just seen that "By Design", pretty curious why the connections readonly list should keep the closed client connections in it as <null> entries by design ?

  3. spacefrog

    May 29, 2017 08:52

    This issue still exists in 5.6.1f1 and 2017.1b7

  4. vmostransistor

    May 10, 2017 09:47

    In which issue has this been resolved? Still have it in 5.6.0b9.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.