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.

So I recently watched a battle report on youtube and they mentioned they were ignoring a new beta fly rule from earlier this fall? It had something to do with units with the fly keyword only being able to move over enemy models and terrain during movement phase specifically and having to roll for charge distance like other non fly units. I checked the big faq 2 just now and it talks about the rule and their reasoning behind it but it doesnt show the actual rule? Is it official now and where / in which document can i find it in? Thank you!

Nixalys wrote:
So I recently watched a battle report on youtube and they mentioned they were ignoring a new beta fly rule from earlier this fall? It had something to do with units with the fly keyword only being able to move over enemy models and terrain during movement phase specifically and having to roll for charge distance like other non fly units. I checked the big faq 2 just now and it talks about the rule and their reasoning behind it but it doesnt show the actual rule? Is it official now and where / in which document can i find it in? Thank you!

Rulebook Errata

Page 177 – Moving
Change the second paragraph to read:
‘If the datasheet for a model says it can Fly, then during
the Movement phase it can move across models and
terrain as if they were not there.’

I don't know who thought separating the rule change itself and the reasoning for it into two documents would be a good idea.