johnpjones1775 wrote:not a discussion about the rule itself, but about people's interpretation of securing an objective.
this is a discussion i've in the community at large before, figured i'd bring it up here.
some interpret OBSEC as something that should be on elites, moving forward, securing an objective, etc. while some say that regular soldiers are the ones who actually secure an objective by actually holding the objective once the elite forces have moved on, etc.
here's a joke, that i find hits on this differing idea of what it might mean to secure an objective, and personally why i think the whole OBSEC rule as it is now is kinda silly.
https://www.reddit.com/r/Jokes/comments/81n73v/the_differences_between_the_branches_of_the_us/
ObSec shouldn't be based on Datasheet Section/Battlefield Role. It would be better to make it based on Keywords (Probably Infantry/Walkers/Monsters) with a few bespoke exceptions here and there (Not actual suggestions just thematic example/fluff of what COULD be: Grots are too cowardly/lazy and don't ObSec without an Ork/Runtherd. Servitors don't get ObSec without a Techpriest/Techmarine/etc. Instinctual Behavior requires in-range Synapse. And many of the ones that don't get it should get a different Objective Based rule that interacts/interrupts ObSec.
Something similar should be done with actions: Actions should be based on Keywords - (this would require adding keywords to non-
SM based on my example categories) Actions for CHARACTER, MONSTER/WALKER, LEADER (think Sergeant, etc and each faction should probably getting a freebie one in their min squad size), or SQUAD (which is given to an Infantry Unit of more than X starting size - this makes it so a
Tac Squad (INFANTRY + SQUAD) can perform an action you don't want an Apothecary (INFANTRY but NOT SQUAD), VEHICLE, CORE, what have you - to do. Mix and Match those enough, with a limited ability to recycle one or two Keywords only, and people are incentivized to still have diverse armies.
Obviously this would need to be playtested for balance, we'd have to add a few more keywords Like SQUAD, and NOT-CORE but that's the beauty of keywords, they can be very powerful if
GW would use them right.
So you might have:
At the start of the game, you roll up what each "objective" is with a story based name(this is shared: Both sides know its a Dataport, and it's a Dataport for both sides. Each side Generates their Action in private before the game. So you know what you need to do where AFTER you've made your list but BEFORE you start deploying.
Objective: Dataport Terminal
Then roll a
D6 for the Action:
1) Hack some Data with a CHARACTER
2) Guard the Access Point of the Dataport with a SQUAD
3) Use your LEADER to corrupt the Dataport.
4) Camoflage/Osbscure the Dataport with a WALKER/MONSTER
5) Bring New Data to the Dataport with a BIKER or FLY
6) Drop Off Repair Parts from your TRANSPORT/INFANTRY.
7) Prepare to tow the Dataport Console with your VEHICLE
Roll 1
D6, pick up or down and count up/down skipping up to 1 choice until you get your Action for this Objective. This way you can't pick objective/Actions ahead of time tailoring your list to your "chores", and you're encouraged to take a diverse army, AND no two games would play the same because you have different Actions/Objectives.