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.

Hey I don't know is this is in the correct place and sorry is that's so... but my question is:

Can we use the imperial armour books from forge world as our codex for non apocalypse games?

I ask this as I like the idea of a Bigmek army (I know it can be done with out the IA book rules but its not the same) in the Raid on Kastorel book. also any tips or people that have play with or against it any tips or things you've notice about it. Just a general discussion on it

Yes if you have your opponents permission.
Some would argue that you need your opponents permission to battle him with a normal codex anyway.
Basically it's best to make sure he/she is okay with it first.

purplefood wrote:
Some would argue that you need your opponents permission to battle him with a normal codex anyway.

Honestly? People are really like that? If I run into someone like that, I am going to tell them they need my permission to play warhammer.

Lord Scythican wrote:

purplefood wrote:
Some would argue that you need your opponents permission to battle him with a normal codex anyway.

Honestly? People are really like that? If I run into someone like that, I am going to tell them they need my permission to play warhammer.

I don't think there are people like that but in the last discussion about this someone pointed out that in a normal game you also need your opponents permission which kinda makes specific permission for a FW book kinda pointless.

Yeh I always try make sure there okay with it.

Just wasn't sure how people feel about it, but if its a strong no then that answers my question but can't you say that about any codex then?

purplefood wrote:

Lord Scythican wrote:

purplefood wrote:
Some would argue that you need your opponents permission to battle him with a normal codex anyway.

Honestly? People are really like that? If I run into someone like that, I am going to tell them they need my permission to play warhammer.

I don't think there are people like that but in the last discussion about this someone pointed out that in a normal game you also need your opponents permission which kinda makes specific permission for a FW book kinda pointless.

Exactly.

The big "taboo" about FW lists is because nobody knows what things do as well as the Codices proper.

If you're going to run a FW list, it doesn't hurt to kind of have 'cheat sheets' that tell your opponent in the most vague terms what things can do, with page references in your book(which seriously--always have it on hand when playing with people who don't have the books themselves) for the detailed descriptions.

I play Elysians, also from the Kastorel book. Forge World lists tend to be, on averege, less powerful than their GW counterparts. Most people should't, or had better not, have a problem with it. The main thing about FW lists is they can somtimes add somthing to your army that isn't otherwise available in the game because FW lists are very fluffy. This usualy involves access to somthing that would otherwise be restricted- for you that's dreads and for me it's valks. Some people will view that(and in some instances rightly) as cheese. For example: My own list allows me to take Thunderbolts and Lightnings, which are flyers, in a normal game of 40k. It is fluffy and totaly realistic for Elysians to get air support. That being said I simply don't even try to take them in a normal game because flyers really shouldn't be in one.

use it if you have your opponents permission.

quite frankly, you and your opponent sign an unwritten contract to play each time you play 40k. regardless of weather you are using a GW codex or a FW IA book.

do you feel it's wrong for an opponent to say he wants to play, you whip out your super cheezy SW razorback spam list and your opponent packs up and leaves on account of your army? if he doesn't want to play space wolves, he has the choice to not do so and there is nothing to stop him from doing so.

now, if he walks away in the middle of the game, then he has violated the contract and you feel slighted. sadly, there are no repercussions from violating the contract aside from your opinion of him(which can be a stiff penelty)

the same applies to IA lists. it's just that most people have this preconcieved notion that FW is full of OP (it's mostly under powered with a few OP things thrown in)

Kanluwen wrote:

