BAR Issue #1

[JoeGuardsman]

Hive Tyrants can not be targeted in close combat while accompanied by Tyrant Guard.

[JoeGuardsman]

I will be a Prosecutor on this issue. The matter of the exact wording the "Shield Wall" rule mean nothing in this case. Tyrant Guard were obviously a late entry into Codex: Tyranids as you can tell by their very small entry. This small entry is the cause for the ShieldWall rule being only one poorly written sentence. If any sense of continuity is to be kept in the rules a simple rule of prescendence should be stated. Tyrant Guard are a retinue and a Hive Tyrant is a monsterous creature, that being said Tyrant Guard should not be treated any differently from other armie's retinues that do not protect their character in close combat and Hive Tyrants should not have their independent unit status in close combat removed as it is a monsterous creature.

[Dan296]

i will be a defender on this issue.
tyrant guard were not 'late entries' into the codex, as they were in the 3rd version codex. i understand why they put this rule in this codex, as it was not in the last one. in the last codex, they were billed the bodyguard, but this was very vague and they were a useless unit, as they conferred no real protection for the tyrant and you could still focus all of your big gribblie killling firepower on the tyrant. this rule gets rid of the vague language. you cant target it in close combat, no if, ands, or powerfists to the face.
speaking of which, fluff wise this rule also makes sense. the hive mind wants to protect its swarm leaders. if you have are assaulting the tyrant, the guards sole job is to protect him. the seargent with the powerfist throws a punch at the tyrant, the guard jumps in front of it and takes the blow. he cant protect against range attacks because he is to slow to stop a lascannon traveling at X mph.

rebuttal?