>>6175244Yes, Agent Dragon - that's what it's intended for! And it also provides on-the-spot restraints, seals holes, plug gaps, fixes leaks and at very low dosages shines up your hair. Outputting FOAM on a precise, localized spot really affixes any two things to each other.
<span class="mu-s">As for your other question, Agent</span>, yes. Recall that NoGard is a <span class="mu-s">enormously</span> advanced, adaptive system. You either direct it to take action on its own - whenever you order it around, it spends 9 AL to take actions, using its "Sophont" value of 3. So 3d10. It sometimes generates and builds tools adaptively itself - if you ask it to mark someone, it's likely to cobble together some sensors first to mark it properly.
You can <span class="mu-s">also</span> use Process+Sophon to "pair" with NoGard, taking advanced data operation actions. One of those very much is building more advanced tools or allowing it direct acccess to systems and tools you have (Proficiency+Sophont lets you work together to attack with a smartgun!)
The CRADLE outputs shortlived, advanced maeshdemons systems.
>3AL: Spin-up a MarkerDaemon [Process3+MeshOps3, Cradle2] -- 3 hits, +2 straight effect, 5 hits total, you get a MarkerDaemon with 2Ping and +2 Firewall. It goes off and performs actions autonomously until its core routines is no longer up to date and then it degrades; usually by having its firewalls breached and being compromised. It's like a ... lesser, smaller version of NoGard?
But you could simply *make a meshshell for NoGard*, or give it access to allowing it to make its own fine-tuned tools.
>3AL: Process3+Sophont3: Try to spin up a Sophont-Level ewar package.3 hits, +2 from the CRADLE, but this is *sophont level software operations*, NoGard is briefly flash-deriving entirely new adaptions to its core featureset and likely intuitively and autonomously using code-integrations we can't even easily analyse without lab time. It's like... It's like what GhostlyGlitch is doing, Agent! S--- oh it all fits, she's just a Sophont too!!
Sophont-Level Emergent Mesh Phenomena <span class="mu-s">breaks the rules</span>, it uses novel architecture to accomplish novel things, Agent. A standard firewall might sometimes not even have the ability to detect that there's hostile intrusions happening, it might bypass advanced cloaks, it might derive new targetting for links, a host of other features.
Unlike the lesser MeshDaemons, this functionality just incorporates into NoGard's meshshell. If you want to get specific, it's really because it's likey copying its own code and spawning a minor that it uses seamlessly...
Finally, remember that you can - at great risk - add Sophont as a <span class="mu-s">style</span>
>3AL: Process3+MeshOps3+Sophont3, try to take out that cameraA third dicepool
But you aren't monitoring what NoGard actually does - it might do ... very complicated things, or get in the way, or fail to integrate. You have to be <span class="mu-s">very</span> careful with this functionality, because co-riding with an near-autonomous level Sophont is hard!
