If Headless Client is kicked/rejoins, HC spawns as seagull and game logic is assigned clientID of server.
Description
Description
Details
Details
- Legacy ID
- 2001327165
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Always
- Category
- Engine
Steps To Reproduce
- Setup a dedicated server + headless client per BIKI (https://community.bistudio.com/wiki/Arma_3_Headless_Client)
- Create a mission with player and playable Headless Client Game Logic
- Start server + headless client and join server
- Run diag_log (owner h1) from server = clientID is Headless Client
- Kick the Headless Client from server, it will auto rejoin
- Notice HC is connected to proper slot but spawns as seagull (HC RPT: 14:13:25 creating seagull (no person))
- Notice diag_log (owner h1) from server returns clientID of server
Additional Information
This can pose an issue if one were to setGroupOwner to HC and the HC disconnects/reconnects as all AI on HC will transfer locality to server automatically. With this bug, the AI cannot be transferred back to the HC as the HC game logic's clientID = dedicated server clientID.