Perhaps related to https://feedback.bistudio.com/T121717
This is new to 1.66.
When players disconnect MP missions, their bodies become AI, even with disabledAI = 1; in description.ext. This seems related to using selectPlayer to move a player into a new character.
The HandleDisconnect event is not firing in this case, so scripts are not informed of disconnects for cleanup tasks.
Example:
addMissionEventHandler ["HandleDisconnect", { diag_log "Fired"; false}];
This event won't fire, and the abandoned body becomes AI - it does not die.
addMissionEventHandler ['PlayerDisconnected',{
params['_id','_uid','_name','_jip','_owner'];
blub
}];
seems to work tho :)
Yes this is the exact same issue that occurred in previous arma version perf build 1.
Which was reverted
The eventhandler never fires and ai unit takes over.
Depending on your test mission, when you reconnect in the same slot player will take over the ai unit.
Might explain how it missed QA Testing ;)
This is also occurs in the latest dev branch
Hello,
yet again, I am unfortunately unable to reproduce this.
Would you mind to upload a simple repro mission (as simple as possible) that could demonstrate the issue?
I have tried to create a simple repro mission
4 Playable units
init.sqf
addMissionEventHandler ["HandleDisconnect", { diag_log "Fired"; false}];
description.ext
disabledAI = 1;
Connected with 2 players, one disconnected afterwards.
"Fired" was correctly logged in the RPT file of the server. Player 2 unit died, AI did not take over.
If you can please try to provide the repro mission or fill in possible blanks in my repro mission.
Thank you
Could it be that this is also related to "selectPlayer"? Switch from the unit you get from the lobby slot to another and then disconnect.
selectPlayer must be used to transfer the player to a new body. Then all these new open issues reproduce.
More specifically, if the original player-assigned body is deleted (using deleteVehicle) the server stops receiving disconnect events from the player and their new body.
However, if the original body is kept around (usually this is a virtual or invisible body) the disconnect events propagate correctly.
Here's a repro Altis mission. Mod for server and client included.
Run server with client+server mod.
Run client with client mod.
Join server.
After joining and receiving a body, Disconnect. (do not respawn)
Look at server rpt logs - You should see a Disconnect event logged.
Look at client code in Init\fn_preInit.sqf
If you comment/uncomment the deleteVehicle line, you can affect the behavior of the disconnect event.
After the client disconnect, also note that the player's body is AI. It should have been killed / freed up by the server due to the DisableAI setting. But the zombie remains.
And when i come back in my server, i can look myself in the face, and say hello.....
It's annoying, players become AI's after leaving the server. And when a player dies, he sees a blurry screen, even when he re-spawns.
after re-spawn, the player has to leave the server, and restart the game to see normal again.
This reconnection results in a new AI after leaving .........
After update 1.66 the loading screen also changed....
I only host exile: Altis, but the loading screens shows: Tanoa
Probably obvious, but the allPlayers list is incorrect after a player dies and respawns into spectator after this. The player that dies or respawns into spectator has their UID empty, and their name is ERROR: No unit.
This is causing our system to kick spectators because their player information appears invalid. (they have no UID and no name)