Warhammer 40k Forum and Wargaming Forums banner

Different print runs of a Codex.

5508 Views 52 Replies 12 Participants Last post by  don_mondo
Just had a chat with TYRANIDS the Living Metal rule on the Monolith and it seems that we have different things printed in our Codex.
(I now know that his is the newer one.)

Tyranids wrote:

I was looking at the codex when I wrote it "any weapon attacking the Monolith will roll for armour penetration using its unaugmented strength and a single D6 no matter what"
My codex does not say this at all!

It is fairly common fo GW to edit a later print run of a Codex without saying they have which can cause some annoying and un-needed auguments and disscusions.

If you have spotted any of these list them here so that we can all save time and much angst.

EDIT Please Do not quote whole passages of your Codex as this is against the old Copyright laws
1 - 4 of 53 Posts
Yeah GW are really bad for this rubbish. They try to slip things in because they didn't play test things properly in the first place. God only knows how many changes they have made to the chao's codex! One of the re-incarnations even imply's that a Slaanesh model with a doom siren will alway hit on initative, regardless of the weapon used ie I5 powerfists!

MarzM :mrgreen:
Yeah ork tankbusta bombs don't work against Monoliths! I think orks have a really problem against them!

But then again, the ork player could just keep shooting rokkits and then just beat up the Necrons themself!

MarzM :mrgreen:
Thats true! My chao's codex is the origional, so it shows oblits at T 5. I really should buy the new one with all the updates, buy really. Why should i spend more of my money because again GW buggered up again, and then tried to paste over the top of it?

MarzM :mrgreen:
Swapping older wrong codex's!

Thats, sadly, about as likey as you walking into a GW on January the 1st and asking whats in the sale, and not being laughed at!

MarzM :mrgreen:
1 - 4 of 53 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.