Jump to content

AM/MT: The Core Guard


Recommended Posts

The very foundation of the defense of the Imperium.  The only wall against the tides of xenos, heretic and corrupted, mutated spawn.  The one and only bastion of defense, upon which all other aspects of the Imperium's defenses rally around, rely on, and must assist to stand a chance against the foe, every day, week and year in the coming times.  These are the Astra Militarum; these, are the Regiments of the Imperial Guard.

 

Of these Regiments, I have a current conundrum: how to represent my vision of The Core Guard, or, in OOC terms, the USMC surviving into the WH40k setting, at least in some version thereof.

 

I think using Militarum Tempestus Regiments will save me a great deal of headache; however, the issue is, in the Only War RPG, there's a Regiment Building system that allows one to make a custom Regiment, as well as variant pattern weapons that can be generated.

 

My issue is how to best represent the force I intend to build in time.  This muster will not occur that soon, however, I do plan on getting the ideas fleshed out; after some discussion with someone here, I feel it wise to discuss this matter further here, and I hereby request feedback and constructive critiques as to how to proceed.

 

The nitty gritty:

 

- Variant pattern Lasgun (M6 for now): 1d10+3 Energy, Pen 0, Clip 60, Accurate, Reliable, (One weapon trait free), Variable Weapon Setting, Custom weapon option: Extended Barrel (adds to range, and adds 50% to weight)

- Normal pattern Lasgun (M36): 1d10+3 Energy, Pen 0, Clip 60, Reliable, Variable Weapon Setting

 

Accurate means that at three and five degrees of success (ten percentage points rolled below one's Ballistic Skill), the weapon adds another 1d10 to the damage roll, to a total of 2d10 added; neither die added can Righteous Fury, which generates a Critical Damage hit on the target.

 

I really love this weapon, which is costed in the Only War rules as a Special Weapon to make it more play balanced, overall.  The problem is, using the weapon drives the cost of turning my idea into a very points heavy Regiment.

 

Representing this weapon in the WH40K rules for table top is the hangup for me figuring out how to proceed from here.

 

The range is that of a longlas, the pen I don't know yet, and the weapon quality Accurate might just need to be Poisoned 2+, or, treat all BS to hit rolls of BS -2 from skill as some special rule that gets brought in since a better shot is being made.  This however might needlessly slow down the game, and working this shot as a longlas on single shot seems like it would needlessly anger opponents.  Eight shots per squad being treated as a chance for pinning?  I'd pretty well say that does not sound fun, at least on initial reaction.

 

Veteran Squads are not a part of the standard Infantry Platoon, I get that.  However, my idea is this: using the Infantry Platoon, add +1 BS, and adjust the points to compensate for this.  The further cost of the replacement Lasgun has not been factored in yet.

 

Thoughts?  Sorry for the long read, thank you for hopefully making it this far.

Link to comment
https://bolterandchainsword.com/topic/289621-ammt-the-core-guard/
Share on other sites

I don't think the RPG rules translate well to 40k at all, you're probably better off treating them as normal Lasguns. For better accuracy take Veterans - it's best to see how the current rules and units can work with what you want rather than getting caught up tweaking things.

 

It's a lot easier to get games saying "I'm using the Guard codex" rather than "I'm using my own custom rules" too.

You had me confused. 

 

 The only advice I could give would be to pick USMC "units" that you like. and match codex units to those roles. Example I was in the Army. The 101'st airborne division (air assault).  If that was what I was trying to recreate through the AM. I'd look at which bregades did what. #rd brigade are an infantry brigade so that might be my infantry platoons. The 159th is aviation so their might be my Valkyries. Just as examples. I don't know any units in the USMC. 

 If it were me, that's how I would do it.

Good luck.

To say it, Line/Siege Infantry; the fighting force of the Marines, the standard infantry trooper.

 

Also, thanks for the feedback.  I am guessing to go MT rules once I get them, and the overall design from there might change.

 

It just seems like the headache of trying to translate this weapon is not worth the time it might take to figure it out.  As it is, I would at least like to try and get an idea of how to design it for tabletop; the problem appears to be that it is not a feasible translation.

 

Thanks,

Karack.

Black stone are you a Marine? What exactly are you wanting to accomplish? The Marine Corps is varied and has a lot of different unit organization. I might be able to help out if I know exactly what your wanting.

 

No, I did not make it through boot.  I was willing to go try, I just did not make it.

 

If that's a problem, I'm too old now to serve, and I guess this is more a respect for those that serve and defend the rest of us from threats both near and far.

 

I guess I am looking for a weapon that would serve the needs of the standard line infantry version of the wh40K version of the USMC infantry fighting force.  I'm thinking a MEU(SOC) pattern style force, just a normal force as far as others are concerned.  I know MEU(SOC) is pretty open ended, so the standard infantry trooper I was thinking of is a highly trained, skilled, and potent warfighter.

 

0311 if that helps is what I would think is the core of the infantry Regiment I'm planning on one day making into a fighting force.  There's just going to be plenty of other toys present as far as the overall fielded fighting force goes, thus the MEU(SOC) as mentioned above.

 

Hope this helps, Ulrock.

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.