Obsolete

[Turk1964]

DIVISION B

Challange up for Iandavidsmith versus my Lombard Barbarians password=Lombard

Cheers Turk

[fogman]

I respect all opinions on the split hex rear charge but ive seen it on more than one occasion lately and feel although its not as common as it once was it still exists.

Cheers Turk

True dude but against the pc i tried it with both drilled and undrilled troops one hex at a time and it wouldnt let me chrage even with drilled however it die allow me to come boring in from an angle in one move then turn and align on impact

I now understand why sometimes there is automatic disruption, other times there isn't. it is working perfectly well because since this came to my attention i have been able to predict the outcome with 100% accuracy.

Concretely, my experience has been that if you start directly behind there will be automatic disruption. If you start on its flank there will be no disruption: your straight path leads you to its rear and if there's no enemy units in your front your unit turns to face its rear. Small sample though. I had assumed there was a cohesion test.

[rexhurley]

Ahhh first the irish, then the Wallabies and Saffers now the meek and weak Welsh fall to the mighty AB's

[klayeckles]

Div B
Pontic (44/51) VS Macsen, Roman (41/38)

pontic snuck out a victory

[klayeckles]

Philoi or scipioasinus....
you ready for a game?
i have one up for one of you...first to take it gets it...
PW: pontic

[ericdoman1]

Div A

eric (Dailami Buyids) 21/35 vs cavehobbit (fatimid Egytptian) 40/38

Again a tough game and a lot closer than it looks

[rexhurley]

No win's for Okie here, all lost.

you just bet me so post it

[caiko]

Division (C)


Caiko (Jewish Revolt) 101/106 vs Bagration (Bosporan) 44/44

Jewish Win

[Mike48]

fogman (medieval germans) 10/47 vs rom1944 (medieval aragonese) 41/38

aragonese marched up, knights on the right, armoured spears in the centre, and impact foot catalans on the left through rough terrain, intending to envelop the germans. but swiss pikes struck first swiftly charging through the middle and smashing the aragonese spears. aragonese knights tried to disengage but with catastrophic results. catalans did most of the damage but were stopped by heavy cavalry upon emerging into the open.

challenge up for mike48
pw: tannenberg

Well found the challenge.
Thank you for the game.
Mike.

[batesmotel]

I respect all opinions on the split hex rear charge but ive seen it on more than one occasion lately and feel although its not as common as it once was it still exists.

Cheers Turk

True dude but against the pc i tried it with both drilled and undrilled troops one hex at a time and it wouldnt let me chrage even with drilled however it die allow me to come boring in from an angle in one move then turn and align on impact

I now understand why sometimes there is automatic disruption, other times there isn't. it is working perfectly well because since this came to my attention i have been able to predict the outcome with 100% accuracy.

The split move rear charge bug was fixed in the last update with the Scenario Pack release. See the on line help for what is required for a rear charge to cause an automatic cohesion drop. Basically the charging BG must start in a hex row behind the one the target is in. If you move to a rear hex but did not start in a row behind the target, you get the ++POA advantage for rear contact but no automatic drop. There is a possible post combat drop for the loser (in addition to the automatic drop if any) in the combat if it fails to pass its cohesion test.

Chris

[dave_r]

Okie's wins in Medieval:
Okie 3/28, 11% to Mike48 40/37, 100%
Okie 5/28, 18% to Daver 34/32, 100%
Okie 24/28, 86% to Supervak 39/32, 100%

I'm afraid you are going to have to replay the game against me! The settings weren't correct so the game is null and void.

[ianiow]

Div A Imperial.

Challenges posted vs my Lombards for:-

Klayeckles, Triarius, Batesmotel, Morbio and Sharkall.

pw ianiow

Good luck!

[bagration1812]

Still recovering from PTSD over coming from WAY ahead to lose to Caiko's horde of Hebrews... Very nice comeback.

I need to play lydianed. Set up a game: PW lydianed

[ericdoman1]

Division A

eric (Later Seleucid (post 166BC)) (46/49) vs ianiow (Classical Spartans) (61/61)

This was a truly remarkable game. At one stage I had about a 20+ bp advantage with number of good combats in my favour to near enough win the game BUT I was unable to win combats, rear attacks then fisnihed them off and the bp advantage was narrowinga nd narrowing until Ian was actually in the lead. Finally I got it by just killing 1 casualty froma poor lf bg that auto rout. If that Hadn't had happened it could well have beena draw or NIGHTMARE a win for Ian. What a comeback, well palyed.

[Turk1964]

The split move rear charge bug was fixed in the last update with the Scenario Pack release. See the on line help for what is required for a rear charge to cause an automatic cohesion drop. Basically the charging BG must start in a hex row behind the one the target is in. If you move to a rear hex but did not start in a row behind the target, you get the ++POA advantage for rear contact but no automatic drop. There is a possible post combat drop for the loser (in addition to the automatic drop if any) in the combat if it fails to pass its cohesion test.

Chris

Yep thats right Chris this is whats supposed to happen,but ive seen it happen with my own eyes and A1 did it to me aswell.Strated in front hex chased a skirmished off stopped pivoted and changed direction hit Cats in the rear and dropped 2 cohesion levels to Fragged.I will admit i havent seen it often but lately ive seen it 4 times,3 times in a recent game.

[ericdoman1]

The split move rear charge bug was fixed in the last update with the Scenario Pack release. See the on line help for what is required for a rear charge to cause an automatic cohesion drop. Basically the charging BG must start in a hex row behind the one the target is in. If you move to a rear hex but did not start in a row behind the target, you get the ++POA advantage for rear contact but no automatic drop. There is a possible post combat drop for the loser (in addition to the automatic drop if any) in the combat if it fails to pass its cohesion test.

