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.

 BLADERIKER wrote:
So simple enough question then as it pertains to this.

If I have a 30 model unit of Orc Boys, and I lose 10 to shooting what is my leadership value for the subsequent moral test?

The mob rule allows me to substitute the Boyz Ld value (Of 6) for the number of models in the unit (In this case 30) or which ever is higher.

If we presume that models count as part of a unit even after they suffer fatal wounds (and are removed from the table/playing field) then the Ld value should be 30 even if one boy remains.

However, if we presume that once a model suffers a fatal wound they are removed from the unit (Thus no longer part of it, but having come from it), then having 20 boy left out of 30 nets us a Ld value of 20 (as those Boyz lost to shooting no longer count s being "in" the unit).

Exactly. Charistoph has been wholly unable to present a valid argument that doesn't break all the Core Rules.


Automatically Appended Next Post:

 Charistoph wrote:

 BLADERIKER wrote:
So simple enough question then as it pertains to this.

If I have a 30 model unit of Orc Boys, and I lose 10 to shooting what is my leadership value for the subsequent moral test?

The mob rule allows me to substitute the Boyz Ld value (Of 6) for the number of models in the unit (In this case 30) or which ever is higher.

If we presume that models count as part of a unit even after they suffer fatal wounds (and are removed from the table/playing field) then the Ld value should be 30 even if one boy remains.

However, if we presume that once a model suffers a fatal wound they are removed from the unit (Thus no longer part of it, but having come from it), then having 20 boy left out of 30 nets us a Ld value of 20 (as those Boyz lost to shooting no longer count s being "in" the unit).

The issue is where are we instructed to actually remove the model from the unit without relying on making up instructions?

Leadership rolls could be a case where it is relying on models in play as much as in the unit. We presumably cannot call on them for Leadership any more than we can call on them for Shooting or checking to see if they are Coherency.

Are we supposed to take your ad hoc rationale here seriously (highlighted in red)?

I think you have just proven to your thread that you are forced to resort to a dozen or so House Rules to fix the mountain of rules that your premise that 'slain models are in units' break.

Your argument is ridiculously invalid.

This leaves orknado and myself with the only valid rule supported argument.

col_impact wrote:

 Charistoph wrote:

One can return from many places. In order to return from outside the unit, one must be outside in the unit. Where is the instruction to remove the model from the unit? This is something that neither you nor orknado have addressed.

We don't need to address this. The Reanimation Protocols rule asserts with its very wording that the slain models 'must be outside in the unit' as you note. We have no choice but to follow the RAW on this, and take the Reanimation Protocols rule at its word. If you don't take the Reanimation Protocols rule at its word then you are violating plainly stated RAW.

Reanimation Protocols says absolutely nothing about a model being "out" or "in". As such, any consideration of the model being "out" is a fabrication in your own mind, and not an assertion of the rule. Any consideration of "out" would have to be written before Reanimation Protocols is stated. Without the actual written terms, you have no RAW.

col_impact wrote:

 Charistoph wrote:

In order for it to be "only models that are in units have datasheets and profiles", the quoted statement would have to have "only" in it. It does not. A connection to the datasheet and profile is established when you build the army list. An instruction must be provided to do so. Where is the instruction to separate the model from its datasheet and profile when it is removed from play?

Models only have permission to have datasheets/profiles while they are in units. You have to show a rule that permanently affixes a profile to a model in order to overcome the loss of the profile when the model no longer has permission to have the profile. Remember the rule says "each unit has a datasheet that lists the characteristics, wargear and abilities of the models in that unit". A model that is no longer in the unit, is no longer being 'listed' by the datasheet.

The burden of proof is on you here to provide a rule that affixes profiles to models such that the datasheet will list them when they are not in the unit.

I can demonstrate that the word "only" does not exist in the datasheet quote that orknado provided. Without that, there would need to be instruction to disconnect that connection between model and profile datasheet. I need no burden of proof to state that your opinion on this matter is made up. Any perusal of the Primer will find none of these instructions. You and orknado have a burden of proof that the model is removed from the unit, and having done so, loses all connection to its datasheet and profile. So, where is it besides your own heads?

col_impact wrote:

 Charistoph wrote:

Yes, it does say "returned to this unit", but where was the model in the first place? Where is the instruction telling you that the model was out and separated from the unit?

There are indeed other ways to construe this if we consider all the rules provided so far. We are instructed to remove the model from play, and then to return it to the unit. Where was the model? Out of play. In a way, there is a closer analogy that can be made to a hockey player being in the penalty box, then being a dead soldier in a ditty bag. The player (model) is removed from the play of the game, when he returns to the team, he is still on the same team (unit) in the same position within that team (unit). While the model is removed from play, it is still in the unit (organizationally), but removed from interactions involved with Movement, Shooting, Charging, Fighting, etc. This is not breaking the rules of the game, but using the instructions we have so far, in the order they are given, to put them in proper perspective.

Your own analogy proves my argument.

A player who is in the penalty box is still on the team so its not the same thing as what Reanimation Protocols rule is telling us.

The RP rule tells us that slain models are not in the unit. Unit is an organizational definition so slain models are not part of the unit organization.

While slain models are not part of the unit organization, datasheets will not list their characteristics as per the Datasheet rule.

The RP rule states nothing about the model not being in the unit. That is pure fabrication.

We have no instructions removing slain models from the unit organization. That is pure fabrication.

We have no instructions that state when models are no longer part of a unit, datasheets will no longer apply to them. That is pure fabrication.

Fabrication is fine for HYWPI, but not for RAW.

col_impact wrote:

 Charistoph wrote:
But you were attributing it to something else, the datasheet quote provided by orknado's list and you represented as your own which stated that models were in the unit, not the actual definition. The way you and orknado were presenting it was that it could never be modified. Well, it has been modified once to remove the model from play, where does it tell us to modify it back?

Yup. The profile is modified and when slain the slain model is no longer in the unit. When the slain model is not in the unit, the datasheet no longer lists the characteristics the model. That's the RAW.

Again, where do the rules tell us to modify the Wounds back?

Where does it tell us that the slain model is no longer in the unit?

Where does it state that a datasheet no longer lists the characteristics of a slain model?

Core Rules for the latter two, please.

col_impact wrote:

 Charistoph wrote:
Not entirely. In order for the model to be restored in pristine condition, we must consider the datasheet profile to be completely inviolate and unchanging. However, we do have instructions to modify the profile, which is what I was pointing out. I then stated that in order for them to be restored, it must be done in reverse order, in other words, with an instruction specifically detailing the number of Wounds being restored.

But sure, taking things out of context makes it easy to knock down strawmen.

So the profile is modified. The model is reduced to zero wounds and the slain models is no longer in the unit. When the model is not in the unit, the datasheet will no longer list the Wound characteristic. When the slain model is reanimated and the model is 'returned to this unit' then at that point the datasheet will list the Wound characteristic, which will be 3 in the case of a Destroyer model.

Where are the rules quotes to support the highlighted?

col_impact wrote:

 Charistoph wrote:
It asserts no such thing in and of itself. It would only be asserting this if we already had instructions for the model to be out, or if it said "return the model in to the unit". The rules do not operate in a vacuum, and we must be aware of previous instructions before making any assumptions on how to interpret the rules. This is a concept called "context". The only thing the model could be returning from is "out of play", since that is the only thing we have been literally instructed to do.

Nope. The Reanimation Protocols rule indeed asserts in and of itself that slain models are not in units when it indicates that reanimated slain models are 'returned to this unit'. It is logically impossible to construe another way without breaking the semantic logic of what the rule is saying. The RP rule is a rule in the book and so we have to adhere to what it is telling us.

Reanimation Protocols cannot assert that the model is out of the unit because it never states it. You and orknado are asserting it.

There is no semantic logic that connects to anything you are saying because it would require written phrases to process in semantics. And it is quite logically to logically construe other associations with it, as I demonstrated with the penalty box analogy. The hockey player is removed from the play of the game. A slain model is removed from the play of the game. Reanimation Protocols then returns the model to the unit for the play of the game.

col_impact wrote:

 Charistoph wrote:

col_impact wrote:
1) First, he must define 'play' as all Core Rules except rules that specifically target the 'removed from play' zone (e.g. Kill points, Reanimation Protocols) which is an entirely made up category on his part.

