Profile of trigg

Update: I tried the sight-block-only object per the instructions below, and it doesn't project the undesired impassibility onto the terrain above the blocks. I played a game and didn't notice any abuse, but I'll need to play several more to be sure.

A few units were still just barely clipping the corner of the hilltops with their shots, so that may mean that I sank the blocks too deep. (Or maybe they had a spotter, so the sight blocks were irrelevant.)

I'll do some more experimenting and then update the instructions if I think it's working OK.

This didn't work - it projects impassibility to the terrain above the blocks.

I'll leave this post for now, in case someone figures out a workaround.

Easier said than done...

I haven't tried it in a game yet, but here's the easiest way I can figure out to do it in the worldbuilder:

• Set the overlay to the 5m grid, to help you see the curvature of the landscape better.
  
• Create an object spline:
  
  • Start by using a wall such as concrete_l_04. This is important because the thin wall sections make it easier to see where to align the spine with the terrain.
    
  • Set it to wall mode / adjustable to terrain.
    
  • Unless the ground is perfectly level, set the spacing to -0.75/-0.75. The resulting overlap will make the stairsteps between the sections smaller.
    
  • Line it up with the crest or edge of the hilltop until you're satisfied.
    
  • Now switch the spine to ebps->gameplay->designer_objects->objects->6x12_sight_shot_blocking_uncrushable instead of the wall.
    
    • In addition to having the desired properties, this one is really nice because it shades the whole volume blue, making it easy to see it when you sink it in the ground later.
      
    • The wide blocks won't match the terrain as well as the fence did, but unless you're just placing a few blocks you're only sacrificing a little accuracy to avoid a whole lot of headache.
      
  • Uncheck wall mode and click Apply Changes.
    
  • Now click Bake (at top of the right panel) to convert it from a spline to objects.
    
  • Leave it as it is for now.
    
• Do the above for the whole map.
  
• When they're all laid out, use Scenario->Blueprint List to select all instances of the sight/shot blocker.
  
• Put your camera where you have a good view of some of them, an sink them into the ground by holding 'h' and mb-1 while pulling down with the mouse. Sink them until they just barely disappear under the terrain.
  
  • Notice that since they are all selected, you will be lowering them all by the same amount. You will again be trading a little precision for a whole lot of convenience.
    

If you're a perfectionist (and what map maker isn't?) you can sink one spline at a time until most of it disappears but a few corners stick out, then select individual blocks to sink further if you think their exposed corners will be a problem.

OTOH, if your terrain elevation isn't extremely convoluted, just sink things until all the corners disappear, and the blocks should be pretty close to where you want them. If one block is a bit too low it just means there will be a LOS a little further back on the hilltop, but probably not enough for anyone to tell the difference during a game.

Hopefully this will save a lot of annoying behavior in the game.

Does the blocking effect apply to the whole volume of the rectangular frame you get when you select the block, or just to the vertical plane where the word BLOCK appears?

edit: outdated post, broken links

This is a faked single-player map. You just launch it as a custom MP map, and select yourself vs two AI opponents. In this case, you play Germans against 2 x Soviets. Your goal is to defend your sector of a front line until you win on victory points, about an hour of game time if you play for 1000 VP.


The map+script provide minor variations in the initial map configuration, some initial units for a screening force, randomized (and changing) weather, randomized/context-dependent reinforcements, AI air and artillery strikes, and a little bit of "offmap theater" on your flanks.

The randomness should make the experience somewhat different every time you play.

Your initial forces and the reinforcements provide a variety of troop types that you cannot get with any single choice of commander.

The map is pretty simple, but may include a few things you find interesting if you look closely. However, most of the work has gone into the scripting. Due to the large combination of random and circumstantial events I probably haven't executed every line of the script in context, so if you try it please use -dev and give me a line number if scar bombs off.

If you extract it and look at the script, there is a huge amount of commented-out cruft showing things I tried that either worked or didn't. (Also, I was learning scar as I went, so hopefully my next map will have a much cleaner implementation.)

There is a companion summer map, identical except for the weather.

map at Steam workshop


edit: removed outdated material