01-14-2018, 01:10 AM | #11 |
Join Date: Jul 2014
Location: Pennsylvania
|
Re: BEACH Overlays/Hexes/Tiles
The new and updated QUAGMIRE (using OGRE Rules, no Stacking and Beaches with Swamp) and QUAGMIRE! (using GEV Rules with Stacking and Beaches with Swamp) have been republished over in the WorkShop on STEAM.
http://steamcommunity.com/sharedfile...?id=1268876514 Both Scenarios still retain the "bug" that allows GEVs to use Beach hexsides and not have to stop before entering Swamp. So, if you want to see how "Marsh" works in these Scenarios, head over and give them a playthrough. If you do, please report back here and let us know what you think.
__________________
"So I stood my ground...my only hope to die as I had always lived-fighting" John Carter of Mars Last edited by Tim Kauffman; 01-14-2018 at 01:14 AM. |
01-19-2018, 12:08 AM | #12 |
Join Date: Jul 2014
Location: Pennsylvania
|
Re: BEACH Overlays/Hexes/Tiles
...or could it work instead by saying that GEVs do not have to stop when entering or leaving Swamp? All other rules for Swamp still apply.
...or instead of Marsh hexsides and all that "fiddly" stuff, we could simply have a full hex size Marsh only which would allow GEVs to not have to stop before entering or leaving. This would only be one new Terrain Token, a lighter green and less dense Swamp looking Terrain hex. We could rephrase the official rule something to the affect that Swamp and Marsh are neither considered Water or Land. Thus GEVs moving from or into a Water hex that is either from or into a Swamp or Marsh hex does not affect there movement. All other rules still apply. It's late as I write this, so maybe this is too far out there. Apologies if so.
__________________
"So I stood my ground...my only hope to die as I had always lived-fighting" John Carter of Mars |
01-19-2018, 03:17 PM | #13 | |
Ogre Line Editor
Join Date: Sep 2006
Location: Plainfield, IL
|
Re: BEACH Overlays/Hexes/Tiles
Quote:
This also points out an interesting quirk. The rules for water stopping movement is the only place where the behavior of the terrain you are _in_ dictates what happens when you try to leave. Changing 5.08.2 really put some wrinkles in a lot of places.
__________________
GranitePenguin Ogre Line Editor |
|
01-21-2018, 03:50 AM | #14 | |
Join Date: Jul 2014
Location: Pennsylvania
|
Re: BEACH Overlays/Hexes/Tiles
Quote:
Exception: Marsh is the same as Beach for transitioning purposes and considered to be a six-sided Beach hex. Otherwise Marsh is the same as Swamp. Thus, GEVs may move into Marsh without stopping before entering, but otherwise are then considered to be in Swamp. ...it's late again...lol
__________________
"So I stood my ground...my only hope to die as I had always lived-fighting" John Carter of Mars Last edited by Tim Kauffman; 01-21-2018 at 04:14 AM. |
|
01-26-2018, 01:03 AM | #15 |
Join Date: Jan 2018
|
Re: BEACH Overlays/Hexes/Tiles
The iteration above has the value of simplicity, which is what one wants in Ogre, but I think I can go it one better:
Marsh is a form of Swamp. GEVs do not have to stop before entering a Marsh hex, or when moving from a Marsh or Swamp hex to an adjacent Marsh or Swamp hex. If a road or railroad passes through the Marsh hex, a GEV may gain the road bonus in the same manner as a road/RR in a Beach hex. For all other purposes, treat Marsh as Swamp. This has the added advantage of flexibility: for instance, all or some printed swamp hexes could be declared to be marsh in a particular scenario, without needing overlays. Phil Last edited by Broadway Phil; 01-26-2018 at 01:19 AM. |
01-26-2018, 02:03 AM | #16 |
Join Date: May 2007
|
Re: BEACH Overlays/Hexes/Tiles
I can dig that wording.
|
01-26-2018, 03:02 PM | #17 |
Join Date: Feb 2016
Location: Lancaster, PA
|
Re: BEACH Overlays/Hexes/Tiles
I love where he's going with it, but have a concern about unintended consequences...namely that as written it seems to overrule the existing "Must stop if there's a Disabled By Terrain roll" for not just Marshes, but destination Swamps as well...but only if coming from a Marsh or Swamp.
Or to put it another way...the way it's worded: Clear -> Marsh: Must stop. Clear -> Swamp: Must stop. Marsh -> Swamp: May continue onward if not disabled by terrain. Swamp -> Marsh: May continue onward if not disabled by terrain. Would we better off with this, instead? Marsh is a form of Swamp. A GEV entering a Marsh is not subject to the "Units which enter terrain that may disable them must stop" rule. When a Marsh borders a Water hex, GEVs treat the bordering hexsides as Beach Hexsides.
__________________
Andy Mull MIB Agent #0460 Ogre 134th Battalion Lancaster, PA Imgur: https://agent0460.imgur.com/ |
01-26-2018, 09:45 PM | #18 | |||
Join Date: Jul 2014
Location: Pennsylvania
|
Re: BEACH Overlays/Hexes/Tiles
Quote:
Quote:
Quote:
Marsh is considered a six hex-sided Beach hex for GEV transitioning with the exception no matter what terrain hex it is next to a GEV moving from those hexes into the Marsh hex or moving from the Marsh hex to those hexes does not have to stop before entering unless it fails it's disable roll if one is required. A Marsh is always a full-size hex. It is not actually beach anywhere in it's hex, but rather the transitional meeting line that acts as beach between both hex-sides of the Marsh and any other terrain. Thus, a GEV moving from: Marsh}Marsh, Marsh}Swamp, Swamp}Marsh, Marsh}Clear, Clear}Marsh, Marsh}Forest, Forest}Marsh, Marsh}Town, Town}Marsh, Marsh}Rubble, Rubble}Marsh does not have to stop before entering unless it fails it's disable roll. A Marsh is the same no matter what the adjacent hex terrain is. Water, Marsh and Swamp can be assumed to be on the same water level. All other terrain can be assumed to be compatible with Marsh in the sense a transitional level is created between the two hex-sides that are on the same level. In other words, Marsh next to other terrain morphs that terrain to be compatible and on the same level as the Marsh creating that even transition between the two. I'm trying to keep this as KISS as possible.
__________________
"So I stood my ground...my only hope to die as I had always lived-fighting" John Carter of Mars Last edited by Tim Kauffman; 01-26-2018 at 09:56 PM. |
|||
01-27-2018, 02:21 AM | #19 |
Join Date: Jan 2018
|
Re: BEACH Overlays/Hexes/Tiles
I knew not having the rules in front of me was a mistake. Of course "if not disabled by terrain" should be added. But I would be confused by the references to beach hexes, and avoided them as much as possible. I thought the whole idea of marsh was to provide a transition from clear terrain (etc.) to swamp in the same manner as beaches do from clear terrain (etc.) to water.
Phil |
01-27-2018, 07:55 AM | #20 |
Ogre Line Editor
Join Date: Sep 2006
Location: Plainfield, IL
|
Re: BEACH Overlays/Hexes/Tiles
Absolutely. If you are going down this road, you do not want to reference other terrain types to explain the terrain you are discussing (i.e., discussions of what a marsh does should not include any reference to beaches).
If you can't clearly define the terrain on its own merits, you are either doing it wrong or it's a good indicator it shouldn't exist.
__________________
GranitePenguin Ogre Line Editor |
Thread Tools | |
Display Modes | |
|
|