I have never stated that there was a "removed from play" zone. That is your manufacturing. However, 'play' must be defined as we are instructed to remove the model from play. When you 'play' with a model, you are moving it, shooting with it (hopefully), Charging with it (maybe), and fighting with it (maybe). When it is removed from play, you are not moving it, shooting with it, Charging with it, or fighting with it, no matter how much you would like to complicate this concept.

You are making up this definition of 'play'. There is no such definition in the rules. So once again it is an example of a house rule that you must invent in order to fix the rules that you radically break with your premise that 'slain models are in units'. This is one of the reasons why your premise is invalid.

I never stated this was a definition. I was stating that is what people do with the model when it is in play, and what people don't do with it when it has been removed from play.

Can you provide any actual core rules which actually state we do otherwise?


Automatically Appended Next Post:

col_impact wrote:
Exactly. Charistoph has been wholly unable to present a valid argument that doesn't break all the Core Rules.

Just because you don't like it, doesn't mean it hasn't been done. There is a difference. The main differences is that I acknowledge that most of this indication of 'play' is how players play it, not written statements.

col_impact wrote:

charistoph wrote:The issue is where are we instructed to actually remove the model from the unit without relying on making up instructions?

Leadership rolls could be a case where it is relying on models in play as much as in the unit. We presumably cannot call on them for Leadership any more than we can call on them for Shooting or checking to see if they are Coherency.

Are we supposed to take your ad hoc rationale here seriously (highlighted in red)?

Are we supposed to take your statements of RAW seriously when you add words to the rules?

You still have yet to properly answer the questions provided, nor answer the challenges requested to demonstrate the RAW validity of your and orknado's stance:
* Quote Reanimation Protocols and highlight where it states "out", "not in", "Wound", or "datasheet".
* Quote the core rule that states a model is removed from the unit.
* Quote the datasheet rule that states only models within a unit have access to the datasheet and highlight the word "only".

Tenet #1, You say it is written, prove it.

 Charistoph wrote:

col_impact wrote:

 Charistoph wrote:

One can return from many places. In order to return from outside the unit, one must be outside in the unit. Where is the instruction to remove the model from the unit? This is something that neither you nor orknado have addressed.

We don't need to address this. The Reanimation Protocols rule asserts with its very wording that the slain models 'must be outside in the unit' as you note. We have no choice but to follow the RAW on this, and take the Reanimation Protocols rule at its word. If you don't take the Reanimation Protocols rule at its word then you are violating plainly stated RAW.

Reanimation Protocols says absolutely nothing about a model being "out" or "in". As such, any consideration of the model being "out" is a fabrication in your own mind, and not an assertion of the rule. Any consideration of "out" would have to be written before Reanimation Protocols is stated. Without the actual written terms, you have no RAW.

Incorrect. The Reanimation Protocols rule asserts with its own wording that slain models are not IN units because slain models that are reanimated are 'returned to this unit'. 'Unit' is an organizational term in 8th edition, so slain models must not be part of the unit organization. There is absolutely no other way of construing it.

 Charistoph wrote:

col_impact wrote:

 Charistoph wrote:

In order for it to be "only models that are in units have datasheets and profiles", the quoted statement would have to have "only" in it. It does not. A connection to the datasheet and profile is established when you build the army list. An instruction must be provided to do so. Where is the instruction to separate the model from its datasheet and profile when it is removed from play?

Models only have permission to have datasheets/profiles while they are in units. You have to show a rule that permanently affixes a profile to a model in order to overcome the loss of the profile when the model no longer has permission to have the profile. Remember the rule says "each unit has a datasheet that lists the characteristics, wargear and abilities of the models in that unit". A model that is no longer in the unit, is no longer being 'listed' by the datasheet.

The burden of proof is on you here to provide a rule that affixes profiles to models such that the datasheet will list them when they are not in the unit.

I can demonstrate that the word "only" does not exist in the datasheet quote that orknado provided. Without that, there would need to be instruction to disconnect that connection between model and profile datasheet. I need no burden of proof to state that your opinion on this matter is made up. Any perusal of the Primer will find none of these instructions. You and orknado have a burden of proof that the model is removed from the unit, and having done so, loses all connection to its datasheet and profile. So, where is it besides your own heads?

Per the Datasheet rule, datasheets list the characteristics of models in the unit. When slain models are not in the unit, the datasheet will not list them. The rule directly supports my argument. The burden of proof is on you to show some rule that affixes the profile to the model since the datasheet does not list characteristics for models that are not in units.

 Charistoph wrote:

col_impact wrote:

 Charistoph wrote:

Yes, it does say "returned to this unit", but where was the model in the first place? Where is the instruction telling you that the model was out and separated from the unit?

There are indeed other ways to construe this if we consider all the rules provided so far. We are instructed to remove the model from play, and then to return it to the unit. Where was the model? Out of play. In a way, there is a closer analogy that can be made to a hockey player being in the penalty box, then being a dead soldier in a ditty bag. The player (model) is removed from the play of the game, when he returns to the team, he is still on the same team (unit) in the same position within that team (unit). While the model is removed from play, it is still in the unit (organizationally), but removed from interactions involved with Movement, Shooting, Charging, Fighting, etc. This is not breaking the rules of the game, but using the instructions we have so far, in the order they are given, to put them in proper perspective.

Your own analogy proves my argument.

A player who is in the penalty box is still on the team so its not the same thing as what Reanimation Protocols rule is telling us.

The RP rule tells us that slain models are not in the unit. Unit is an organizational definition so slain models are not part of the unit organization.

While slain models are not part of the unit organization, datasheets will not list their characteristics as per the Datasheet rule.

The RP rule states nothing about the model not being in the unit. That is pure fabrication.

We have no instructions removing slain models from the unit organization. That is pure fabrication.

We have no instructions that state when models are no longer part of a unit, datasheets will no longer apply to them. That is pure fabrication.

Fabrication is fine for HYWPI, but not for RAW.

Nope. Not fabrication at all. By its very wording, the Reanimation Protocols rule indicates that slain models that are reanimated are 'returned to this unit'. This can only mean that prior to reanimation they were not IN the unit. The rules directly support my argument.

Further, the Datasheet rule directly states it lists the characteristics for models in the unit. When a model is slain and not in the unit, the datasheet will not list its characteristics. The rules directly support our argument.

 Charistoph wrote:

col_impact wrote:

 Charistoph wrote:
But you were attributing it to something else, the datasheet quote provided by orknado's list and you represented as your own which stated that models were in the unit, not the actual definition. The way you and orknado were presenting it was that it could never be modified. Well, it has been modified once to remove the model from play, where does it tell us to modify it back?

Yup. The profile is modified and when slain the slain model is no longer in the unit. When the slain model is not in the unit, the datasheet no longer lists the characteristics the model. That's the RAW.

Again, where do the rules tell us to modify the Wounds back?

Where does it tell us that the slain model is no longer in the unit?

Where does it state that a datasheet no longer lists the characteristics of a slain model?

Core Rules for the latter two, please.

The Reanimation Protocols rule indicates by its wording that without a doubt slain models are not in units. Slain models that are reanimated are 'returned to this unit' which means that prior they were not in the unit.
The Datasheet rule lists the characteristics for models that are in units. The RP rule tells us slain models are not in units. Both of these rules combined directly indicate that datasheets do not list the characteristics of slain models.
I am not required to support my argument with Core Rules. The Necron index has rules of equal authority in this argument. Don't task me with requirements I do not have.

 Charistoph wrote:

col_impact wrote:

 Charistoph wrote:
It asserts no such thing in and of itself. It would only be asserting this if we already had instructions for the model to be out, or if it said "return the model in to the unit". The rules do not operate in a vacuum, and we must be aware of previous instructions before making any assumptions on how to interpret the rules. This is a concept called "context". The only thing the model could be returning from is "out of play", since that is the only thing we have been literally instructed to do.

Nope. The Reanimation Protocols rule indeed asserts in and of itself that slain models are not in units when it indicates that reanimated slain models are 'returned to this unit'. It is logically impossible to construe another way without breaking the semantic logic of what the rule is saying. The RP rule is a rule in the book and so we have to adhere to what it is telling us.

Reanimation Protocols cannot assert that the model is out of the unit because it never states it. You and orknado are asserting it.

