Whenever a mission is launched, and the Headless Client is already on the server, it automatically jumps into a slot (seems it is the first slot in the mission.sqm?).
That slot disappears from the slotting screen, even if the HC is manually moved to another slot, and cannot be accessed anymore.
Moreover, ForceHeadlessClient = 1; doesn't work: the slot with this line is greyed out in the slotting screen and nobody can access it. {F22226}
Create any mission with multiple playable slots.
Edit the mission.sqm to have one slot with forceheadlessclient = 1;
Connect the HC to the dedicated server.
Launch the mission.
This has been observed on the Stable branch. Any repro on the Dev branch is most welcome.
Experience the same issue on Stable 1.04.111746
Very simple MP mission with 3 units on the map, no scripts etc.
2nd unit config:
id=1;
side="WEST";
vehicle="B_Soldier_F";
player="PLAY CDG";
forceHeadlessClient=1;
leader=1;
skill=0.60000002;
text="Unit_2_hc";
description="Unit_2_hc";
Expected behavior:
HC will connect automatically in 2nd player slot
Observed behavior:
(This slot disappears from selectable players even if hc is dragged to other slot)
Removing "forceHeadlessClient=1; " from 2nd unit
Observed behavior:
(This slot disappears from selectable players even if hc is dragged to other slot)
Found this out with some unrelated testing, not necessarily directly useful but you never know...
If the mission has joinUnassigned=0 and disabledAI=1 in its description.ext, the headless client is able to automatically join "properly" (as in, spawns as a player in game).
Note that just joinUnassigned=0 on its own isn't sufficient.
Tested in V1.24 and you must join two times... first join the HC go to the first not "forceHeadlessClient=1" Unit and the second try he is on the rigth slot...
Update for 1.30: HC doesn't autoassign (if the mission has the default value for joinUnassigned) but also doesn't make a slot disappear.