Attention Soldiers!

Please type: "!FWR" In the In-Game Chat to Report a False Warning, we will be logging certain events to isolate the issues and this will help us to easily pick out the ones that are wrong.

A lot of time and help from qsek has been put into fixing the bugs in this script on Wake Island but frustratingly we still get false-warnings from time to time.

Hopefully, we are getting less false-warnings now that I have moved us to a higher-performance server on which the AutoAdmin is running.

However, it would be really helpful if you could share (in as much detail as possible) any experiences you have or see when the warning goes off and it shouldn't. This will help us to locate any remaining issues in the script. To do so you will need to pay attention to who is doing what in the server, who is in what vehicles, kills & deaths etc.

Some things to think about:
1) What was the attacker doing exactly?
2) What was/were the victim/victims doing exactly?
3) Did the victim/victims swap vehicles?
4) Did the victim/victims get killed as infantry or in an aircraft before?
5) If so, was that by the same attacker?
6) Was it in a protected area? Helipad or Runway or was it somewhere else? In the air? On the ground?

The more detail you can give the better. Basically, we are trying to workout the logic behind what is happening and why it is triggering a false warning. If you have an idea as to why, don't be afraid to say it, any suggestion is potentially helpful.

Cheers,

5tarLine

I have noticed that the warnings seem to be a bit keener now, (more of them )

More false warnings or more accurate warnings?

The only thing I can input as of yet is I have been warned and kicked from the server for "Destroying grounded aircraft". However, I actually shot the enemy jet down in the sky above arty island (btw it was a J-10 so it was far away from the "protected zone". This occurs extremely frequently to me as I spend a lot of the time in the jet, so I notice a lot of warnings from time to time, all of them being away from the protected zone.

I can't determine what the cause of this error is, but how far does this so-called 'protected zone' expand to, of-course it should only be the Airfield or the Carrier, but are the values in the script producing a much larger protected zone which expands further than it should?

From my many experiences, here are some answers to the questions:

1) What was the attacker doing exactly? Flying an F35, pursuing a J-10 from the airfield, around the map for a while then destroying the enemy J-10 in the air above 'Beach'

2) What was/were the victim/victims doing exactly? Flying away like a headless chicken in their unsuccessful attempt to escape.

3) Did the victim/victims swap vehicles? Nope.

4) Did the victim/victims get killed as infantry or in an aircraft? The F35 destroyed the jet above Beach, with the pilot still in the J-10 at the time.

6) Was it in a protected area? Helipad or Runway or was it somewhere else? In the air? On the ground? In the air (above 'Beach' for this example).
_______________________

This is all the info I can give at the moment, however I'll be sure to post some screenshots in the near future if I experience this bug again.

Thank-you Mitch, this is exactly the type of thing we need to look at and investigate. I have also noticed that the warning seems to like triggering around the arty-island in particular. It's strange because there are no zones around the arty-island but it must be getting mixed up with another part of the AutoAdmin.

The value for the zones are accurate, if you go to the Wake Island Rules topic you can see the size of the zone around the carrier. The Grounded Aircraft Protected zones for the Chinese at airfield are also pretty pinpoint at ground level and shaped around the helipads/runways.

Interestingly, I have also noticed the warnings triggering close to beach and specifically close to the UAV Asset. I think in that case we will need to see if it's getting confused with any of the asset locations (artillery / UAV Scanner).

Please try (as well) to keep an eye on what the victim/attacker has been doing previous to that death in terms of vehicles and other deaths / game-play before the warning is triggered. This should help us find other bugs too.

Will keep an eye on it, but most of the time it's working well.

Accurate or false, both, just more of them, I find the guys atracking grounded aircraft are picked up more often

i´m pretty sure this issue is appearing when:
You are killing a J10 anywhere on the Map
AND
J10 #2 is on the PLA Runway either standing with a pilot inside or just Rolling for the Takeoff.

Since that issue is not happening to any PLA Pilot.
Because they aren´t allowed to kill a Jet right onto the US Carrier.

That issue happens to me even when players use the chinese attack chopper.
A few days ago I killed a chopper near south base (got kicked because it was the 3rd warning) and near north base (4th warning)

The victims were Kaasentra and Tai-Lung. Maybe they can describe what they have done before?

Killed a helicopter that was flying at around 180 altitude - far from grounded - south-west of the airfield, just above the sea (I took the screen two seconds after shooting them).


Date of picture if you can go back on the the battlerecorders: 17.56h (UCT+1) 26/12/2016