Question 1: If the Deva Functionary is taken with a Devabot, and Devabot is destroyed/disconnected, can that Deva Functionary be included in a Fireteam? Question 2: If "yes", what if Devabot is then repaired or Deva moves back into Coherency, while still a member of a Fireteam? Which rule takes precedence?
According to G:Sync: A G: Synchronized trooper and its Controller cannot be part of a Coordinated Order nor be a member of any type of Fireteam, unless specified otherwise. But then there's the obnoxiously kind-hearted FAQ: Q: When a trooper with the G: Servant or G: Synchronized Skill is in a Null state or a Disconnected state, can his controller be part of a Coordinated Order? A: Yes. Personally, I'm inclined to point to the scenario for Question 2 (the null state of the G:Sync model being reversible) for the reason why this FAQ doesn't address putting a G:Sync model's controller in a Fireteam, and give the answer: A1: No, because of the situation described in Q2. Also, the FAQ doesn't give you permission to do this for Fireteams, just Coordinated Orders. Your trooper hasn't stopped being the Controller of a G:Sync model. A2: N/A
I don't see what the big problem is. If the Synch gets repaired and reconnected, the Deva is immediately kicked out of the fireteam because they now have a rule applied to them that says they can't be part of a fireteam.
