I moved a lancer fwrd a hex and he anarchied, I had another lancer BG nearby, that lancer then anarchied all by himself (ie I didn't hit end turn nor select the unit....) I call it proximal anachy
_[NAB] Anarchy BUG v1.8.12.818 bRC6u03
Moderators: Slitherine Core, FoG PC Moderator, NewRoSoft
-
TheGrayMouser
- Field Marshal - Me 410A

- Posts: 5001
- Joined: Sat Nov 14, 2009 2:42 pm
_[NAB] Anarchy BUG v1.8.12.818 bRC6u03
Playing MP game
I moved a lancer fwrd a hex and he anarchied, I had another lancer BG nearby, that lancer then anarchied all by himself (ie I didn't hit end turn nor select the unit....) I call it proximal anachy
I moved a lancer fwrd a hex and he anarchied, I had another lancer BG nearby, that lancer then anarchied all by himself (ie I didn't hit end turn nor select the unit....) I call it proximal anachy
Re: _[NAB] Anarchy BUG v1.8.12.818 bRC6u03
This is not a bug, but a new feature added into rev 818 
The new adjacent FBG anarchy charge rule (same idea as the adjacent FBG rout rule, or the adjacent FBG commander death one) states that each time when a friendly BG anarchy charges, it's FBG neighbours able to anarchy charge are tested for anarchy charge too, introducing the possibility of chain anarchy charges (with countless historical occurrences) and making a commander presence near the battleline a little bit more important.
// - added GP.AdjacentFBGAnarchyCharge() <<// GAMEPLAY RULE - [Anarchy Charge]: a BG must take an ACT if any adjacent friendly BG anarchy charges>> rule
You could also see it in the console log's if you would have following it.
The new adjacent FBG anarchy charge rule (same idea as the adjacent FBG rout rule, or the adjacent FBG commander death one) states that each time when a friendly BG anarchy charges, it's FBG neighbours able to anarchy charge are tested for anarchy charge too, introducing the possibility of chain anarchy charges (with countless historical occurrences) and making a commander presence near the battleline a little bit more important.
// - added GP.AdjacentFBGAnarchyCharge() <<// GAMEPLAY RULE - [Anarchy Charge]: a BG must take an ACT if any adjacent friendly BG anarchy charges>> rule
You could also see it in the console log's if you would have following it.
-
TheGrayMouser
- Field Marshal - Me 410A

- Posts: 5001
- Joined: Sat Nov 14, 2009 2:42 pm
Re: _[NAB] Anarchy BUG v1.8.12.818 bRC6u03
cothyso wrote:This is not a bug, but a new feature added into rev 818
The new adjacent FBG anarchy charge rule (same idea as the adjacent FBG rout rule, or the adjacent FBG commander death one) states that each time when a friendly BG anarchy charges, it's FBG neighbours able to anarchy charge are tested for anarchy charge too, introducing the possibility of chain anarchy charges (with countless historical occurrences) and making a commander presence near the battleline a little bit more important.
// - added GP.AdjacentFBGAnarchyCharge() <<// GAMEPLAY RULE - [Anarchy Charge]: a BG must take an ACT if any adjacent friendly BG anarchy charges>> rule
You could also see it in the console log's if you would have following it.
Uh, OK, not saying I dont like the concept BUT perhaps it might be an optional rule like how ddouble moves etc are optional?
I know alot of players hate anarchy altogtehr and you will have an uprising!
-
Turk1964
- Lieutenant Colonel - Fw 190A

- Posts: 1138
- Joined: Tue May 18, 2010 1:14 pm
- Location: Victor Harbor South Australia
Re: _[NAB] Anarchy BUG v1.8.12.818 bRC6u03
Yes this is what used to happen and you would end up with a whole line of Offensive spearmen commiting suicide. Im pretty sure it was toned down to prevent this in the current version of Fog.Like TGM says you will have a riot on your hands if you introduce mass Anarchy charges....
Re: _[NAB] Anarchy BUG v1.8.12.818 bRC6u03
I think you guys are jumping to conclusions without having played with it first.
Anarchy charge chance was toned down, first of all, so it is less likely it will happen in the first place. And only then, if an anarchy charge happens, the adjacent anarchy charge is triggered, and these adjacent units will not anarchy charge directly, but they will just be tested for anarchy charge too.
Historically speaking, that's what was happening. Not single units anarchy charges only, but groups of units following one who anarchy charged into a sort of local mass anarchy charge.
Anarchy charge chance was toned down, first of all, so it is less likely it will happen in the first place. And only then, if an anarchy charge happens, the adjacent anarchy charge is triggered, and these adjacent units will not anarchy charge directly, but they will just be tested for anarchy charge too.
Historically speaking, that's what was happening. Not single units anarchy charges only, but groups of units following one who anarchy charged into a sort of local mass anarchy charge.
