Caching also has a security problem as i described in https://feedback.bistudio.com/T133807

I agree this should be changed. It is a control change still not done.

I agree this should be changed. It is a control change still not done.

I agree this should be changed. It is a control change still not done.

I agree this should be changed. It is a control change still not done.

I agree this should be changed. It is a control change still not done.

I agree this should be changed. It is a control change still not done.

The "fix" with the new compile syntax is not really a fix. Noone will update their code to that, same as noone (relatively speaking) updated their 5 year old code to parseSimpleArray.
Also unless that syntax is used in CfgFunctions every Mission launch that has its own functions still clutters the cache.
Not to think about execVM and eventhandlers and addAction and everything else that I can't even think of right now.

It doesn't appear anyone has event looked at this issue. I'd appreciate it if we at least got a response. Even if it was just to say it won't get fixed.

In T125680#1808800, @Wulf wrote:

Both Achievments work on the latest Dev branch of the game give them a try.

Both Achievments work on the latest Dev branch of the game give them a try.

In T84155#1808738, @TheSpiritof69 wrote:

@fire-39_1 Which is impossible to do if your "static IP" is a v4 address behind carrier-grade nating and you *cannot* set up port forwards. Typically the case with ISP that are using DualStackLite to connect their customers.

nope, I have not found a work around for this. Still having the issue.

@fire-39_1 Which is impossible to do if your "static IP" is a v4 address behind carrier-grade nating and you *cannot* set up port forwards. Typically the case with ISP that are using DualStackLite to connect their customers.

@fire-39_1 this has nothing to do with port forwarding or a static IP, but people switching (or being forced to switch) to the new IPV6 Protocol which ArmA doesn't support. :-)

I self host for friends all the time. Can be done by setting up a static IP and forwarding ports on your router. Sometimes connecting clients will connect and drop without giving an error, I find that if you (the host) are in the mission select screen and not the slot-in screen of the mission while others are connecting they will stay connected. Use the instructions for Arma 3 from this site>> https://portforward.com/

I have this same issue. Anytime I try to put down a marker, open chat, or hit escape, the aircraft throttles down for helicopters and max throttle for planes. As fire-39_1 stated, it appears to be related to analog binding. I reverse thrust for helicopter and plane.

@Bohemia Any chance of this becoming a thing? A growing userbase can't host private servers anymore.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.