Forum adverts like this one are shown to any user who is not logged in. Join us by filling out a tiny 3 field form and you will get your own, free, dakka user account which gives a good range of benefits to you: No adverts like this in the forums anymore. Times and dates in your local timezone. Full tracking of what you have read so you can skip to your first unread post, easily see what has changed since you last logged in, and easily see what is new at a glance. Email notifications for threads you want to watch closely. Being a part of the oldest wargaming community on the net. If you are already a member then feel free to login now.

Page 97 of the old Ork codex helpfully pointed out that runt/squig upgrades could be represented either on the upgraded model or by a suitable runt/squig model placed beside the upgraded model - any such extra model was otherwise ignored for game purposes. Fine.

But I can find no equivalent wording in the new codex. Have I missed it, or have the game's WYSIWYG rules changed? E.g. if my ork has an ammo runt upgrade, does that upgrade still need to be represented either on the ork model or by an extra runt model, or are we back to "Oh, by the way, that guy there has an ammo runt"?

WYSIWYG isn’t in the rules though it’s a strong gaming convention for 99% of players, albeit usually just for main wargear. Upgrades not so essential, so just declaring an Ammo Runt is usually fine, so long as your opponent knows.

WYSIWYG isn't in the rules but these days Ammo Runts, Grot Oilers and Bomb Squigs aren't wargear - they're models in their own right and have a statline as well as abilities that they confer. As such they should really be represented by models or things could get confusing your you and your opponent. Not representing them with a model would be very similar to telling your opponent "this unit of Ork Boyz that has 29 models on the board is actually a unit of 30 Boyz, it also has a Boss Nob with a Power Klaw in but you can't see it".

Targeting Squigs on Flash Gitz Kaptins and Grot Crew for vehicles are still wargear however.

 JohnnyHell wrote:
WYSIWYG isn’t in the rules though it’s a strong gaming convention for 99% of players, albeit usually just for main wargear. Upgrades not so essential, so just declaring an Ammo Runt is usually fine, so long as your opponent knows.

So you are okay not presenting models with stats not being represented? Just saying "this unit has it"? Okay so I declare my unit has lascannon marine but not bother put him on the board yet use him then.

It's got rules how it interacts. You can pick it for casualty. Why it would NOT be put on table?

I presume you would also not have models for tank busta bombs then either?

For models that have stat-lines such as ammo runts or bomb squigs, you absolutely must have the model there, they can be taken as casualties, count for range and LOS etc.

For things like a Warbosse's Attack Squigs, which is wargear, it's not technically required to represent them.

tneva82 wrote:

 JohnnyHell wrote:
WYSIWYG isn’t in the rules though it’s a strong gaming convention for 99% of players, albeit usually just for main wargear. Upgrades not so essential, so just declaring an Ammo Runt is usually fine, so long as your opponent knows.

So you are okay not presenting models with stats not being represented? Just saying "this unit has it"? Okay so I declare my unit has lascannon marine but not bother put him on the board yet use him then.

It's got rules how it interacts. You can pick it for casualty. Why it would NOT be put on table?

I presume you would also not have models for tank busta bombs then either?

Ah my bad, simple error. No need to extrapolate it or be obtuse. If it has a stat line then yes, you need a model. The OP’s inference was things that don’t so if I made an error, my bad.

Have to put the model on the table with the unit.

Ah, so because e.g. an ammo runt has its own stat line, it can be targeted or assaulted (unlike in the old codex), and therefore it does need a separate model - yup, that makes sense for anything with a stat line.

However, e.g. a gitfinda squig doesn't have a stat line, and so doesn't have a separate model (although ideally should still be represented somehow, just like other wargear).

Thanks, all