Chris

Yep thats right Chris this is whats supposed to happen,but ive seen it happen with my own eyes and A1 did it to me aswell.Strated in front hex chased a skirmished off stopped pivoted and changed direction hit Cats in the rear and dropped 2 cohesion levels to Fragged.I will admit i havent seen it often but lately ive seen it 4 times,3 times in a recent game.

This needs to be sorted out, although this example looks accidental.

I myself have still not seen it and may well try a few more scenarios but if it is being used and has not been debugged, it has to stop.

Once more players using it will have to forfeit their games, that is will lose 3 vs 0. Not sure what to do with bps inflicted etc when this happens.

It had been covered in Season 9 and has now been covered quite a bit on all LOEG links.

If players have used it because they hadn't read the rules, "Season 9". They should own up and I will give them the benefit of the doubt so they can replay the game BUT after the numerous posts in various LOEG Season 9 - Communications ..... Players ares still intentionally using it, their game is forfeited, they lose 3 vs 0.

Please make this clear to all players whom you are playing, again as was pointed out in Season 9.

[ericdoman1]

The split move rear charge bug was fixed in the last update with the Scenario Pack release. See the on line help for what is required for a rear charge to cause an automatic cohesion drop. Basically the charging BG must start in a hex row behind the one the target is in. If you move to a rear hex but did not start in a row behind the target, you get the ++POA advantage for rear contact but no automatic drop. There is a possible post combat drop for the loser (in addition to the automatic drop if any) in the combat if it fails to pass its cohesion test.

Chris

Yep thats right Chris this is whats supposed to happen,but ive seen it happen with my own eyes and A1 did it to me aswell.Strated in front hex chased a skirmished off stopped pivoted and changed direction hit Cats in the rear and dropped 2 cohesion levels to Fragged.I will admit i havent seen it often but lately ive seen it 4 times,3 times in a recent game.

This needs to be sorted out, although this example looks accidental.

I myself have still not seen it and may well try a few more scenarios but if it is being used and has not been debugged, it has to stop.

Once more players using it will have to forfeit their games, that is will lose 3 vs 0. Not sure what to do with bps inflicted etc when this happens.

It had been covered in Season 9 and has now been covered quite a bit on all LOEG links.

If players have used it because they hadn't read the rules, "Season 9". They should own up and I will give them the benefit of the doubt so they can replay the game BUT after the numerous posts in various LOEG Season 9 - Communications ..... Players ares still intentionally using it, their game is forfeited, they lose 3 vs 0.

Please make this clear to all players whom you are playing, again as was pointed out in Season 9.

[ericdoman1]

The split move rear charge bug was fixed in the last update with the Scenario Pack release. See the on line help for what is required for a rear charge to cause an automatic cohesion drop. Basically the charging BG must start in a hex row behind the one the target is in. If you move to a rear hex but did not start in a row behind the target, you get the ++POA advantage for rear contact but no automatic drop. There is a possible post combat drop for the loser (in addition to the automatic drop if any) in the combat if it fails to pass its cohesion test.

Chris

Yep thats right Chris this is whats supposed to happen,but ive seen it happen with my own eyes and A1 did it to me aswell.Strated in front hex chased a skirmished off stopped pivoted and changed direction hit Cats in the rear and dropped 2 cohesion levels to Fragged.I will admit i havent seen it often but lately ive seen it 4 times,3 times in a recent game.

This needs to be sorted out, although this example looks accidental.

I myself have still not seen it and may well try a few more scenarios but if it is being used and has not been debugged, it has to stop.

Once more players using it will have to forfeit their games, that is will lose 3 vs 0. Not sure what to do with bps inflicted etc when this happens.

It had been covered in Season 9 and has now been covered quite a bit on all LOEG links.

If players have used it because they hadn't read the rules, "Season 9". They should own up and I will give them the benefit of the doubt so they can replay the game BUT after the numerous posts in various LOEG Season 9 - Communications ..... Players ares still intentionally using it, their game is forfeited, they lose 3 vs 0.

Please make this clear to all players whom you are playing, again as was pointed out in Season 9.

[ericdoman1]

The split move rear charge bug was fixed in the last update with the Scenario Pack release. See the on line help for what is required for a rear charge to cause an automatic cohesion drop. Basically the charging BG must start in a hex row behind the one the target is in. If you move to a rear hex but did not start in a row behind the target, you get the ++POA advantage for rear contact but no automatic drop. There is a possible post combat drop for the loser (in addition to the automatic drop if any) in the combat if it fails to pass its cohesion test.

Chris

Yep thats right Chris this is whats supposed to happen,but ive seen it happen with my own eyes and A1 did it to me aswell.Strated in front hex chased a skirmished off stopped pivoted and changed direction hit Cats in the rear and dropped 2 cohesion levels to Fragged.I will admit i havent seen it often but lately ive seen it 4 times,3 times in a recent game.

This needs to be sorted out, although this example looks accidental.

I myself have still not seen it and may well try a few more scenarios but if it is being used and has not been debugged, it has to stop.

Once more players using it will have to forfeit their games, that is will lose 3 vs 0. Not sure what to do with bps inflicted etc when this happens.

It had been covered in Season 9 and has now been covered quite a bit on all LOEG links.

If players have used it because they hadn't read the rules, "Season 9". They should own up and I will give them the benefit of the doubt so they can replay the game BUT after the numerous posts in various LOEG Season 9 - Communications ..... Players ares still intentionally using it, their game is forfeited, they lose 3 vs 0.

Please make this clear to all players whom you are playing, again as was pointed out in Season 9.

[epos]

DIV C

FREE COMP.(epos) 16/34 -vs- L.MED.SWEDISH(Porsenna) 40/34

thanks for the game !