Hi, since Exp. 1.3 you had to restart Workbench everytime you made changes. Otherwise PeerTool will no longer work.
In 1.2. this was only neccessary if you do changes on RPL Prefabs. But now there is a problem with duplicated Player Ident. (See Screen)
RPL : ServerImpl event: authenticating (identity=0x00000000, address=127.0.0.1:59830)
RPL : ServerImpl event: connected (identity=0x00000000)
WORLD : UpdateEntities
WORLD : PostFrame
WORLD : UpdateEntities
NETWORK (E): Trying to register connection of possibly unauthorized client.
NETWORK : Player connected: connectionID=0
NETWORK : ### Connecting player: connectionID=0, Name=
WORLD : UpdateEntities
WORLD : PostFrame
WORLD : UpdateEntities
RPL : rpl::Pip::ProcessNetToGame
DEFAULT (W): Another connected player with the same identity found. Dropping this connection request and disconnecting the client
WORLD : UpdateEntities
WORLD : PostFrame
WORLD : UpdateEntities
RPL : rpl::Pip::ProcessNetToGame
DEFAULT : Disconnecting identity=0x00000000: group=6 reason=2
NETWORK (W): RplAuthBackend::OnFailure called (identity=0x00000000, group=6, reason=2)
NETWORK : Player disconnected: connectionID=0
NETWORK : Total number of players: 1This is most probably because authentication with backend passes before client connect to the server and since both client have same Identity ID it will not allow second one to join.
You can try running with -noBackend CLI https://community.bistudio.com/wiki/Arma_Reforger:Startup_Parameters#noBackend
Not exactly sure why it is happening on 1.3.0 but recently there is lot of refactors around these systems so probably some change is now causing it to happen.
But that would be considered as correct behavior and previously it was working due to race condition.
Hi, so this is related to the BackendID?
**string playerUID = GetGame().GetBackendApi().GetPlayerIdentityId(playerId);**
Because in 1.2 the PeerTool Client did not get one. So this ID was always empty.
Update: running PeerTool with "-noBackend" works. But I'm not sure if that's what was intended.