There is no semantic logic that connects to anything you are saying because it would require written phrases to process in semantics. And it is quite logically to logically construe other associations with it, as I demonstrated with the penalty box analogy. The hockey player is removed from the play of the game. A slain model is removed from the play of the game. Reanimation Protocols then returns the model to the unit for the play of the game.

Your analogy once again dismantles your case. The rule would say 'returned to play' if it meant 'returned to play'. The rules says 'return to this unit' since it meant 'return to this unit'. That's the RAW. The burden of proof is on you to show a rule that Reanimation Protocols meant something different than 'return to unit' when it said 'return to unit'. Otherwise we obey what the rule says. That's the RAW.

 Charistoph wrote:

col_impact wrote:

 Charistoph wrote:

col_impact wrote:
1) First, he must define 'play' as all Core Rules except rules that specifically target the 'removed from play' zone (e.g. Kill points, Reanimation Protocols) which is an entirely made up category on his part.

I have never stated that there was a "removed from play" zone. That is your manufacturing. However, 'play' must be defined as we are instructed to remove the model from play. When you 'play' with a model, you are moving it, shooting with it (hopefully), Charging with it (maybe), and fighting with it (maybe). When it is removed from play, you are not moving it, shooting with it, Charging with it, or fighting with it, no matter how much you would like to complicate this concept.

You are making up this definition of 'play'. There is no such definition in the rules. So once again it is an example of a house rule that you must invent in order to fix the rules that you radically break with your premise that 'slain models are in units'. This is one of the reasons why your premise is invalid.

I never stated this was a definition. I was stating that is what people do with the model when it is in play, and what people don't do with it when it has been removed from play.

Can you provide any actual core rules which actually state we do otherwise?

Right. So it's a house rule that you are inventing in order to repair the game you profoundly broke with your premise that 'slain models are in units'.

You have only presented ridiculously invalid arguments so far. You require 6+ house rules to prop up your premise.

Alternatively, we can accept the RAW that slain models are not in units and slain models are automatically exempt from all the Core Rules your premise breaks. Our argument requires no house rules.

 Charistoph wrote:

col_impact wrote:
Exactly. Charistoph has been wholly unable to present a valid argument that doesn't break all the Core Rules.

Just because you don't like it, doesn't mean it hasn't been done. There is a difference. The main differences is that I acknowledge that most of this indication of 'play' is how players play it, not written statements.

So you break the Core Rules with your premise and then fabricate 6+ house rules out of thin air to repair the broken mess your premise caused. Let me know when you have a valid argument for consideration.

 Charistoph wrote:

col_impact wrote:

charistoph wrote:The issue is where are we instructed to actually remove the model from the unit without relying on making up instructions?

Leadership rolls could be a case where it is relying on models in play as much as in the unit. We presumably cannot call on them for Leadership any more than we can call on them for Shooting or checking to see if they are Coherency.

Are we supposed to take your ad hoc rationale here seriously (highlighted in red)?

Are we supposed to take your statements of RAW seriously when you add words to the rules?

You still have yet to properly answer the questions provided, nor answer the challenges requested to demonstrate the RAW validity of your and orknado's stance:
* Quote Reanimation Protocols and highlight where it states "out", "not in", "Wound", or "datasheet".
* Quote the core rule that states a model is removed from the unit.
* Quote the datasheet rule that states only models within a unit have access to the datasheet and highlight the word "only".

Tenet #1, You say it is written, prove it.

I have repeatedly demonstrated my rules support.
The Reanimation Protocols rule indicates that reanimated slain models are 'returned to this unit' meaning that prior they were not in the unit. That is direct rules support.

The Datasheet rule by definition lists the characteristics for models in units. The datasheet does not list characteristics for models not in the unit.

Combined the RP rule and the Datasheet rule prove that a slain model has no wound characteristic and is reanimated per the number of wounds on its datasheet.

I am not required to quote only Core Rules to support my argument. The RP rule is in the Necron codex and is equally a rule as any rule in the Core Rules.

 BLADERIKER wrote:
So simple enough question then as it pertains to this.

If I have a 30 model unit of Orc Boys, and I lose 10 to shooting what is my leadership value for the subsequent moral test?

The mob rule allows me to substitute the Boyz Ld value (Of 6) for the number of models in the unit (In this case 30) or which ever is higher.

If we presume that models count as part of a unit even after they suffer fatal wounds (and are removed from the table/playing field) then the Ld value should be 30 even if one boy remains.

However, if we presume that once a model suffers a fatal wound they are removed from the unit (Thus no longer part of it, but having come from it), then having 20 boy left out of 30 nets us a Ld value of 20 (as those Boyz lost to shooting no longer count s being "in" the unit).

This is an excellent example that proves that Charistoph's argument is implausible.

col_impact wrote:
The Reanimation Protocols rule asserts with its own wording that slain models are not IN units because slain models that are reanimated are 'returned to this unit'. 'Unit' is an organizational term in 8th edition, so slain models must not be part of the unit organization. There is absolutely no other way of construing it.

You need to learn to differentiate the difference between imply and assert. You are actually asserting the rule is implying it, but have yet to demonstrate that it is asserting it. Look up the difference between the words.

* Quote Reanimation Protocols and highlight where it states "out", "not in", "Wound", or "datasheet".

col_impact wrote:
Per the Datasheet rule, datasheets list the characteristics of models in the unit. When slain models are not in the unit, the datasheet will not list them. The rule directly supports my argument. The burden of proof is on you to show some rule that affixes the profile to the model since the datasheet does not list characteristics for models that are not in units.

* Quote the core rule that states a model is removed from the unit.
* Quote the datasheet rule that states only models within a unit have access to the datasheet and highlight the word "only".
* Quote the core rule that states that when a model is removed from a unit, it loses its connection to the datasheet.

col_impact wrote:
By its very wording, the Reanimation Protocols rule indicates that slain models that are reanimated are 'returned to this unit'. This can only mean that prior to reanimation they were not IN the unit. The rules directly support my argument.

No, Reanimation Protocols STATES the slain model is 'returned to this unit'. To demonstrate that the returning model was not IN the unit, we must demonstrate that it was out before hand.

* Quote the core rule that states a model is removed from the unit.

col_impact wrote:
Further, the Datasheet rule directly states it lists the characteristics for models in the unit. When a model is slain and not in the unit, the datasheet will not list its characteristics. The rules directly support our argument.

* Quote the datasheet rule that states only models within a unit have access to the datasheet and highlight the word "only".
* Quote the core rule that states that when a model is removed from a unit, it loses its connection to the datasheet.

col_impact wrote:
The Reanimation Protocols rule indicates by its wording that without a doubt slain models are not in units. Slain models that are reanimated are 'returned to this unit' which means that prior they were not in the unit.
The Datasheet rule lists the characteristics for models that are in units. The RP rule tells us slain models are not in units. Both of these rules combined directly indicate that datasheets do not list the characteristics of slain models.
I am not required to support my argument with Core Rules. The Necron index has rules of equal authority in this argument. Don't task me with requirements I do not have.

* Quote Reanimation Protocols and highlight where it states "out", "not in", "Wound", or "datasheet".

col_impact wrote:
Your analogy once again dismantles your case. The rule would say 'returned to play' if it meant 'returned to play'. The rules says 'return to this unit' since it meant 'return to this unit'. That's the RAW. The burden of proof is on you to show a rule that Reanimation Protocols meant something different than 'return to unit' when it said 'return to unit'. Otherwise we obey what the rule says. That's the RAW.

Umm, why should I demonstrate something as RAW, which I am not stating as RAW? Why should I accept your definition of RAW when you have not properly demonstrated the written rules to support your points? Why should I accept your definition of RAW when you cannot even recognize when I am speaking HIWPI?

Very specifically, we are instructed to have the model "removed from play", not "removed from unit". One can return without ever being out. That was the point of the analogy.

col_impact wrote:
Right. So it's a house rule that you are inventing in order to repair the game you profoundly broke with your premise that 'slain models are in units'.

You have only presented ridiculously invalid arguments so far. You require 6+ house rules to prop up your premise.

Alternatively, we can accept the RAW that slain models are not in units and slain models are automatically exempt from all the Core Rules your premise breaks. Our argument requires no house rules.

When a model is slain, what is the instruction?
* Quote Reanimation Protocols and highlight where it states "out", "not in", "Wound", or "datasheet".
* Quote the core rule that states a model is removed from the unit.
* Quote the datasheet rule that states only models within a unit have access to the datasheet and highlight the word "only".

