Project

General

Profile

Bug #2055

[MP] Multiple instances can't connect to a local server

Added by vermil about 5 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
2015-05-16
% Done:

0%


Description

Multiple instances of Dday running on the same computer can't connect to the same server; Dday immediately disconnects the second player citing a duplicate connection.

In this case, the shell console interestingly incorrectly lists this second players connection time as the time the first player has currently been connected for.


Related issues

Related to Bug #1980: Client should refuse to use the same userdir as another already running clientNew2015-02-16

Related to Feature #2057: Multiple client instancesNew2015-05-16

History

#1 Updated by skyjake about 5 years ago

  • Related to Bug #1980: Client should refuse to use the same userdir as another already running client added

#2 Updated by skyjake about 5 years ago

  • Tags set to Multiplayer, Client
  • Subject changed from [Multiplayer] multiple instances can't connect to a local server to [MP] Multiple instances can't connect to a local server

Client identification is determined by the client.id file in the runtime folder. When you were running multiple instances, did they have different userdirs and if so, were the client.id files different, too?

It is safe to delete client.id. A new random one will be automatically generated.

#3 Updated by skyjake about 5 years ago

#4 Updated by skyjake about 4 years ago

  • Target version set to 2.1 (Late 2018)

#5 Updated by skyjake almost 2 years ago

  • Target version changed from 2.1 (Late 2018) to Multiplayer

Also available in: Atom PDF