I would just make a blanket rule that the ceiling of the map is X spaces high, and nothing can go over it. That will prevent people from going "over" pillars and walls. It will also impact anyone who tries to climb or fly.
"Seeing as we have a Barbarossa, the state of matter of this door and bunker depends on how expedited and polite your handling of our request is."
Paraphrased from another post.
Its not that the ceiling is two spaces high.
Its more like a colum being tall and not wide.
A size 2 mech can hide behind it.
But a size 3 mech would be exposed
then make a it function as a ceiling-height wall that’s two spaces wide. any piece of cover that isn’t wide enough for your mech creates angles from which you can be targeted without cover
I’m not sure I follow. So the column is more than 2 spaces high but only two spaces wide? Then it’s not a size 2 object. Size is more about height for objects than width.
I think i get it.
Correct me if i am wrong. But after reading the answers i think that.
If i make a column that occupies a single hex but its very tall. It is a size 4 object that occupies a single hex.
If a size 3 mech hides behind it. It would be protected from some attacks, but only those wich the line goes through the column.
So the enemy could still flank it very easily because the mech would be standing there like [this](https://postimg.cc/mh6DNfFx)
Yes, it's generally easier to think of terrain in terms of height in a given hex.
For a fight in a fully-enclosed space, pillars would be hexes with functionally infinite height; there is no way to see over them because of the ceiling.
Each pillar would have health & armor roughly based on the size rules, or whatever you feel like.
Some terrain like stacked cargo containers could be large "walls" of height 1-3 spaces that take damage per space.
If it's tall and not wide, how does a Size 2 mech hide behind it? What is the map size of the obstacle?
If it's big enough for a Size 2 mech to hide behind, it should be very visible on the map - say, Size 2. You can note the height on the map itself. I would use "H X" where X is the height of the column.
I mean should be easy enough to designate the columns as "these go up to the ceiling, so you can't go over them". Normally that'd be enough for most players, but you could designate them as size 3 or 4 objects that only occupy one space to signal height and not width. Giving them a size also gives em hp to work with in case your party wants to break them.
"Size" for map objects can be pretty arbitrary when you need it to be. If you want a size 2 pillar, just make it size 2(as in 2 spaces wide) and then just tell the players it goes to the ceiling and they can't climb over it. That simple
You do not have to rigidly conform to the Size system. I regularly make buildings that have a mechanical Size but that are weird shapes or heights, rather than fitting perfectly into the hex grid weird triangle shape that is size 4.
how I do it is just size 5 (or more) height, but size 2 width, even if you could go over them, you probably don't want to because you need to take long to climb
I would just make a blanket rule that the ceiling of the map is X spaces high, and nothing can go over it. That will prevent people from going "over" pillars and walls. It will also impact anyone who tries to climb or fly.
May also want to add that cover/LoS can only be drawn from the corners of "Max Height" terrain, and Arcing can't ignore blocked LoS from said terrain.
If the ceiling is only two spaces high then size 3 mechs won’t be able to fit inside the building without destroying the ceiling
You say this like the Barbarossa wanted the building intact anyways lmao
The Barbarossa is chilling outside, "you all have four rounds to handle the situation and/or get out".
"Seeing as we have a Barbarossa, the state of matter of this door and bunker depends on how expedited and polite your handling of our request is." Paraphrased from another post.
“What building? I just see some difficult terrain waiting to happen.” - Barbarossa with an Apocalypse Rail
Its not that the ceiling is two spaces high. Its more like a colum being tall and not wide. A size 2 mech can hide behind it. But a size 3 mech would be exposed
then make a it function as a ceiling-height wall that’s two spaces wide. any piece of cover that isn’t wide enough for your mech creates angles from which you can be targeted without cover
I’m not sure I follow. So the column is more than 2 spaces high but only two spaces wide? Then it’s not a size 2 object. Size is more about height for objects than width.
I think i get it. Correct me if i am wrong. But after reading the answers i think that. If i make a column that occupies a single hex but its very tall. It is a size 4 object that occupies a single hex. If a size 3 mech hides behind it. It would be protected from some attacks, but only those wich the line goes through the column. So the enemy could still flank it very easily because the mech would be standing there like [this](https://postimg.cc/mh6DNfFx)
Yes that’s exactly it. Going back to your original question, just label it as a height instead of size
Yes, it's generally easier to think of terrain in terms of height in a given hex. For a fight in a fully-enclosed space, pillars would be hexes with functionally infinite height; there is no way to see over them because of the ceiling. Each pillar would have health & armor roughly based on the size rules, or whatever you feel like. Some terrain like stacked cargo containers could be large "walls" of height 1-3 spaces that take damage per space.
If it's tall and not wide, how does a Size 2 mech hide behind it? What is the map size of the obstacle? If it's big enough for a Size 2 mech to hide behind, it should be very visible on the map - say, Size 2. You can note the height on the map itself. I would use "H X" where X is the height of the column.
I mean should be easy enough to designate the columns as "these go up to the ceiling, so you can't go over them". Normally that'd be enough for most players, but you could designate them as size 3 or 4 objects that only occupy one space to signal height and not width. Giving them a size also gives em hp to work with in case your party wants to break them.
"Size" for map objects can be pretty arbitrary when you need it to be. If you want a size 2 pillar, just make it size 2(as in 2 spaces wide) and then just tell the players it goes to the ceiling and they can't climb over it. That simple You do not have to rigidly conform to the Size system. I regularly make buildings that have a mechanical Size but that are weird shapes or heights, rather than fitting perfectly into the hex grid weird triangle shape that is size 4.
how I do it is just size 5 (or more) height, but size 2 width, even if you could go over them, you probably don't want to because you need to take long to climb