col_impact wrote:
So you break the Core Rules with your premise and then fabricate 6+ house rules out of thin air to repair the broken mess your premise caused. Let me know when you have a valid argument for consideration.

Do not misrepresent. I only need to add 2 house rules to get this work: The definition of "Play" in reference to "removed from play"; The number of Wounds RP restores.

I do not need to add the house rules of:
> A model removed from play is removed from the unit.
> Adding "only" to the definition of datasheets.
> Removing the connection between the model and the datasheet when the model is removed from play.
> All actions, aside from removing from play, are removed from the model when it is removed from play.

col_impact wrote:
I have repeatedly demonstrated my rules support.
The Reanimation Protocols rule indicates that reanimated slain models are 'returned to this unit' meaning that prior they were not in the unit. That is direct rules support.

To demonstrate that it is direct rules support, we must first indicate the model is out of the unit when it is removed from play. To support this you need:
* Quote Reanimation Protocols and highlight where it states "out", "not in", "Wound", or "datasheet".
* Quote the core rule that states a model is removed from the unit.

col_impact wrote:
The Datasheet rule by definition lists the characteristics for models in units. The datasheet does not list characteristics for models not in the unit.

* Quote the core rule that instructs us to sever a model's connection to the datasheet when it is removed from the unit. OR
* Quote the datasheet rule that states only models within a unit have access to the datasheet and highlight the word "only".

col_impact wrote:
I am not required to quote only Core Rules to support my argument. The RP rule is in the Necron codex and is equally a rule as any rule in the Core Rules.

In order for a statement to be RAW, it must be written. In order to demonstrate that a rule is written, it should be quoted. If you cannot quote the rule and highlight the specific passages, it is not RAW, but assumption or HYWPI. Tenet #1: Don't make a statement without backing it up. Tenet #4: Rules as Written are not How You Would Play It. Please clearly state which one you are talking about during a rules debate, and do not argue a RAW point against a HYWPI point (or vice-versa). Rules As Written (RAW) - This refers to playing by the strict letter of the rules, which can lead to odd or counterintuitive situations. How You Would Play It (HYWPI) - This refers to taking small liberties with the rules to smooth out the odd or counterintuitive situations listed above.

If you want to change your stance to this being HYWPI, fine by me, that's been the whole point of my interaction against orknado's comments and yours. Both you and he have been claiming RAW without providing written proof. When asked for the written proof, both you and he go of on it being logically deduced and not quoting where it actually states it, which is HHWPI not RAW. Neither of you have even properly identified when I was speaking between HIWPI and RAW. Both you and orknado have been assuming all I have presented is RAW and treating it as such.

Charistoph,

I have repeatedly demonstrated my rules support.





The Reanimation Protocols rule indicates that reanimated slain models are 'returned to this unit' meaning that prior to that they were without a doubt not in the unit. That is direct unequivocal rules support.

The Datasheet rule by definition lists the characteristics for models in units. The datasheet does not list characteristics for models not in the unit. If a model ever leaves the unit the datasheet by definition will no longer list it. The datasheet is the entity that actively lists the characteristics for models in the unit. Models do not list their own characteristics. The belief that models list their own characteristics is a misconception on your part that is supported by no rule in 8th edition. There is no rule that indicates a model 'carries' a profile with it or has a profile 'affixed' to it. Datasheets do the listing for models in the unit, and the datasheet does not list the characteristics for those models that are not in the unit.

Combined, the RP rule and the Datasheet rule prove that a slain model that is not in a unit has no wound characteristic listed. With that wound characteristic no longer listed, a slain model is reanimated per the number of wounds on its datasheet. In the case of a Destroyer model that number will be 3 wounds.

You are tasking me with requirements that I am not required to meet to claim a RAW argument. I am not required to quote only Core Rules to support my argument. The RP rule is in the Necron codex and is equally a rule as any rule in the Core Rules. Together, the Reanimation Protocols rule and the Datasheet rule justify my RAW argument.

col_impact wrote:

Spoiler:

Roll a D6 for each slain model FROM this unit (unless the whole unit has been completely destroyed) at the beginning of your turn. On a 5+, the model's reanimation protocols activate and it is RETURNED to this unit, otherwise they remain inactive (although you can roll again at the start of each of your subsequent turns). When a model's reanimation protocols activate, set it up model in unit coherency with any model from this unit that not returned to the unit as a result of reanimation protocols this turn, and more than 1" from enemy models. If you cannot do this because there is no room to place the model, do not set it up.

No highlighting.

col_impact wrote:

Spoiler:

Each unit has a datasheet that lists the characteristics, wargear and abilities of the models IN that unit.

No highlighting. You really do not wish to properly support your statement.

col_impact wrote:
The Reanimation Protocols rule indicates that reanimated slain models are 'returned to this unit' meaning that prior to that they were without a doubt not in the unit. That is direct unequivocal rules support.

The Reanimation Protocols STATE that reanimated slain models are returned to this unit. I am correcting you on this because "indicate" is a weak word for this, while "state" is a stronger and more accurate term.

Returned can mean several things. Coming from outside something is not the exclusive definition of this word. Indeed, you will be hard pressed to find a definition of "return" which states an exclusive association with "out". The definitions "return" has state it is going back to something. One can return from inside a house just as easily as one returns from outside the house. The relationship of "return" to the subject is dependent on where it was previously. In order to have an association with "out", one needs to demonstrate an "out" versus "in" relationship before hand.

So, where are we told the model is "out of the unit"?

col_impact wrote:
The Datasheet rule by definition lists the characteristics for models in units. The datasheet does not list characteristics for models not in the unit. If a model ever leaves the unit the datasheet by definition will no longer list it. The datasheet is the entity that actively lists the characteristics for models in the unit. Models do not list their own characteristics. The belief that models list their own characteristics is a misconception on your part that is supported by no rule in 8th edition. There is no rule that indicates a model 'carries' a profile with it or has a profile 'affixed' to it. Datasheets do the listing for models in the unit, and the datasheet does not list the characteristics for those models that are not in the unit.

The association a model has with a datasheet is established at some point while it is in a unit (its how we know it interacts with the world). In order to demonstrate an exclusive association, the exclusivity must be engaged. Having a term of "only" in the description would do that. Failing that, an instruction to separate the model from the datasheet would be required. There may be no rule that a model carries a profile with it or has a profile affixed to it, but there is no instruction to separate it from the model when it is removed from play. Even more importantly, an actual statement of removing a model from the unit would be required to in order to associate this removal from your definition of the datasheet in the first place.

Where does it it state this exclusive relationship of the model with the datasheet?
Failing that, where is the relationship of the model with the datasheet stated to be terminated?

col_impact wrote:
You are tasking me with requirements that I am not required to meet to claim a RAW argument. I am not required to quote only Core Rules to support my argument. The RP rule is in the Necron codex and is equally a rule as any rule in the Core Rules. Together, the Reanimation Protocols rule and the Datasheet rule justify my RAW argument.

I am tasking you with requirements to demonstrate a RAW argument. If you cannot quote and highlight the relevant portions of a rule, there is no specific lettering. If you have no specific lettering, you are not practicing RAW.

So, yes, I am tasking you with requirements that are required to support your statements to claim RAW, because you have yet to actually do it. If someone is asking questions about your interpretation, and asking you to provide the written statements which actually state what you are proposing, then obviously they are not believing your assumptions you are basing your reading on.

 Charistoph wrote:

col_impact wrote:
The Reanimation Protocols rule indicates that reanimated slain models are 'returned to this unit' meaning that prior to that they were without a doubt not in the unit. That is direct unequivocal rules support.

The Reanimation Protocols STATE that reanimated slain models are returned to this unit. I am correcting you on this because "indicate" is a weak word for this, while "state" is a stronger and more accurate term.

Returned can mean several things. Coming from outside something is not the exclusive definition of this word. Indeed, you will be hard pressed to find a definition of "return" which states an exclusive association with "out". The definitions "return" has state it is going back to something. One can return from inside a house just as easily as one returns from outside the house. The relationship of "return" to the subject is dependent on where it was previously. In order to have an association with "out", one needs to demonstrate an "out" versus "in" relationship before hand.

So, where are we told the model is "out of the unit"?

