The Ogre Stronghold

The first and largest home of the Ogre Kingdoms — preserved.

Filter by date range

Standalone from the search box above — this queries Pagefind directly and checks each result's date itself, since the packaged search widget can only match a single exact date, not a range.

Store AoS campaign

original thread ↗

I haven't played AoS at all yet and this campaign is imminent. To give it some balance the store manager has given us 5 War Scrolls with wound limits to make our warband.

1. Key word hero (10 wounds)
2. Cannot include a hero (16 wounds)
Last 3 have no restriction but are all limited to 12 wounds.

I have loads of Ironguts, a fair few bulls, gnoblars, MFC, a giant, Leadbelchers, Firebelly and a slaughtermaster/butcher but I don't really know where to start.

Any ideas?
Huh, where are you playing? I think that's the same rules they're using at my local GW.

Anyway, the best choice for your Hero slot is probably either a Tyrant or a Bruiser BSB, the Tyrant is nicely killy even if it's command ability won't be so useful with such small unit sizes, whereas the BSBs planted standard ability can help pile on the wounds. If you don't have either of those then you could try a Butcher of Firebelly; both do basically the same thing and I believe have the same stats. Boost units armour saves to mess with your opponents target priority, and as you get closer start sniping with Maw/Arcane Missile.

With 16 wounds your probably going to want a solid unit of 4 Bulls or Ironguts, or Maneaters if you want to be extra mean.

Then for the 12 slots you have choices; the Giant is real good and will force your opponent to deal with it fast, could couple well with MFC who can get across the board quickly. Leadbelchers are alright, but I think their short range in AoS makes them less effective compared to just standard Ogres as you only really get to shoot when they are already in combat.

Gnoblars really need to be in units of 30+ to work properly, so I wouldn't bother with those.
Cheers Halos, I'm in York.

The BSB was 1st on my list I've been working on since posting.

Something like this:

Bruiser BSB, Ironguts x4, MFC x2, giant (then probably 3 bulls or I might go with a Firebelly because of the buff magic, breath weapon in the shooting phase combo)

At least it's less time consuming than 8th lists  :P
I feel the Tyrant is a better call than the BSB in this game.  His ability is great.  Also, the Maw spell on the butcher is pretty vicious and can keep going as long as you roll well enough. Way better than the firebelly spell. 

I like the giant, but MFC are far less effective in this version of the game.
Cheers Halos, I'm in York.

The BSB was 1st on my list I've been working on since posting.

Something like this:

Bruiser BSB, Ironguts x4, MFC x2, giant (then probably 3 bulls or I might go with a Firebelly because of the buff magic, breath weapon in the shooting phase combo)

At least it's less time consuming than 8th lists  :P

I think that list looks alright. At least one wizard would be good. Firebelly performs well when he's near the enemy, his fire-cloak working best when close to multiple units. Butcher is a good for softening up defensive units or tough monsters/heroes.

Bear in mind that 10 measly gnoblars is sufficient to completely tarpit a unit when your general inspires them. Although 3 ogres could probably do the same. Maybe two mournfang could even better.

But my biggest advice would be to not chain yourself to a preset list. I think you'll do much better if you planned some variations and counter deploy smartly. If that is even aloud at this event.
Sounds like my gw (manc) id run a tyrant a block of iron guts for the 16, a unit of leadies a unit of bulls and if feeling nasty a stonehorn though an other unit of bulls or a butcher/firebelly would work for buffing.
If it ain't nailed down it's a snack if it is it's lunch
Continue this conversation on GitHub ↗

Opens a new GitHub Issue pre-filled with a link back here — sign in with GitHub to post. If someone already restarted this thread, please add to that issue instead of opening a second one.