Did you edit anything within the mission files?
No.
If yes, what did you edit exactly?
Short Issue Description
When a player with an AI squad is incapacitated the AI takes command and then spams the player's chat and voice channel with "Taking command" and/or "I'm the new actual" in a continual loop until command is re-established following revive or respawn.
Expected Behaviour
AI should report "Taking command" only once.
Steps to Reproduce the Issue
Build one or more AI squad members. Become incapacitated in battle or via a self-inflicted method... personally I like vaulting from the roof of a cargo tower :)
Screenshots, Serverlog or any other helpful Information
The issue occurs regardless of which player slot is selected.
I think this issue occurs on all maps, in both local and dedicated games, and dating back several versions of the mission. Some time over the past year or so running Tanoa (0.954), Malden (0.955) and then Takistan (0.961 & 0.963) campaigns on a dedicated server I started to notice this spamming. All other players have commented on it as well. I had made many edits to mission files so I assumed the error was my own and didn't document it.
Yesterday, while setting up our next campaign on Chernarus and prior to making any of my usual edits the issue occurred again. I figured a formal test on Altis would be the best way to rule out any mod interaction - which seems to be the case.
In order to determine how AI is intended to behave in a purely "vanilla" Arma environment and rule out "Arma just being Arma" I created a simple mission with the same multiplayer attributes as are set in KP Liberation via the default mission parameters...
Respawn = Respawn on custom position
Revive mode = Enabled for all players
Incapacitation mode = Basic
These are the only ones I thought would/could be connected to issue. Repro-ing in this vanilla mission results in the expected behaviour: my AI squad-mate only announces "Taking command" once.
During a quick check of 0.954 (Tanoa) today I did not encounter the problem. However, I'm pretty sure it was an issue for us on Malden (0.955) and it is definitely happening on Takistan (0.963). Therefore, if the problem does stem from some Liberation coding I think it may be something that was introduced in 0.955.
Basic Information
Mission version: 0.963 Map used: Altis Mods used: none Dedicated or local game: local Source of the mission file (URL): Steam workshop http://steamcommunity.com/sharedfiles/filedetails/?id=878714108&searchtext=kp+liberation+altis
Individual Things
Did you edit anything within the mission files? No.
If yes, what did you edit exactly?
Short Issue Description
When a player with an AI squad is incapacitated the AI takes command and then spams the player's chat and voice channel with "Taking command" and/or "I'm the new actual" in a continual loop until command is re-established following revive or respawn.
Expected Behaviour
AI should report "Taking command" only once.
Steps to Reproduce the Issue
Build one or more AI squad members. Become incapacitated in battle or via a self-inflicted method... personally I like vaulting from the roof of a cargo tower :)
Screenshots, Serverlog or any other helpful Information
http://steamcommunity.com/sharedfiles/filedetails/?id=1336035535
The issue occurs regardless of which player slot is selected.
I think this issue occurs on all maps, in both local and dedicated games, and dating back several versions of the mission. Some time over the past year or so running Tanoa (0.954), Malden (0.955) and then Takistan (0.961 & 0.963) campaigns on a dedicated server I started to notice this spamming. All other players have commented on it as well. I had made many edits to mission files so I assumed the error was my own and didn't document it.
Yesterday, while setting up our next campaign on Chernarus and prior to making any of my usual edits the issue occurred again. I figured a formal test on Altis would be the best way to rule out any mod interaction - which seems to be the case.
In order to determine how AI is intended to behave in a purely "vanilla" Arma environment and rule out "Arma just being Arma" I created a simple mission with the same multiplayer attributes as are set in KP Liberation via the default mission parameters...
These are the only ones I thought would/could be connected to issue. Repro-ing in this vanilla mission results in the expected behaviour: my AI squad-mate only announces "Taking command" once.
During a quick check of 0.954 (Tanoa) today I did not encounter the problem. However, I'm pretty sure it was an issue for us on Malden (0.955) and it is definitely happening on Takistan (0.963). Therefore, if the problem does stem from some Liberation coding I think it may be something that was introduced in 0.955.