As you have stated, "unit" is an organizational term in the rules. You are either in the organization called unit or not in the organization called unit. You cannot 'return to this unit' if you are already in the organization called unit. This is direct unequivocal rules support. You can't use 'hockey' or 'house' metaphors to disprove my argument. You must show how in the case of the organizational term 'unit' that the 40k rules use that some other option is logically plausible than that slain models are not in the organization called 'unit' when they are reanimated to 'return to this unit'. You won't be able to because that is logically impossible based on the direct wording of the rule.


Automatically Appended Next Post:

 Charistoph wrote:

col_impact wrote:
The Datasheet rule by definition lists the characteristics for models in units. The datasheet does not list characteristics for models not in the unit. If a model ever leaves the unit the datasheet by definition will no longer list it. The datasheet is the entity that actively lists the characteristics for models in the unit. Models do not list their own characteristics. The belief that models list their own characteristics is a misconception on your part that is supported by no rule in 8th edition. There is no rule that indicates a model 'carries' a profile with it or has a profile 'affixed' to it. Datasheets do the listing for models in the unit, and the datasheet does not list the characteristics for those models that are not in the unit.

The association a model has with a datasheet is established at some point while it is in a unit (its how we know it interacts with the world). In order to demonstrate an exclusive association, the exclusivity must be engaged. Having a term of "only" in the description would do that. Failing that, an instruction to separate the model from the datasheet would be required. There may be no rule that a model carries a profile with it or has a profile affixed to it, but there is no instruction to separate it from the model when it is removed from play. Even more importantly, an actual statement of removing a model from the unit would be required to in order to associate this removal from your definition of the datasheet in the first place.

Where does it it state this exclusive relationship of the model with the datasheet?
Failing that, where is the relationship of the model with the datasheet stated to be terminated?

Your understanding of how datasheets work is confused and not supported by the rules. Models have no established connection to a datasheet. A datasheet by definition lists the characteristics of models in the unit. So the datasheet is the active entity here that maintains a list, not the model. The datasheet as a listing simply no longer lists the characteristics of a model if the model ceases to be in the unit. That is literally how the rules are written. If you are treating datasheets as permanently affixed to models then you are playing by some set of rules that you have imagined in your head and not by the rules in the book.

Out of curiosity, col, why do you choose to post in such a manner as to to disjoint your response, and possibly lose proper context? In other words, why do you post a response, but only a portion of the post you are responding to, then repost responding to another portion, and so on?

col_impact wrote:
As you have stated, "unit" is an organizational term in the rules. You are either in the organization called unit or not in the organization called unit. You cannot 'return to this unit' if you are already in the organization called unit. This is direct unequivocal rules support. You can't use 'hockey' or 'house' metaphors to disprove my argument. You must show how in the case of the organizational term 'unit' that the 40k rules use that some other option is logically plausible than that slain models are not in the organization called 'unit' when they are reanimated to 'return to this unit'. You won't be able to because that is logically impossible based on the direct wording of the rule.

One can be away from an organization without being out of it. I can use them to demonstrate how the term works.For another case of common use of "return" in regards to an organization, some sports players get hurt or are suspended. When they are able to take the field again, announcers will often state that the player is returning to the team after the injury/suspension. Their contract was not terminated, they were not outside the team, so why would they be using that phrase if "return" was exclusively connected to being out of something?

What is important to note, is that "return" is a term that is dependent on context. Without an actual sentence stating that a model is out of a unit, return is not applying to it being "out of a unit". The only instruction the model has had prior to this is being removed from play. Now, "removed" does indicate an action of placing something out of something, but what we are removing the model from in this phrase is not "a unit", but "play". If RP said "the slain model returns in to the unit", there would be a case of implying that it was out.

So, we are told the model is "out of play", but where are we told the model is "out of the unit"?

col_impact wrote:
Your understanding of how datasheets work is confused and not supported by the rules. Models have no established connection to a datasheet. A datasheet by definition lists the characteristics of models in the unit. So the datasheet is the active entity here that maintains a list, not the model. The datasheet as a listing simply no longer lists the characteristics of a model if the model ceases to be in the unit. That is literally how the rules are written. If you are treating datasheets as permanently affixed to models then you are playing by some set of rules that you have imagined in your head and not by the rules in the book.

You have provided no rules supporting your interpretation so far before now. What has been quoted is one non-exclusive statement that you have reworded in to being exclusive.

Where does it state that the datasheet is an active entity? I understand a datasheet to be a reference document defining a unit and the models within it. After all, that is the only statement we are actually given in regards to it, right?

If a model does not have a connection to a datasheet and profile before it is removed from play, then there is no way for them to move (we are told to look up the characteristic on its datasheet) or be Wounded ("Wounds show how much damage a model can sustain before it succumbs to its injuries", "If a model's wounds are reduced to 0, it is either slain or destroyed and removed from play"). So, a model has an established connection in order to play the game.

Now that a connection has been established, we need permission to sever the connection. Just because we are told that datasheets define for models in a unit, it is no exclusive statement for when they are away from the unit. An exclusive term must be used to indicate this, such as "only". You have not provided this term, so this consideration is pure HYWPI, not RAW.

Since it is not exclusive and we need to have permission to sever the connection, where is the instruction to do so?

 Charistoph wrote:

col_impact wrote:
As you have stated, "unit" is an organizational term in the rules. You are either in the organization called unit or not in the organization called unit. You cannot 'return to this unit' if you are already in the organization called unit. This is direct unequivocal rules support. You can't use 'hockey' or 'house' metaphors to disprove my argument. You must show how in the case of the organizational term 'unit' that the 40k rules use that some other option is logically plausible than that slain models are not in the organization called 'unit' when they are reanimated to 'return to this unit'. You won't be able to because that is logically impossible based on the direct wording of the rule.

One can be away from an organization without being out of it. I can use them to demonstrate how the term works.For another case of common use of "return" in regards to an organization, some sports players get hurt or are suspended. When they are able to take the field again, announcers will often state that the player is returning to the team after the injury/suspension. Their contract was not terminated, they were not outside the team, so why would they be using that phrase if "return" was exclusively connected to being out of something?

What is important to note, is that "return" is a term that is dependent on context. Without an actual sentence stating that a model is out of a unit, return is not applying to it being "out of a unit". The only instruction the model has had prior to this is being removed from play. Now, "removed" does indicate an action of placing something out of something, but what we are removing the model from in this phrase is not "a unit", but "play". If RP said "the slain model returns in to the unit", there would be a case of implying that it was out.

So, we are told the model is "out of play", but where are we told the model is "out of the unit"?

An announcer that says that a player is returning to the team is announcing that the player will once again be considered part of the team for the purposes of the game, where prior the player was not part of the team for purposes of the game. You have just proven my point for me with your example. Unit is an organizational term. You are either considered in the organization or not in the organization for some purpose. The Reanimation Protocols rule states that reanimated slain models are 'returned to this unit' meaning that they were not already considered in the unit. Unit is strictly an organizational term in 8th edition so you must adhere to that context.


Automatically Appended Next Post:

 Charistoph wrote:

col_impact wrote:
Your understanding of how datasheets work is confused and not supported by the rules. Models have no established connection to a datasheet. A datasheet by definition lists the characteristics of models in the unit. So the datasheet is the active entity here that maintains a list, not the model. The datasheet as a listing simply no longer lists the characteristics of a model if the model ceases to be in the unit. That is literally how the rules are written. If you are treating datasheets as permanently affixed to models then you are playing by some set of rules that you have imagined in your head and not by the rules in the book.

You have provided no rules supporting your interpretation so far before now. What has been quoted is one non-exclusive statement that you have reworded in to being exclusive.

Where does it state that the datasheet is an active entity? I understand a datasheet to be a reference document defining a unit and the models within it. After all, that is the only statement we are actually given in regards to it, right?

If a model does not have a connection to a datasheet and profile before it is removed from play, then there is no way for them to move (we are told to look up the characteristic on its datasheet) or be Wounded ("Wounds show how much damage a model can sustain before it succumbs to its injuries", "If a model's wounds are reduced to 0, it is either slain or destroyed and removed from play"). So, a model has an established connection in order to play the game.

Now that a connection has been established, we need permission to sever the connection. Just because we are told that datasheets define for models in a unit, it is no exclusive statement for when they are away from the unit. An exclusive term must be used to indicate this, such as "only". You have not provided this term, so this consideration is pure HYWPI, not RAW.

