Jump to content

Sanguinor and the Glaive Encarmine


Noctus Cornix

Recommended Posts

Good evening, brothers and sisters.

 

So I have a bit of a question for you guys. I've playing around with the idea of creating a Blood Angels Successor Chapter and unlike most, I'm a huge advocate of making DIY Special Characters using pre-existing character rules. Now, an idea that struck me was for this particular Chapter is to have the very Chapter Master having fallen to the Black Rage, but is this very strange and disturbing version of it, quiet and lax, almost utterly silent as he slaughters across the battlefield like an avatar of death. Any time he's not in battle, he's likely left in solitude in his tower or chained up in warp transit.

 

Now the idea is that, given the nature of the character and his purpose, I think he would make an excellent counts as for Sanguinor. That being said, I came across something I wanted opinions on. In the FAQ, the Glaive Encarmine has been registered as being able to be a sword or an axe and its up to the player to decide unless the listing states otherwise. Sanguinor is listed as having a Glaive Encarmine but no where have I seen it stating that it should be a sword. Now, rules of common sense would clearly dictate that if you are indeed using Sanguinor and his base model, you should use a sword, but what about if you converted an axe onto him?

 

Essentially what I'd like to know is this. IF I create a completely custom made counts as Sanguinor model fitted with a Glaive Encarmine Axe, by the rules, do you guys think that would be acceptable?

It's a sword because the model comes with a sword.

 

Unless you convert it to have an axe. It would still be RAW, as it would still be a Glaive Encarmine. Does the codex specify that it *has* to be a sword though? Personally for me, I'd be no worries, I can however see people being a bit prickly in a Tournament environment.

We had this discussion a while back and someone asked about it at Games Day. It's a sword because that's what he was designed with.

 

Similarly, Dante is armed with a Power Weapon in the rules, but he has to have an axe for the above reason.

Rules iffiness aside, why would you even want to give him an axe?

 

The Sanguinor is a lot like vampire counts in warhammer fantasy, killy but super fragile and best suited to mulching rank and file that can't fight back properly.

Don't be fooled by his duelist rules, the only place he'll ever do any good is going up against weak units with MEQ stats or worse.

Strike first so you can reduce the number of return attacks and only get hit on 5+ with an almost automatic sweep if you win. Rinse - repeat.

1. Because Axes are cool (its also sort of the weapon of choice for the Chapter)

 

2. Because I've done some play testing with him (both with a sword and an axe) and he just performed so much better for me with the Axe. He's tough as nails and I delighted in butchering my way though a Grey Knight Terminator squad like they were weeds. Every time I tried to put him up against any kind of MEQ unit, he'd just get mowed down by mass fire or softened up and then bogged by attacks and bodies. He performed much better, atleast for me, as an Elite Squad killer and HQ Hunter. 6 Str 7 attacks on the charge is nothing to snuff at.

 

3. Because Axes are cool

  Every time I tried to put him up against any kind of MEQ unit, he'd just get mowed down by mass fire or softened up and then bogged by attacks and bodies.  

 

Surivability is his big weakness, axe isn't going to change the fact he's as easy to kill as 3 terminators. Do you deploy him from a storm raven?

 

You seem to have an odd local meta if the sanguinor can survive going after HQs and elites.

He is very easy to wound but his 3++ and EW can make him surprisingly survivable.

 

Personally it's cool to give him an axe, but then it gets me thinking why not just take a better character from another chapter and have him counts as ragee BA. Asterion Moloch would be my choice as he's high S and AP2 but still hits at I6.

You could use astorath?

Really, I'm sure the worst that would ever happen is this

"So this is my counts as sanquinor, he has an axe"

" that's a cool model, but officially he's supposed to have a sword right?"

" cool, for this game my counts as sanquinor has a counts as sword, you dig?"

" cool"

This one is slightly different to me than Dante.  Dante's weapon is actually called an axe, which happens to be a power weapon, while the Sanguinor's weapon specifically has two separate profiles available to it.  I wouldn't have a problem with it, but like knife&fork said I wouldn't put an axe on him.  Also, what makes you believe that axes are the weapon of choice for the chapter?

looking at both the codex and the faq/errata I would think it would be fine to give him an axe if you wanted.  They addressed both Dante and Astorath's axes specifically which were power weapons turned into power axes.  The only edit to the glaive encarmine gives you the option to take them as either an axe or a sword.  The entry under The Sanguinor directs you to the entry under the Sanguinary Guard which is the one that has been updated.  Unless someone that has the digital codex can say otherwise I think you should be good to go.

We had this discussion a while back and someone asked about it at Games Day. It's a sword because that's what he was designed with.

 

Similarly, Dante is armed with a Power Weapon in the rules, but he has to have an axe for the above reason.

My Dante used to be armed with a sword (in fact I liked the look better with a sword and will likely go back to it).

 

The FAQ says its an axe, so its an axe that looks like  a sword.

 

I don't like to use the idea of what the model comes with.  Nothing in the rules says Mephiston has a sword or Sanguinor has a sword.  Model it as an axe and have fun.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.