If you're going to run a FW list, it doesn't hurt to kind of have 'cheat sheets' that tell your opponent in the most vague terms what things can do, with page references in your book(which seriously--always have it on hand when playing with people who don't have the books themselves) for the detailed descriptions.

This. Whenever I use a FW list or unit, I not only bring the book, but also a print out copy of relevant rules and list for my opponent's use to reference. If they don't take a look before hand when I offer it, it's their fault for being surprised throughout the game from here on out. They are, of course, free to take a look throughout the game if they ask, too.

As strange as it might sound, there are those that don't want to play against Forgeworld lists. I have a friend who doesn't play against them yet, but he's new to the game, so it's understandable that he doesn't want to get mixed up in some strange rules that he won't see outside of fun play.

I am never opposed to FW rules, and do hope to start running my DK army as real DK soon as I can get my hands on more of them and actually finish it. Infantry heavy army.. thanks a lot FW, make me NEED to buy 50 dollar squads to build it!

Matt1785 wrote:As strange as it might sound, there are those that don't want to play against Forgeworld lists. I have a friend who doesn't play against them yet, but he's new to the game, so it's understandable that he doesn't want to get mixed up in some strange rules that he won't see outside of fun play.

I am never opposed to FW rules, and do hope to start running my DK army as real DK soon as I can get my hands on more of them and actually finish it. Infantry heavy army.. thanks a lot FW, make me NEED to buy 50 dollar squads to build it!

That's how Forge World gets you. They put out the best looking models in the history of 40k, then charge for them!

Thanks so has anyone played with or against anyone with this sort of army? Any tips or suggestions from you would be greatly appreciated.

I've never played the ork bigmek list. My only advise is to try and not be too spammy. That's one of the things people complain alot about and avoiding it will help people accept your list.

It's perfectly fine to use FW lists, haven't had anyone flat out refuse to play against my FW armies but there is a big misconception about FW lists being super overpowered, if anything unless if you are doing a theme army, the lists provided by the IA books are incredibly restrictive and underpowered.

Take the Elysian list from Kastorel Novem, sure you can take Valkyries for dedicated transports, but the command squads are much worse (you can only take one special weapon as opposed to four in the regular codex), they cost more in terms of points (and money if using the models) and lose all armoured support from tanks.

For Orks, i'd suggest using the Ork Codex and using unit entries such from IA8 on FW units (if you choose to field them). There are only a few units that you can't field in the Ork Codex that you can in the IA list (Cyborks and the Grot Scavenger mob comes to mind which are just regular grots with a big downside that they set themselves on fire). The Ork codex is versatile enough for you to easily field the Dread mob (in fact, the Ork codex dread mob is better since you don't have to take the 1+ Spanna Boyz mob).

However, if you are really dead set on taking something like three Mega Dreadz (which are massive fire magnets for what is essentially an ironclad dreadnought) and the corresponding amount of Meka-Dreadz, the IA list might be useful (for a total of 5 Mega-Dreadz, 3 from Heavy Support and 2 from HQ), but otherwise, if you want to just take 1 or 2, you can field them just as well in the Ork codex. (as long as your opponent doesn't mind, but after you let him/her read the rules, i'm sure they will let you field them as they are incredibly overpriced in points)

Snarky wrote:It's perfectly fine to use FW lists, haven't had anyone flat out refuse to play against my FW armies but there is a big misconception about FW lists being super overpowered, if anything unless if you are doing a theme army, the lists provided by the IA books are incredibly restrictive and underpowered.

Take the Elysian list from Kastorel Novem, sure you can take Valkyries for dedicated transports, but the command squads are much worse (you can only take one special weapon as opposed to four in the regular codex), they cost more in terms of points (and money if using the models) and lose all armoured support from tanks.

This. My squads can't take heavy weapons either.

I have played against the Big Mek list.

it's pretty nasty although somewhat gimmiky.


Megadreds are tough to kill and intimidating, but they really boiling down to a Deffdred with a bigger weapons and a 5+ invuln.

they never get cover either because of size.

Spanna boyz are overpriced and suffer from not being able to get PKs(I was told they couldn't get PKs. didn't think to look that up myself as they didn't do much)

I know there gimmiky but im kinda tired of playing horde armies... Orks and IG so im trying to find ways of making them smaller as i still like the races also orks are just fun and unpredictable