Tactical Command
http://www.tacticalwargames.net/taccmd/

Ropecon 2009 report
http://www.tacticalwargames.net/taccmd/viewtopic.php?f=84&t=16318
Page 1 of 10

Author:  BlackLegion [ Sun Aug 02, 2009 9:12 pm ]
Post subject:  Ropecon 2009 report

silver towers(sheesh? 4+ invulnerable save? What's wrong with 4+ RA + reqular invulnerable? Effectively
Hmm Silver Towers HAVE 4+ save with regular 6+ Invulnerable.

Whats with the problem with countercharge? You still move toward the closest enemy unit.




Author:  tneva82 [ Sun Aug 02, 2009 9:17 pm ]
Post subject:  Ropecon 2009 report

Quote: (BlackLegion @ 02 Aug. 2009, 21:12 )

silver towers(sheesh? 4+ invulnerable save? What's wrong with 4+ RA + reqular invulnerable? Effectively

Hmm Silver Towers HAVE 4+ save with regular 6+ Invulnerbale.
Huh? Did I misunderstand hena then when he said 4+ invulnerable? Maybe he meant it as 4+ AND invulnerable.

That would make more sense though then I should have aimed to get some shooting done at them  :evil: Thought of 4+ invulnerable save however made me less interested in firing at them when I thought they would dodge half the volcano cannon shots...

Ah well. Wouldn't have changed anything though.

Problem is: You move toward closest foe. One that is SUPPORTING assault. You can't firefight them since they aren't directly involved in assault(just supporting) so if you aren't in range of the unit that assaulted you then you are moving AWAY from them and toward unit you CANNOT firefight! So essentially the supporting unit denies me FF attacks against unit that attacked you when units that were outside FF range but could have moved into FF range with counter charge were forced to stand still or counter charge AWAY from unit that engaged them. Bloody hell! This was exploited by the first space marine opponent mercilessly when I had like ~6 troopers in range with rest having to go toward land speeders which they then couldn't shoot anyway...Or stand still...

My regimental HQ for example sure could have found use for the ~half a dozen FF attacks I missed. Maybe it wouldn't have changed anything but maybe I might have survived it afterall.




Author:  Man of kent [ Sun Aug 02, 2009 9:30 pm ]
Post subject:  Ropecon 2009 report

you know that you don't HAVE to countercharge don't you...

Hope that helps,
R>

Author:  tneva82 [ Sun Aug 02, 2009 9:45 pm ]
Post subject:  Ropecon 2009 report

Quote: (Man of kent @ 02 Aug. 2009, 21:30 )

you know that you don't HAVE to countercharge don't you...

Hope that helps,
R>

Yes but of course that means they still aren't in range...

So my choices are: Stand still or move away from the formation that engaged them. Without that stupid rule I could move toward unit that assaulted me and get INTO the range!

In essence that unit that came to my rear is a) giving supporting fire b) denying me FF attacks in totally illogical rule. What? My troops have to either stand still, unable to shoot anything, or move toward enemy and then not use FF attacks against them in ongoing assault since they didn't assault me but only provide supporting fire? WHAT logic that is?

That shouldn't have been too hard to fix so why the triple darned loop hole is still there is beyond me. That's just plain broken rule!

Very illogical, very gamey, very much broken. That thing needs to be fixed ASAP and doesn't even take much of an effort. Can anybody point to single GOOD thing that rule accomplishes?




Author:  Ginger [ Sun Aug 02, 2009 11:27 pm ]
Post subject:  Ropecon 2009 report

Supports and supporting fire can be misunderstood. The supports can only shoot at target uints in range and LoS of the attacking formation. So where the target formation is spread out, it is quite possible that the supports 'pin' part of the target formation, but cannot actually shoot.


A A A                       <------- 16cm ------>            S S  
 
A A A <----10cm ---> T T T T T T T T T T T < 5cm > S S

A A A                       < 5cm >                                S S


Here, only the first 4x Target units can countercharge the attackers, the remainders are closer to the Supports. However, the supports have no target because the 4x defenders that are in range to the attackers are 16cm from the supports.

While this may be considered somewhat 'gamey', the mechanic is there to prevent the even more gamey tactic of a huge support formation being used with a tiny attacking formation.

Unfortunately, the problem is caused by the principles underlying the assault mechanics which effectively requires combat between only two formations. Introducing supports etc causes situations that need various 'additional' rules to mitigate the effects. Basically to correct this you actually need to rewrite the entire assault process.




Author:  The_Real_Chris [ Mon Aug 03, 2009 6:14 am ]
Post subject:  Ropecon 2009 report

What you hate is actually a feature of the assault rules :)

You may be angry at it, but really you are the one that left that opportunity there, from having a poor flank, or too wide a deployment, or whatever.

Basically your army is surrounded and failing apart under pressure. Next time maintain your lines and mutual supporting formations to avoid it :)

Author:  tneva82 [ Mon Aug 03, 2009 8:57 am ]
Post subject:  Ropecon 2009 report

Quote: (Ginger @ 02 Aug. 2009, 23:27 )

Supports and supporting fire can be misunderstood. The supports can only shoot at target uints in range and LoS of the attacking formation. So where the target formation is spread out, it is quite possible that the supports 'pin' part of the target formation, but cannot actually shoot.


A A A                       <------- 16cm ------>            S S  
 
A A A <----10cm ---> T T T T T T T T T T T < 5cm > S S

A A A                       < 5cm >                                S S


