Seems that ENET's maximum connections is how many connection slots that will be used by the server. Connecting and then disconnecting clicks down the remaining slots.
ie. 4 slots = 4 connection capacity, no more after that. Not "I can run 4 connections at the same time".
For example, using Mirror's example pong scene and connecting to the same server more than 4 times will cause the transport to be dumped back to the unconnected state.
Will need a work around. Maybe need to poke upstream to ensure my facts are right
Seems that ENET's maximum connections is how many connection slots that will be used by the server. Connecting and then disconnecting clicks down the remaining slots.
ie. 4 slots = 4 connection capacity, no more after that. Not "I can run 4 connections at the same time".
For example, using Mirror's example pong scene and connecting to the same server more than 4 times will cause the transport to be dumped back to the unconnected state.
Will need a work around. Maybe need to poke upstream to ensure my facts are right