Probably both category Inventory and Savegame/Loadgame, but I'll opt for the latter in this case.

Did I understand right, the problem arises when you both use addRating OR setFriend? It seems extremely odd to me, that both commands independently cause you to be unable to use vehicles or parachutes (I could not try a repro myself, it would help if you attached a mini-mission).

Can you verify that there is not another issue to the mission?

Your ticket has the wrong title. You're looking for a solution to your scripting problem. Please use the BI forums for that (http://forums.bistudio.com). I'm sure there is a solution for that already (e.g. EH handleDamage).

I suggest we correct the description and then analyze your issue.

Fixed title for you.

My question is if you're not simply doing it wrong and if the issue you observed is by design.

Dupe of #7773.

Dupe of #17661.

Closing then. Thanks.

Still unfixed?

EDIT: Please specify if this issue is related to the original ticket or simply a misfeature.

Closing down this one then. Thanks highhead!

Keep your head high, highhead. There seems to be an issue and you're probably not the only guy(s) interested in a fix, the the CBA team is looking into it anyway.

Once we have a reliable repro, BI devs can have a look. Maybe there is no reliable repro, but 'we' get it to reproduce without any mods and then we know it might be a racing condition within the engine (which would be my guess).

Geez. Why can't people just test vanilla...waiting with resolved until we're sure there's no engine involvement to this issue.

Setting to (already) resolved then.

Freezing the client for a second on weather change should be its own ticket, but they're probably aware of the issue.

Resolved according to Techrep 6.

Resolved according to Techrep 6.

Resolved according to Techrep 6.

Yep, false alert, all is good, even though it doesn't really make sense if they're on a roof which is so obscured from the scene with the pickup, so they could impossibly ever have shot there from that roof where they were this time.

Ohh, okay. Maybe I've not been too persistent in searching them, due to the fact that the one house with chairs and map on flipchart really looks predestined for them (where I found the the first time).

Will re-verify then and give feedback.

Yes, I've searched the area to no avail. But due to placement of mines and other props, I don't believe they're randomized, in this case.

<edited, rhetorical question>

Resolved according to Techrep 6.

I noticed if you lower AI skill in custom difficulty to 0.4 with precision 0.2, it gets "better".

I don't think versioning related to existing savegames is implemented. While for some this would be nice but OTOH the users would never see or receive an updated/fixed mission while they still got a savegame.

IMO it should ask if it should update the mission if a savegame is still around instead of mindlessly overwriting it.

My question would be if the mission was updated for real or just been refreshed from Steam workshop.

To my understanding, if there's a new mission file with changed content, you cannot use an old save with it - it would make no sense, the entire state is fubar.

Or did I misunderstand something?

Resolved according to todays DEV changelog.

Dupe of #17661.

What's the matter with everyone thinking they have the right to assign tickets to whoever? Just pull the ticket and wait in line, don't assign them by yourself. Thank you.

EDIT: Specially if the ticket is of such bad quality.

Well, this might be what's needed to make it MP playable for actual MP campaign. So we don't know if those options/vars would work, if nobody tried them.

Taking the SP campaign as a measure for missing MP campaign options is not valid IMO, as the SP campaign has many solo parts, where not even a second AI is present to make it a potential COOP campaign.

Hence waiting for feedback...

Removing off-topic comments. This is not about the official campaign, which will allegedly never COOP.

Sorry then, I could swear I've read changelog entry that would say that rain effect was excluded from NVG...

I believe the rain effect has been excluded from night vision.

Thanks.

That means, I find it a well-written ticket.

Thanks, marking resolved.

Please do not assign tickets yourself. Thank you.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Dupe of #17765

Closing as fixed.

Sounds like an attachTo bug.

Which campaign episode is that?

I can't see a difference between the two uploaded pictures; both have the same light at the briefing table.

It might be a graphics/monitor setting issue, or it simply overblends the existing light.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Closing as fixed.

Does the hotfix work?

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Resolved according to Zeus Manual.

https://community.bistudio.com/wiki/Arma_3_Field_Manual_-_Zeus#Pinging_Zeus

Mass-close of resolved tickets not updated in last two weeks.

Duplicate.

This might be by design then, if, in your example, all AI units are in danger mode?

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Try repairing your A3 copy:

Right-click on "Arma 3" in your Steam Library and select "Properties", on tab "Local Files" press "Verify Integrity of Game Cache...".

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass-close of resolved tickets not updated in last two weeks.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass-close of resolved tickets not updated in last two weeks.

I can confirm that this happens, but I know this is by design; e.g. with AI the next in line assumes control over the squad, which is a MUST; with humans this happens normally too and makes sense, since ArmA is not always respawn by design.

I'm not sure if this could/should be solved by the mission maker. Then again it would be very sexy if this is an option if respawn is enabled. This makes this ticket rather a feature request, but to be treated as such, it would have to be rephrased entirely, including the additonal option for respawn modes.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass-close of resolved tickets not updated in last two weeks.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass-close of resolved tickets not updated in last two weeks.

Can you elaborate more on which mission you were playing, what you were doing?

EDIT: What is "wacking space laod"?

Mass-close of resolved tickets not updated in last two weeks.