AW Auto Placement is not working at all

Jaxugar

Even though the option to Auto place defenders in aw is enabled, we had to manually place defenders every war. Due to this issue some of us are missing out on Placement which is costing our alliance that war. It's back to chasing members again after we were all made to be used to the Auto placement feature INTRODUCED BY THE GAME TEAM.
Kindly fix it ASAP

SummonerNR

Under what circumstances are you expecting Auto-Placement to work ?

(and WHICH war ? The 1st of season, which was bugged and used people's OFF-Season setting for that 1st war ? and might not be counting anyways, they are still discussing that war)

Did you move UP (or DOWN) to the next War Tier Map ?
That is when Auto-Placement is designed to carry-over your defense placements from the former Tier Map, and put those same defenders onto same nodes in the new +/- Tier Map that you have just moved to.

So that people don't have to worry about placing into the adjoining +/- Tier Maps, only have to worry about placing into a single “Current” Tier Map.
(with Auto-Placement setting, the +/- Tier buttons aren’t even available, only 1 current map is)

Without further explanation of what happened, will just say that it is NOT designed to go and pull random champs out of people's rosters, and put them randomly onto map nodes.
Similarly, it is NOT meant for automatically doing that for any New Members you bring in either.
Everyone still has to have a set of Defenders in place somewhere on the Current Map (or what was “Current” at the time they placed, and was still Current as of when Alliance had put setting to Auto-Placement).

**oh, and there is another setting (forget exact wording) called “remove everyone's champs from defense map when the war is over”. (might be on a per-BG setting basis).
That would allow 1 BG or 2 BG Ally's to do wars where they let people switch in and out every war.
That setting clears out a BG's defense, so that different people can place defenders for the NEXT war.
(* so maybe your Ally had inadvertently turned that setting on as well ???)