Huh, where in the deployment rules does it say that Ally units do not count towards on table deployments for reserves? My book is stored at my wargaming clubhouse.
The models need to be part of the Dracothion´s Tail battalion. "You can set up 1 reserve unit waiting to appear at Kuoteq´s command for each unit from the same battalion you set up on the battlefield."
Ohh, might have to leave all 3 units of Saurus Knights on the ground then. I was operating under the assumption that it followed standard deployment rules.
Wait... It's in a faq or is written that way in the GHB2019? ...because in my italian version there's not such a limitation and it wouldn't be the first time that translations are incorrect.
It was added into the GHB2019. It wasn't in the 2018 ed, it might not have been updated correctly in Italian. It is also part of the core rules that you can only place a unit into reserves for each unit that is already deployed on the table. Still trying to find this rule's location. Crawling through the FaQ's and errata/designer commentaries today.
Ah, good to know. And that suddenly creates new problems to the list i was planning to play this weekend...
Hey, Lizwiz, wouldn't FoS be better with a bastiladon? I was wondering that, thanks for your work man
Everything is better with a Bastiladon. The question becomes what you give up to include it. The ScV on Carno and 10x Skinks can certainly be dropped to add one. All the second Carno adds is a meaty body and exploding 6's for the 40x Warrior unit. I think you might get more benefit by adding in Razordons though. FoS is really just a fun Warrior themed platform. My list is far from the most optimized version of it as it does little to take advantage of the extra movement battalion buff. I think the best way to wield it with MinSU warrior units as a tax for being 1 drop with extra artefacts.
You could drop the cogs and skinks for some razordons to add a bit of shooting (6d6 and rerolls is nothing to scoff at). I do believe though that the scar veteran is much more optimal then a bastiladon in a FoS, simply because of those extra attacks meaning anything will get gutted by the warriors.
Cogs adds a lot to the battalion. Not only is it beneficial for summoning, but it can be used for a massive turn one movement within the battalion.
The main short fall of FoS is the amount of tax the battalion requires. The platform itself is rather useful for the 1 drop and extra movement. Essentially, if you want to do well with FoS at a tournament it won't be warrior based. You could potentially do something fun with Carnosaurs and cogs to get turn one charge reach. Perhaps a Terradon version of Fos could allow for turn one Rock drops to snipe supporting heroes. Most of the things I would do with FoS are done better with DT. Thus, the primary attraction of the battalion to me is that it makes Saurus Warriors usable. The list posted to this thread is the one I use when helping AoS players improve their games.
When i play FOS i literally kill nothing and just throw bodies at objectives for 5 turns. Usually i can get out to such a big lead by the time you lose everything your opponent cant come back. Its a questionable way to play the game but i dunno how else you can win with saurus. This is the only thing that seems to work at a competitive level and even then its a rough go.
FoS is interesting to say the least. I would say that against daemons that have to go in Melee (slaanesh, khorne, burgle) it does ok. If you can get reroll saves of 1, or just rerolling failed saves warriors become decently tough for their price point. However if you want better staying power maybe guards could be used with razordons or salamanders in support as guard do have decent staying power.