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.

The codex says more than 12" from enemy units and deployment zone... thats it? So if I get to deploy first I put this thing in the middle of the board and pretty much unload half my army super alpha strike on turn 2?

Maybe?

Your opponent has the option of either avoiding or flooding the zone. The Webway Gate won't be much of an advantage if your opponent fills the area wholly within 6" of both of the Wraithbone Arches with melee units and all you have in Strategic Reserves is shooting units you don't to deploy within Engagement range of said units.

Not to mention, you only have so much space to deploy in to start with.

There's no reason to use the gate with shooting units... but melee thats a big deal.

From the core rules:

Units with the Fortifications Battlefield Role are terrain features that are part of your army. Unless otherwise stated, when setting Fortifications up on the battlefield, they cannot be set up within 3" of any other terrain feature that is not part of its own datasheet (excluding hills).

On a typical 9th edition table this will rule out huge sections of the middle and you may not have a legal deployment option in a useful place.

The webway gate has its own rules how to set it up. Core rules dont apply here.

 p5freak wrote:
The webway gate has its own rules how to set it up. Core rules dont apply here.

From the core rules:

Units with the Fortifications Battlefield Role are terrain features that are part of your army. Unless otherwise stated, when setting Fortifications up on the battlefield, they cannot be set up within 3" of any other terrain feature that is not part of its own datasheet (excluding hills).

The webway gate does not state otherwise, it must follow the rule. It's just like weapons that say "this weapon automatically hits" do not get to ignore all of the rules about selecting valid targets just because they have a special rule.

Aecus Decimus wrote:

 p5freak wrote:
The webway gate has its own rules how to set it up. Core rules dont apply here.

From the core rules:

Units with the Fortifications Battlefield Role are terrain features that are part of your army. Unless otherwise stated, when setting Fortifications up on the battlefield, they cannot be set up within 3" of any other terrain feature that is not part of its own datasheet (excluding hills).

The webway gate does not state otherwise, it must follow the rule. It's just like weapons that say "this weapon automatically hits" do not get to ignore all of the rules about selecting valid targets just because they have a special rule.

It does state otherwise. The core rules are for fortifications which dont have any rules how to set it up, like an imperial bunker.

Mysterious Appearance: During deployment, when you set up this unit, it can be set up anywhere on the battlefield that is more than 12" away from the enemy deployment zone and any enemy models.

Nothing specifically says "may be placed within 3" of other terrain" so no exception to the core rule is granted. The webway gate follows both sets of rules and must satisfy every requirement contained there: more than 12" from the enemy deployment zone, more than 12" from any enemy models, and more than 3" from any other terrain (other than hills).

Aecus Decimus wrote:
Nothing specifically says "may be placed within 3" of other terrain" so no exception to the core rule is granted.

It doesnt have to say that. Specific rule overrides general rule. The general rule even says unless otherwise stated, the gate states otherwise, so it uses its own rules how to set it up.

Specific overrides general when there is a contradiction. If a rule says a unit may move 6" it still has to follow the normal rules for moving, it doesn't get to move within engagement range or through terrain which lacks the traits to allow it. You don't get to say "well, it has a specific rule that lets it move 6" so I get to put the model anywhere within 6". Same thing with the webway gate. The specific deployment rules do not grant an exception to the general rule and do not contradict it. Both rules apply and all three conditions must be satisfied.

The "unless otherwise stated" modifies whether you can set up within 3" of terrain. It does not override any other part of the set up rules.

Aecus - anywhere on the table is a conflict.

nosferatu1001 wrote:
Aecus - anywhere on the table is a conflict.

Um, no.

When they say, "unless otherwise specified", the relevant datasheet would need to say that the fortification can be placed within 3" of other terrain.

Plain English, taken together, the Webway Gate can be set up anywhere on the table and at least 3" away from other terrain (and at least 12" away from enemy models/deployment zone).

To claim otherwise is to be intentionally obtuse.

FORTIFICATIONS
Units with the Fortifications Battlefield Role are terrain features that are part of your army. Unless otherwise stated, when setting Fortifications up on the battlefield, they cannot be set up within 3" of any other terrain feature that is not part of its own datasheet (excluding hills). If it is not possible to set up a Fortification as a result, it cannot be deployed and counts as having been destroyed. Fortifications can never be placed into Strategic Reserves.

Mysterious Appearance: During deployment, when you set up this unit, it can be set up anywhere on the battlefield that is more than 12" away from the enemy deployment zone and any enemy models. When this unit is set up on the battlefield, both of its Wraithbone Arches must be set up within 3" of each other. Once it has been set up, each Wraithbone Arch is treated as an Obstacle terrain feature with the following terrain traits: Light Cover, Heavy Cover, Unstable Position, Inspiring (AELDARI).

This is a Glass Half Full, Glass Half Empty question. Is anywhere on the battlefield a statement of otherwise?

It is easy to see that either way depending upon your point of view given that some fortifications have no deployment rules at all.

 alextroy wrote:
Is anywhere on the battlefield a statement of otherwise?

No. As people love to point out, 40k uses a permissive ruleset. "Mysterious Appearance" doesn't give you specific permission to set up the Webway within 3" of other terrain.

nosferatu1001 wrote:
Aecus - anywhere on the table is a conflict.

No it isn't. Let's look at a different example:

C:SM Infiltrator Squad, Concealed Positions rule wrote:During deployment, when you set up this unit, if every model in this unit has this ability then it can be set up anywhere on the battlefield that is more than 9" away from the enemy deployment zone and any enemy models.

Unstable Position terrain trait wrote:Models cannot be set up or end a move on top of this terrain feature (they can move up, over and down this terrain feature, but they cannot end a move on top of it).

How do you think these two rules interact? Do you think that the Concealed Positions rule allows you to set up the unit on top of a terrain feature with the Unstable Position trait?

https://www.dakkadakka.com/dakkaforum/posts/list/30/795894.page#11049896

We’ve done this dance before, people.

Only fun to be had is seeing who’s changed sides, but otherwise it’s the same dogmatic ruck brewing as in this thread.

Agree something with your opponent that’s fun for you both and move on.

The answer is under 9th rules large terrain features are largely irrelevant.

Some tournaments modify these but unless your at one don't take the unit that doesn't work