Here, only the first 4x Target units can countercharge the attackers, the remainders are closer to the Supports. However, the supports have no target because the 4x defenders that are in range to the attackers are 16cm from the supports.

While this may be considered somewhat 'gamey', the mechanic is there to prevent the even more gamey tactic of a huge support formation being used with a tiny attacking formation.

Unfortunately, the problem is caused by the principles underlying the assault mechanics which effectively requires combat between only two formations. Introducing supports etc causes situations that need various 'additional' rules to mitigate the effects. Basically to correct this you actually need to rewrite the entire assault process.

But why leave supporting units 16cm away when you can have them IN range?

Now you can have huge supporting unit supporting tiny assault unit and prevent target formation from FF'ing with bunch of units they would be able to shoot without supporting unit. Gamey as hell and actually makes that huge support unit + token assault unit MORE powerfull because they can limit number of shots assault unit has to face while providing tons of FF attacks in support.

Author:  tneva82 [ Mon Aug 03, 2009 8:59 am ]
Post subject:  Ropecon 2009 report

Quote: (The_Real_Chris @ 03 Aug. 2009, 06:14 )

What you hate is actually a feature of the assault rules :)

You may be angry at it, but really you are the one that left that opportunity there, from having a poor flank, or too wide a deployment, or whatever.

Basically your army is surrounded and failing apart under pressure. Next time maintain your lines and mutual supporting formations to avoid it :)

There was no way I could have prevented that. That's totally illogical rule which has no basis whatsoever in reality. It's just abuse of rules without any logic whatsoever. That's the sort of stuff I except kids do in 40k. I didn't expect to face that in epic.

Ah well. Maybe it's time to throw all my epic models in garbage can.

Author:  The_Real_Chris [ Mon Aug 03, 2009 9:03 am ]
Post subject:  Ropecon 2009 report

Fix it with a house rule/rule for your tournaments that all counter charge moves are towards the engaging formation.

Personally I like it though :)

Author:  tneva82 [ Mon Aug 03, 2009 9:04 am ]
Post subject:  Ropecon 2009 report

Quote: (The_Real_Chris @ 03 Aug. 2009, 09:03 )

Fix it with a house rule/rule for your tournaments that all counter charge moves are towards the engaging formation.

Personally I like it though :)

You like gamey rules which have no logic behind them and which accomplishes nothign except making sure small token assaults are even more broken with pretty much nothing you can do to prevent them from annihilating entire formations in one go just like that?

Dunno. I would prefer rules that would make sure tactics and strategy decide the game. Not abusing rules.

Ah well. Guess it's time to throw epic armies to garbage bin. I hate games where such gamey broken rules subject to abuse exists so why bother with epic then.




Author:  The_Real_Chris [ Mon Aug 03, 2009 9:11 am ]
Post subject:  Ropecon 2009 report

So you think if you go to the trouble of surrounding an enemy formation you shouldn't be rewarded? Even if it means the units concerned can simply run away in the opposite direction while under the enemies guns.

I have no problems, realism or otherwise, with part of the enemy being fixed in place by demonstrating to its front while an elites formation hit it from the side and cause much trouble and heartache. How many real life examples would you like?

Personally after spending 22 years playing wargames of all eras I have no problem with such an effect in game. Certainly it would not be a cause for me to quit.

Author:  tneva82 [ Mon Aug 03, 2009 9:16 am ]
Post subject:  Ropecon 2009 report

Quote: (The_Real_Chris @ 03 Aug. 2009, 09:11 )

So you think if you go to the trouble of surrounding an enemy formation you shouldn't be rewarded? Even if it means the units concerned can simply run away in the opposite direction while under the enemies guns.

I have no problems, realism or otherwise, with part of the enemy being fixed in place by demonstrating to its front while an elites formation hit it from the side and cause much trouble and heartache. How many real life examples would you like?

Personally after spending 22 years playing wargames of all eras I have no problem with such an effect in game. Certainly it would not be a cause for me to quit.

Isn't tons of supporting fire with immunity to return fire(since they are supporting and not directly involved in assault) big enough reward already? Why make the token assault unit face even less shots to boot?

What's so fun about token clip assaults anyway they need to be beefed up to ridiculous level? They are already nearly impossible to defend if done by certain units so why make the situation even more ridiculous? Especially with totally illogical rule to boot.

Token clipping assaults are already pushing believability but this totally breaks it. "Hey there's units behind us! Let's move toward them! BUT DON'T SHOOT AT THEM! I know they are shooting at us but they aren't directly engaged with us so DON'T SHOOT THEM!". Why I doubt that order from unit leaders would make sense in real battle...

Author:  tneva82 [ Mon Aug 03, 2009 9:53 am ]
Post subject:  Ropecon 2009 report

Quote: (Hena @ 03 Aug. 2009, 09:47 )

Remember that they cannot give support fire unless they are in range of enemy that is involved in assault (eg. a unit that was allowed to fire in the assault).

That's hardly problem. Move to other side of formation, be 6-15cm from target units and engage from other side. Plenty of units in range but whole bunch unable to counter charge toward anything meaningful.

Bleh. Stupid rules. Ah well. Since tyranids aren't allowed I won't be playing any tournaments anyway and ergo no epic games for me anyway. So atleast I won't have to be bothered by this anyway. Does mean I have tons of useless miniatures but what the heck. If they get too much in way there's always the garbage bin option.

Page 1 of 10 All times are UTC [ DST ]
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/