Since it is not exclusive and we need to have permission to sever the connection, where is the instruction to do so?

The datasheet is the entity that lists the characteristics of models in the unit. A model does not list the characteristics for itself. There is no independent connection between a model and its characteristics that is separate from the datasheet actively listing them. Once the model is no longer in the unit, the datasheet will no longer list the characteristics of the model, per the definition of datasheets.

You keep trying to ascribe permanent characteristics to a model when no rule says this. The fabrications you have in your head do not count as rules.

I have repeatedly provided rules support for my argument. My argument is RAW. It does not care about the fabricated rules that you have in your head and that do not exist as actual rules. Let me know when you have some actual rules to present.

col_impact wrote:
An announcer that says that a player is returning to the team is announcing that the player will once again be considered part of the team for the purposes of the game, where prior the player was not part of the team for purposes of the game. You have just proven my point for me with your example. Unit is an organizational term. You are either considered in the organization or not in the organization for some purpose. The Reanimation Protocols rule states that reanimated slain models are 'returned to this unit' meaning that they were not already considered in the unit. Unit is strictly an organizational term in 8th edition so you must adhere to that context.

And yet, the player is never officially out of the team until the proper forms are signed. If the player is out of the team, he is not paid and anyone else can make a contract with him.

Again, you miss the point of the reference. "Return" is a verb that requires context in order to define where it is returning from. Where is the provision for a model being removed from play to be removed from the unit? Specific instructions are required for RAW. Not an allusion that may or may not be provided by another term.

col_impact wrote:
The datasheet is the entity that lists the characteristics of models in the unit. A model does not list the characteristics for itself. There is no independent connection between a model and its characteristics that is separate from the datasheet actively listing them. Once the model is no longer in the unit, the datasheet will no longer list the characteristics of the model, per the definition of datasheets.

Again, where is the datasheet defined as an entity? I see it being defined as a reference, nothing more. If you consider a reference an entity, then the rulebook would also be an entity, as would an encyclopedia

I am not saying that there is an independent connection between a model and its characteristics separate from the datasheet. I am saying a connection is established, now where is the instruction to separate them? When it is removed from the unit? Again, where is this instruction? Tenet #1, quote the rule, please.

col_impact wrote:
You keep trying to ascribe permanent characteristics to a model when no rule says this. The fabrications you have in your head do not count as rules.

False. I have stated nothing about anything being permanent. I am asking where is the instruction to sever a connection that has been made. You are refusing to support your claim with rules, but only assertions on how you think "return" is associated with "out" and misrepresenting a word in a sentence.

col_impact wrote:
I have repeatedly provided rules support for my argument. My argument is RAW. It does not care about the fabricated rules that you have in your head and that do not exist as actual rules. Let me know when you have some actual rules to present.

You have quoted rules, but you have not provided the proper support of terms within those rules to validate your stance as RAW. When asked to provide the validation, you ignore it, claim that you do not have to, or make wild claims about another's position. So, which is it? Is your claim RAW and you can quote and highlight the exact terminology that has been requested for at least 6 pages now (if not more), or will you continue to refuse to do so, thus demonstrating in action that it is only HYWPI?

 Charistoph wrote:

col_impact wrote:
An announcer that says that a player is returning to the team is announcing that the player will once again be considered part of the team for the purposes of the game, where prior the player was not part of the team for purposes of the game. You have just proven my point for me with your example. Unit is an organizational term. You are either considered in the organization or not in the organization for some purpose. The Reanimation Protocols rule states that reanimated slain models are 'returned to this unit' meaning that they were not already considered in the unit. Unit is strictly an organizational term in 8th edition so you must adhere to that context.

And yet, the player is never officially out of the team until the proper forms are signed. If the player is out of the team, he is not paid and anyone else can make a contract with him.

Again, you miss the point of the reference. "Return" is a verb that requires context in order to define where it is returning from. Where is the provision for a model being removed from play to be removed from the unit? Specific instructions are required for RAW. Not an allusion that may or may not be provided by another term.

You don't understand your own example. A player in the penalty is removed from the team in the context of the game so indeed he is out of the team.

For the game of 40k, unit is strictly an organizational term in the game and you must adhere to that context. The Reanimation Protocols rule states that reanimated slain models are 'returned to this unit' meaning that they were not already in the unit. Therefore, it can be unequivocally stated that slain models are not in units. That's the Reanimation Protocols rule as it is written and we must adhere to that rule.


Automatically Appended Next Post:

 Charistoph wrote:

col_impact wrote:
The datasheet is the entity that lists the characteristics of models in the unit. A model does not list the characteristics for itself. There is no independent connection between a model and its characteristics that is separate from the datasheet actively listing them. Once the model is no longer in the unit, the datasheet will no longer list the characteristics of the model, per the definition of datasheets.

Again, where is the datasheet defined as an entity? I see it being defined as a reference, nothing more. If you consider a reference an entity, then the rulebook would also be an entity, as would an encyclopedia

I am not saying that there is an independent connection between a model and its characteristics separate from the datasheet. I am saying a connection is established, now where is the instruction to separate them? When it is removed from the unit? Again, where is this instruction? Tenet #1, quote the rule, please.

The datasheet by definition lists the characteristics of models in the unit. If a model is in the unit, the datasheet by definition will list the model's characteristics. If a model is not in the unit, the datasheet by definition will not list the model's characteristics. Datasheets will not list the characteristics for any slain models since slain models are not in units. It couldn't be any more straightforward. I am not sure why you are struggling with this. Do you similarly struggle with 1+1=2? Everything I am claiming is proceeding directly from the very definition of the Datasheet.


Automatically Appended Next Post:

 Charistoph wrote:

col_impact wrote:
You keep trying to ascribe permanent characteristics to a model when no rule says this. The fabrications you have in your head do not count as rules.

False. I have stated nothing about anything being permanent. I am asking where is the instruction to sever a connection that has been made. You are refusing to support your claim with rules, but only assertions on how you think "return" is associated with "out" and misrepresenting a word in a sentence.

The datasheet by definition lists the characteristics of models in the unit. Slain models are not in units. So the datasheet will not list the characteristics of slain models. This is all by definition. If you claim that a datasheets lists the characteristics of models that are not in units then you are directly contradicting the definition you are provided.


Automatically Appended Next Post:

 Charistoph wrote:

col_impact wrote:
I have repeatedly provided rules support for my argument. My argument is RAW. It does not care about the fabricated rules that you have in your head and that do not exist as actual rules. Let me know when you have some actual rules to present.

You have quoted rules, but you have not provided the proper support of terms within those rules to validate your stance as RAW. When asked to provide the validation, you ignore it, claim that you do not have to, or make wild claims about another's position. So, which is it? Is your claim RAW and you can quote and highlight the exact terminology that has been requested for at least 6 pages now (if not more), or will you continue to refuse to do so, thus demonstrating in action that it is only HYWPI?

I have repeatedly demonstrated my RAW support. Reanimation Protocols returns slain models to units meaning that they were not already in units. Datasheets list the characteristics of models in units. Slain models are not in units so a datasheet by definition will not list the characteristics for slain models. When a slain model is reanimated and returned to the unit, the datasheet will then list its wound characteristic, which in the case of a Destroyer will be 3 wounds.

You are providing examples that ironically prove my point. You are fabricating rules in your head that have nothing to with the rules in the book. You are also proposing things that directly contradict the definitions provided by the rule book. At this point you are simply being obtuse and don't want to admit defeat.

col_impact wrote:

 Charistoph wrote:

col_impact wrote:
An announcer that says that a player is returning to the team is announcing that the player will once again be considered part of the team for the purposes of the game, where prior the player was not part of the team for purposes of the game. You have just proven my point for me with your example. Unit is an organizational term. You are either considered in the organization or not in the organization for some purpose. The Reanimation Protocols rule states that reanimated slain models are 'returned to this unit' meaning that they were not already considered in the unit. Unit is strictly an organizational term in 8th edition so you must adhere to that context.

And yet, the player is never officially out of the team until the proper forms are signed. If the player is out of the team, he is not paid and anyone else can make a contract with him.

Again, you miss the point of the reference. "Return" is a verb that requires context in order to define where it is returning from. Where is the provision for a model being removed from play to be removed from the unit? Specific instructions are required for RAW. Not an allusion that may or may not be provided by another term.

