Because the whole bitching/suggesting/brainstorming ideas for MO before nuMO had happened lead us to current situation (eg nuMO). So yeah, I wouldn't say that "just bitching' is pointless (as being constructive is apparently pointless and stupid).
Not sure that's how it happened. But if it was like that, do we need to keep on ranting about how much Teutons suck? Of course they do, and I'm pretty sure people al CB got the message already.
The KotHS w LGL is a good answer to most ALEPH and OSS builds thanks to their heavy use of Remotes (especially as fireteams and order batteries). The same can be said for Vanilla Combined and Onyx. But outside of those target rich environments the opportunity cost is simply too high. It's not bad... just limited in its application.
High BS LGL with FD would be a no-nonsense counter to such builds in some army capable of bringing a better order support without forfeiting too many decent action pieces. Then again, it would still depend a lot on who gets the first turn.
If we're moving away from bitching about how crap the faction is to trying to find what is most effective in it, how about this; anyone tried basing a list around the Tikbalang? My first draft is; -Tikbalang -Joan Spitfire LT -TO FO Sgt -TO MSR Sgt or Santiago Killer Hacker -Santiago Spitfire Specialist -Warcor+Techbee -2x Order Sgt or Fugazi and Mule REM -Machinist + Palbot Your getting 11 orders + the LT Coordinated order in your limited insertion force. Compared to vanilla, you give up a bunch of good shit, but get an AP HMG, more than one Santiago, and better access to TO infiltrators for scoring or fire support. You can swap the MSR for a Santiago killer hacker easily enough by downgrading the cheerleaders to REMs and similar measures. Still feel this comes under my 'don't do things that vanilla is doing better' clause from way back in this thread, but this build does have some advantages over a tikbalang list in vanilla. Would work fine as a TAG list alongside a paintrain or FO SGT spam main list.
if it is a holo 1 HI is hackable disguised as a hacker, but if the enemy is a zero KHD, he can do nothing (and is legal), but I think the holoed HI would reveal afterwards
So firstly, if it was, then it was a mistake on my part in a friendly game, and not intentional. Saying it is cheating implies that I was deliberately trying to break the rules which I wasn't. Secondly, why was it against the rules? My knight didn't even try to reset, he just tanked it. The guy declare he was going to hack my thing, I said cool , he chose the programme, and I declined to reset. He rolled, was successful, and I told him that the programme had no effect, as whilst the target was hackable, it wasn't affected by khd programmes. Worth saying the knight was only using the first level of holoprojector too. The guy I used it against didn't think it was cheating, and he is a top tier UK player. Sent from my SM-G965F using Tapatalk
I don't know that it would reveal, as it didn't have to make a save, or do anything? Sent from my SM-G965F using Tapatalk
But it was the objective from an attack. Even if the attack did not have any effect, the attack itself would reveal him
From the wiki: Q: How do Holoprojectors interact with Hacking? A: In Holoprojector L1 state the Hackable Characteristic and any Hacking Devices the trooper has are considered Open Information when the trooper is inside the opponent’s Hacking Area. You'd have to tell him, once he had your KotHS in his Hacking Area, that the OS was Hackable but didn't have any Hacking Devices.
So the bit I forgot to mention, the zero was in camo originally, so at what point do I have to say? As he did a surprise attack Sent from my SM-G965F using Tapatalk
As his Hacking Area would be Private Information, the game implodes in a quantum failure. So I'd say you handled it just fine by having the Surprise Shot Hacking Attack fail due to illegal declaration.
It's only public information if you're in your opponent's hacking area, which means he would have to reveal beforehand his marker is a hacker to forces you to disclose your hacking devices and/or the hackable status of your unit. Though I'm not even sure if he is allowed to do so since "Your Private Information remains secret until a specific game event forces you to disclose it." (direct quote from the wiki).
Think =/= Know "so i'm moving this camo marker." "Okay hol' up. So...this fusilier isn't hackable, nor is this trauma doc. that palbot is, but why would you, and that nisse isn't." "do we have to do this every time my marker moves?" "yes. It's the law" Sounds like a horrifying way to play
