Can a cadmus-seed be target of hacking and can he hack back (not that this would be of much use with wip 0)?
If you print a Cadmus hacker, his Sees has the KHD. Hacking is a valid skill against/for a Cadmus Hacker in Seed Embryo State. (disclaimer: if the KHD is not a bug of Army!) Note that being WIP 0 you can try only Maestro or Skullbuster and hope to roll 3 or less, the other programs don't have modifiers and with WIP 0 they are not usable.
Ok, we have 3 things to check. Cadmus KHD (Seed w/KHD), Seed Soldier FO (Seed w/FO), Seed Soldier Paramedic (Seed w/MediKit) @Koni @Zoe
Erh... I think you can't declare a Hacking Attack against an enemy camo/TO camo marker. So the only thing that you get is that the Camo has the Hackable characteristic? Remember, however, that Jammers can declare Intuitive Attack against enemy markers...
You wouldn't even know that, as everything about a camo marker apart from S and group is private IIRC.
The Hackable characteristic is not listed as private information, and has been mentioned before. Picture this, of you want: I have a TO AHD (let's say mk2 proxy) in Hidden Deployment in the middle of the table. It's in the middle of a building and prone, so no LoF to the ground. An enemy TO goes by its side, clearly inside the Mk2's ZoC. The first Short order is move, the second *will* be firing his Swiss-issued HMG against my Dakini link, targeting a Deva I left exposed intentionally. Problem: if I don't know for sure the model is hackable, I cannot declare Delay with my Mk2. So I would let the Swiss to fire (generating an ARO for my Deva), and then Oblivion him unopposed?
Given TO has stealth, you cannot declare ARO until their second short skill so the example is not valid.
Yeah, unless Stealth is not used, the example makes no sense. So let's assume the PanO player is not using Stealth, since he would gain nothing positive from it in this example... Again, Hackable is an Obligatory characteristic, and not classified as Private Information (thus being public), so /shrug.
I've managed to spend the last 6 years blundering my way through games getting this wrong, thanks for the correction!
BS and ARM are also not Private Info (thus is public) and there is nothing optional in those stats (thus mandatory attribute characteristics). I'd argue MOV, BS, PH, ARM, Hackable, Combi Rifle, and all that is all covered under "The contents of your Camouflage and TO Camouflage Markers."
I have no idea what rules argument you are trying to make. The active trooper is a TO Camo marker, therefore you can delay your ARO. That has nothing to do with Open/Private Information, or the Hackable Characteristic. You do not know the Hackable Characteristic of anything under a TO Camo marker, because: These pieces of information are Private in Infinity: ... The contents of your Camouflage and TO Camouflage Markers. Contenido de los Marcadores de Camuflaje y Camuflaje TO. The only thing you know about the TO marker is it's Silhouette and (via FAQ) it's Combat Group. Are you getting confused with Hackable and Holoprojectors?
@xagroth You're probably thinking about these two rules (which I don't think we've quite clearly had an answer from the devs regarding whether the first one applies to a holo trooper nor whether we should consider hackers to have the Hackable characteristic); http://infinitythewiki.com/en/Advan...Devices_and_Hacking_Programs:_Characteristics "They automatically identify whether a figure—but not a Marker—inside the Hacker's Hacking Area is targetable by a specific Hacking Program." http://infinitythewiki.com/en/Holoprojector#Holoprojector_L1 "However, in Holoprojector L1 state the Hackable Characteristic is considered Open Information when the trooper is inside the Hacking Area of an enemy."