You don't understand your own example. A player in the penalty is removed from the team in the context of the game so indeed he is out of the team.

If a player in the penalty box was out of the team, then the team could bring another player on to the ice. In actual fact, they cannot bring another player on to the ice because he is still part of the team.

A team with a player on suspension cannot hire a new player to take his spot if there are rules limiting pay rate or the number of players a team may have on the roster. Why? Because he is not off the team.

In order for a model to be removed from a unit, we must have instructions to remove the model from the unit. You have not presented such, even after numerous requests to provide them. RP may imply it to you when you are reading it, but that is not the same as a specific written instruction telling you to remove the model from the unit.

col_impact wrote:
For the game of 40k, unit is strictly an organizational term in the game and you must adhere to that context. The Reanimation Protocols rule states that reanimated slain models are 'returned to this unit' meaning that they were not already in the unit. Therefore, it can be unequivocally stated that slain models are not in units. That's the Reanimation Protocols rule as it is written and we must adhere to that rule.

I agree that you must adhere to the context. The problem here is you are not providing the rules which establish the context in which you are seeking to apply.

The instructions are such that when a model is slain, it is removed from play. Then, at the beginning of their next turn, a unit with slain models can then roll a die to return the model to the unit. The context of "return" is being applied to the "remove from play" unless we have another set of instructions in between. Where is that set of instructions which turns "remove from play" to "remove from unit"?

col_impact wrote:

 Charistoph wrote:

col_impact wrote:
The datasheet is the entity that lists the characteristics of models in the unit. A model does not list the characteristics for itself. There is no independent connection between a model and its characteristics that is separate from the datasheet actively listing them. Once the model is no longer in the unit, the datasheet will no longer list the characteristics of the model, per the definition of datasheets.

Again, where is the datasheet defined as an entity? I see it being defined as a reference, nothing more. If you consider a reference an entity, then the rulebook would also be an entity, as would an encyclopedia

I am not saying that there is an independent connection between a model and its characteristics separate from the datasheet. I am saying a connection is established, now where is the instruction to separate them? When it is removed from the unit? Again, where is this instruction? Tenet #1, quote the rule, please.

Spoiler:

Each unit has a datasheet that lists the characteristics, wargear and abilities of the models in that unit

The datasheet by definition lists the characteristics of models in the unit. If a model is in the unit, the datasheet by definition will list the model's characteristics. If a model is not in the unit, the datasheet by definition will not list the model's characteristics. Datasheets will not list the characteristics for any slain models since slain models are not in units. It couldn't be any more straightforward. I am not sure why you are struggling with this. Do you similarly struggle with 1+1=2? Everything I am claiming is proceeding directly from the very definition of the Datasheet.

No statement provided that the datasheet is an entity, much less an active entity.

No statement provided that slain models are not in units.

No statement provided that the connection between datasheet and model is disconnected.

This is pure HYWPI, not RAW and a failure to adhere to Tenet #1 and Tenet #4.

col_impact wrote:

 Charistoph wrote:

col_impact wrote:
You keep trying to ascribe permanent characteristics to a model when no rule says this. The fabrications you have in your head do not count as rules.

False. I have stated nothing about anything being permanent. I am asking where is the instruction to sever a connection that has been made. You are refusing to support your claim with rules, but only assertions on how you think "return" is associated with "out" and misrepresenting a word in a sentence.

The datasheet by definition lists the characteristics of models in the unit. Slain models are not in units. So the datasheet will not list the characteristics of slain models. This is all by definition. If you claim that a datasheets lists the characteristics of models that are not in units then you are directly contradicting the definition you are provided.

No statement provided that slain models are not in the unit.

No statement provided that the relationship between model and datasheet only occurs so long as a model is within a unit.

No statement provided that slain models lose their connection to the datasheet.

Without proper written statements, this is pure HYWPI, not RAW, and a failure to adhere to Tenet #1 and Tenet #4.

col_impact wrote:

 Charistoph wrote:

col_impact wrote:
I have repeatedly provided rules support for my argument. My argument is RAW. It does not care about the fabricated rules that you have in your head and that do not exist as actual rules. Let me know when you have some actual rules to present.

You have quoted rules, but you have not provided the proper support of terms within those rules to validate your stance as RAW. When asked to provide the validation, you ignore it, claim that you do not have to, or make wild claims about another's position. So, which is it? Is your claim RAW and you can quote and highlight the exact terminology that has been requested for at least 6 pages now (if not more), or will you continue to refuse to do so, thus demonstrating in action that it is only HYWPI?

I have repeatedly demonstrated my RAW support. Reanimation Protocols returns slain models to units meaning that they were not already in units. Datasheets list the characteristics of models in units. Slain models are not in units so a datasheet by definition will not list the characteristics for slain models. When a slain model is reanimated and returned to the unit, the datasheet will then list its wound characteristic, which in the case of a Destroyer will be 3 wounds.

You are providing examples that ironically prove my point. You are fabricating rules in your head that have nothing to with the rules in the book. You are also proposing things that directly contradict the definitions provided by the rule book. At this point you are simply being obtuse and don't want to admit defeat.

Failure to address any requests for written proof as requested numerous times. Only statements of "trust me" and "you are making things up", with implications of accusations of lying.

You are pushing a HYWPI as RAW, violating Tenets #1, #1a, and #4 while doing so. Enjoy your kicking at the pricks. I will not participate in this with you any more.

 Charistoph wrote:


In order for a model to be removed from a unit, we must have instructions to remove the model from the unit. You have not presented such, even after numerous requests to provide them. RP may imply it to you when you are reading it, but that is not the same as a specific written instruction telling you to remove the model from the unit.

RP states that slain models are returned to this unit, meaning without a doubt that the slain models were not already in the unit. We have no choice but to adhere to the written rule and treat slain models as not already in the unit when we are reanimating them. The rule offers no choice. Since slain models are not already in the unit per the RP rule then that means the Datasheet rule by definition will not be listing the characteristics for slain models.

That's the Rules As Written. My argument is directly supported by the RP rule and the Datasheet rule. If I treat slain models as already in units or datasheets as listing models not in the units I am directly violating the Rules As Written.


The direct consequence of these combined rules is that the a Destroyer model will be reanimated with 3 wounds. Datasheets by definition do not list wound characteristics for models that are not in units so the zero wound characteristic is lost when a model is slain.

col_impact wrote:

 Charistoph wrote:

col_impact wrote:
As you have stated, "unit" is an organizational term in the rules. You are either in the organization called unit or not in the organization called unit. You cannot 'return to this unit' if you are already in the organization called unit. This is direct unequivocal rules support. You can't use 'hockey' or 'house' metaphors to disprove my argument. You must show how in the case of the organizational term 'unit' that the 40k rules use that some other option is logically plausible than that slain models are not in the organization called 'unit' when they are reanimated to 'return to this unit'. You won't be able to because that is logically impossible based on the direct wording of the rule.

One can be away from an organization without being out of it. I can use them to demonstrate how the term works.For another case of common use of "return" in regards to an organization, some sports players get hurt or are suspended. When they are able to take the field again, announcers will often state that the player is returning to the team after the injury/suspension. Their contract was not terminated, they were not outside the team, so why would they be using that phrase if "return" was exclusively connected to being out of something?

What is important to note, is that "return" is a term that is dependent on context. Without an actual sentence stating that a model is out of a unit, return is not applying to it being "out of a unit". The only instruction the model has had prior to this is being removed from play. Now, "removed" does indicate an action of placing something out of something, but what we are removing the model from in this phrase is not "a unit", but "play". If RP said "the slain model returns in to the unit", there would be a case of implying that it was out.

So, we are told the model is "out of play", but where are we told the model is "out of the unit"?

An announcer that says that a player is returning to the team is announcing that the player will once again be considered part of the team for the purposes of the game, where prior the player was not part of the team for purposes of the game. You have just proven my point for me with your example. Unit is an organizational term. You are either considered in the organization or not in the organization for some purpose. The Reanimation Protocols rule states that reanimated slain models are 'returned to this unit' meaning that they were not already considered in the unit. Unit is strictly an organizational term in 8th edition so you must adhere to that context..

