Okay, as I try to interpret the ruling on page 12 about the Isolated state, the defining feature is that Sync, Servant, and Antipode are all cases where the Ghost: unit (or Antipode) does not directly receive the order and thus isolated state doesn't do anything to the unit. Rather the controller (or in the case of the Antipode, the pack) receives the order. That distinguishes it from, say, Jumper where Proxies can still be isolated because that Proxy model is receiving the order directly. So what seems odd is that Ghost: Marionette is not included here in the models that avoid isolation. This seems to closely match the Sync/Servant cases, instead of the Jumper cases. What am I missing?
That this is not a change, merely confirmation that the rules work the way they appear to work when reading RAW. Note that this is an FAQ not Errata. G: Marionette and Jumper have rules for how to handle one of them being isolated, the examples listed in the FAQ do not.
That Ghost: Marionettes includes this rule: "If a G: Marionette trooper enters or is in the Isolated or any Null state, they will enter the Disconnected state at the end of the Order that happened." This will trigger No 2, so we know how to manage other Ghost Marionettes if a Troupe Leader is Isolated; and the Fireteam rules tell us what to do if it isn't the Troupe Leader. Further the Disconnected state says: "Troopers in this state cannot declare Orders or AROs." So we know how the Isolated may act (it can't). And finally we're told what to do if all of a Controller's Ghost:Marionettes are Isolated: "The Controller may be activated in the regular manner only when he or she is deployed without G: Marionette troopers, or whenever all of them are in any Null or Isolated state." So there's no rules issues to resolve. Whereas, Ghost Servant, G Sync and Antipodes where not written with this foresight so created ambiguities that CB thought needed an FAQ to resolve / make clear.
Sure... It's not like CB has ever made a rule change in the FAQ, and then in the next FAQ reversed it.
But remember that now, FAQ and ERRATA have different sections, so FAQs do not fix rules, only explain them
