im sure it functions just like a normal cube against sepsitor but lore says otherwise. i understand in campaigns its garentee resurrection after battle but i find it odd (especially for the steel phalax) that an army meant to fight the EI would have that kind of weakness.
Yeah, it's one of the wackier things about the setting that the force that's specifically about fighting the Combined Army is uniquely vulnerable to it. Really the setting acts like everyone in it is an idiot when it comes to the sepsitor. Regardless, in the rules the Sepsitor works fine against troopers with Cube 2.0.
Back in the N2 days, cube 2.0 had a campaign effect of automatically passing cubevac rolls against any enemy EXCEPT the combine. Against the combine, they automatically FAILED the test, and were lost (presumed sepsitorised). Aleph cuts the connection to backups, and the field units were programmed to self-terminate as a failsafe to prevent the combine getting access to Aleph. "A sepsitorised SSS operative with a fully functional cube2.0 and clearance codes could potentially the access the Aleph network and corrupt it from the inside ... ... To prevent this scenario, cube 2.0s include an emergency shutdown system. When they detect a sepsitor intrusion, a security loop automatically kicks in and instantly erases all access codes to the network and the cube's internal database. ... ... however, this procedure is insufficient in itself, as a sepsitorised sss operative is still a valuable agent for the EI and a potential danger to the human sphere " and goes on to say that cube 2.0 lhosts have an additional "L-gland" that when triggered is supposed to give the bearer a swift and painless way to end their life. The gland secretes a fast acting toxin that causes cardiopulmonary arrest and cerebral death in minutes. This text does not appear to be part of the N3 paradiso campaign related materials.
It's also in the RPG. However, the N3 Campaign book is Daedalus' Fall (the campaign rules... which are the N2 ones with a few tweaks that can be summed as "no 5th level of development for the specialty trees" and "characters that fail cubevac & medevac get the bench for the next battle"). Certainly, something had to be changed to allow for Perseus... if he truly was captured by the EI, that is (it might be a captured Myrmidon by the Nomads and turned into a Nomad-controlled AI).
This is mostly because whilst a cube 1.0 is a physical backup that needs to be retrieved from the battlefield, a cube 2.0 is a direct stream upload (or download, in case of posthumans) to ALEPH's systems. ALEPH cuts loose any suspected of intrusion because of the sepsitor risk to aleph itself.
still gameplay wise (from the perspective from a N1 player coming back into the game,) its just feels derpy when they're the anti EI forces
Fluff wise, all non-posthumans and non-commons (soldiers of fortune, knauf, le muet, etc...) are a part of Aleph. Think of it as in TRON, with Aleph being the whole system while the programs get a body and go around doing stuff... The cube 2.0 allows for them to still be part of ALEPH while away, which is needed. The other option would be to send humans in Lhosts with their mind copied from natural-born ones, because the duplication of ALEPH aspects (like deploying 2 Achilles, for example) would be against the 1 AI Rule Bureau Toth enforces.
You write this like the all powerful AI hasn’t planted an agent amongst the nomad nations. Infiltrating Tunguska only to destroy the data core when it most suits the wise ALEPH’s grand plan of saving humanity from itself and the invading forces of the EI.
No, I was referring only to "why does the Cube 2.0 not act as a dead man's switch, if more than X time passes with no connection, body dies" XD Perseus can really be the Trojan Horse of the EI against the Nomads... or from Aleph against the Nomads... or for the Nomads against Aleph, or... XD