You have this fundamentally wrong, color, and it's telling that you later accuse Christoph of not understanding his own example. The player is part of the organization still while not in the game, and for purposes of the game is still part of the organization. When he returns to the game from the penalty box, the player's statistics are the same as they are when he went into the penalty box. This example in no way at all proves your point, so you really should not claim it does, unless you suddenly changed your mind and now think a model comes back into the game with the same stats it has when it left.

You still have not offered any rules proof that shows that during a game, characteristics bestowed on the character are lost during the game. Without a statement to modify the profile they had or that they lost their profile, they still have whatever statistics they had when last in play as there is no rule to allow you to assume otherwise. Normally it doesn't matter because normally they don't come back in the same game, but here it does. And the video showing them coming back with 1 wound may not be strict RAW, but does help expose that the assumptions you make are not valid, since they wouldn'the play like that if they were. RAW, they did not indicate what wound level to come back with. You do not get to assume it's 3 wounds when the only RAW suggests they come back with what they left. Work out a house rule with the people you play with, but do not presume to sell a stack of hypotheses and assumptions as actual RAW.

 doctortom wrote:


You still have not offered any rules proof that shows that during a game, characteristics bestowed on the character are lost during the game. Without a statement to modify the profile they had or that they lost their profile, they still have whatever statistics they had when last in play as there is no rule to allow you to assume otherwise. Normally it doesn't matter because normally they don't come back in the same game, but here it does. And the video showing them coming back with 1 wound may not be strict RAW, but does help expose that the assumptions you make are not valid, since they wouldn'the play like that if they were. RAW, they did not indicate what wound level to come back with. You do not get to assume it's 3 wounds when the only RAW suggests they come back with what they left. Work out a house rule with the people you play with, but do not presume to sell a stack of hypotheses and assumptions as actual RAW.

Datasheets by definition list the characteristics of models in the unit. If your datasheets are listing characteristics of models not in the unit then you are violating plainly stated rules. That's the Rules as they Are Written.

 doctortom wrote:
Without a statement to modify the profile they had or that they lost their profile, they still have whatever statistics they had when last in play as there is no rule to allow you to assume otherwise. Normally it doesn't matter because normally they don't come back in the same game, but here it does. And the video showing them coming back with 1 wound may not be strict RAW, but does help expose that the assumptions you make are not valid, since they wouldn'the play like that if they were. RAW, they did not indicate what wound level to come back with. You do not get to assume it's 3 wounds when the only RAW suggests they come back with what they left.

Are you suggesting the rules writers intended for players to keep track of how many wounds each individual model had left before it was removed from the table?
That would be incredibly convoluted for an edition that wants to "streamline" play.
Example.
Models A, B, and C are in a unit. They each have 3 wounds with RP.
Turn one,
Model A takes 3 damage and is removed.
Model B takes 2 damage, has 1 wound remaining.
Model C takes 0 damage.
Turn two,
Model A fails RP, does not come back.
Model B takes 1 damage and is removed.
Model C takes 0 damage.
Turn three,
Model A and B both pass their RP.
Model A had left the table with 3 wounds so comes back with 3 wounds.
Model B had left the table with 1 wound so comes back with 1 wound.
...
If they're trying to simplify playtime this edition, having an extra time consuming book keeping mechanic like this seems much more counter intuitive than just "bring them back the same way they come on normally"

Skoffs, slain models are not in units.

And Datasheets by definition list the characteristics of models in units.

If your datasheets are listing the values of characteristics for models that are not in units then you are breaking from the rules as written for the datasheet.

Col, nobody cares about the ad nauseum in/out-datasheet raw vomit that's been going on for the past however many pages except for you three who are keeping it going.
For the majority of us, we already figure we know how it was meant, RAI (the way ITC is ruling it), so that's how we're going to be playing it until a FAQ says otherwise.
I simply saw doctortom post something I wanted some clarification from him on.

 skoffs wrote:

 doctortom wrote:
Without a statement to modify the profile they had or that they lost their profile, they still have whatever statistics they had when last in play as there is no rule to allow you to assume otherwise. Normally it doesn't matter because normally they don't come back in the same game, but here it does. And the video showing them coming back with 1 wound may not be strict RAW, but does help expose that the assumptions you make are not valid, since they wouldn'the play like that if they were. RAW, they did not indicate what wound level to come back with. You do not get to assume it's 3 wounds when the only RAW suggests they come back with what they left.

Are you suggesting the rules writers intended for players to keep track of how many wounds each individual model had left before it was removed from the table?
That would be incredibly convoluted for an edition that wants to "streamline" play.

Example.
Models A, B, and C are in a unit. They each have 3 wounds with RP.
Turn one,
Model A takes 3 damage and is removed.
Model B takes 2 damage, has 1 wound remaining.
Model C takes 0 damage.
Turn two,
Model A fails RP, does not come back.
Model B takes 1 damage and is removed.
Model C takes 0 damage.
Turn three,
Model A and B both pass their RP.
Model A had left the table with 3 wounds so comes back with 3 wounds.
Model B had left the table with 1 wound so comes back with 1 wound.
...
If they're trying to simplify playtime this edition, having an extra time consuming book keeping mechanic like this seems much more counter intuitive than just "bring them back the same way they come on normally"

I don't think he suggesting that at all. If we consider that Reanimation Protocols only applies to slain models, then the situation would always be zero. After all, that's what caused them to be removed from play. The only ones that we need to worry about are those models who are removed from play without being slain (for example, from the Morale Phase), but still have a chance to come back.

We also should consider that GW has never seriously considered Warhammer to be a competitive game, but a game that people can get together and play over beer and pretzels (or root beer in my case), and that we are intelligent and mature enough to make the changes or additions we choose. That is but one of the reasons why making a distinction between RAW and HYWPI is important in these discussions.

 Charistoph wrote:

I don't think he suggesting that at all. If we consider that Reanimation Protocols only applies to slain models, then the situation would always be zero. After all, that's what caused them to be removed from play. The only ones that we need to worry about are those models who are removed from play without being slain (for example, from the Morale Phase), but still have a chance to come back.

We also should consider that GW has never seriously consider Warhammer to be a competitive game, but a game that people can get together and play over beer and pretzels (or root beer in my case), and that we are intelligent and mature enough to make the changes or additions we choose. That is but one of the reasons why making a distinction between RAW and HYWPI is important in these discussions.

You are simply confused in your understanding.

By RAW, slain models are not in units and Datasheets by definition list characteristics for models in units.

If you are allowing Datasheets to list characteristics for models that are not in units you are breaking a plainly stated rule.

From the FAQ:

NECRONS
Q. How many wounds do Necron models have when they return to a unit using Reanimation Protocols?
A. They are returned with their full complement of wounds.

THANK GOD
We can finally end this shameful display that's gone on for far too long

 skoffs wrote:
From the FAQ:

NECRONS
Q. How many wounds do Necron models have when they return to a unit using Reanimation Protocols?
A. They are returned with their full complement of wounds.

THANK GOD
We can finally end this shameful display that's gone on for far too long

So once again, "Most obvious answer to normal people" is the right answer!

Also important:

Q. What about rules that add models to existing units; do I
need to pay reinforcement points for those models?
A. No (unless the rule itself says otherwise).

 Oaka wrote:
Also important:

Q. What about rules that add models to existing units; do I
need to pay reinforcement points for those models?
A. No (unless the rule itself says otherwise).

Not sure how this applies to anything Necron.
All their stuff can only "bring things back", not "add to".

I guess that including the official FAQ on the first post would be nice.
No more doubts! All hail the holy FAQ!

WOW, you mean common sense won over people trying to game rules with stupid arguements? Who woulda thought!

XvReaperXv wrote:
WOW, you mean common sense won over people trying to game rules with stupid arguements? Who woulda thought!

There was a also some people who were stating the same result with some even more stupid arguments, so this statement is not very polite.

And there was no actual common sense answer to the situation, there was just the answer people wanted to put in to the system.

 Charistoph wrote:

XvReaperXv wrote:
WOW, you mean common sense won over people trying to game rules with stupid arguements? Who woulda thought!

There was a also some people who were stating the same result with some even more stupid arguments, so this statement is not very polite.

And there was no actual common sense answer to the situation, there was just the answer people wanted to put in to the system.

You just weren't reading the Rules As Written correctly. It happens. You had an absurd premise that 'slain models are in units' that broke all of the Core Rules. That is what 'game rules with stupid arguements [sic]' refers to.

Oh just stop it, the both of you.
A mod needs to lock this thread already.