![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
NPC colleagues associated with this journal:
NPC Casefile:
Patch code for program with puncture wound through hand. Needed patch to stop injury from spreading before resync.
Cosmetic repairs for a program who landed on her nose. Also advised to decrease neat energy intake.
Legless program in a building Rinzler blew up.
Minor lacerations, bruising, and armor damage due to a building collapse (Rinzler)
Wide-frame scan for code extrapolation, fed code into an open file, incorporated necessary patches/rewrites, tested the fix for compatibility. Incorporated changes into disc(s). Had to collapse memories and dump backup templates just to have processing room for the entirety of the information needed to insert the changes into the complex code. Resynced.
Complications: even a surface scan showed evidence of the large-scale tampering that Rinzler's code had endured. Also, incorporating the fixes took longer because of the complex way the two discs interacted. Procedure was exhausting.
Case notes: workspace snapshot, file of notes and exceptions pertaining to Rinzler's configuration, peripheral information ("took longer to resync but stayed partially aware", "could read his own code").
Follow-up: none.
Glass lacerations with debris in the wound (Aadi)
Medium scan for code extrapolation & to locate debris. Placed code in a flat pane/file next to workspace. Immobilized injured area with a code needle that stopped its energy flow. Extracted glass (no details mentioned) & dropped it in receptacle for derezzing later. Removed needle; rescanned for comparison. Rewrote damaged code in pane/file. Decompressed (Stream code. Scan for errata. Save. Reduce to template. Save. File secure. Memory cleared. Ready.); most information now ONLY in pane/file. Incorporated changes into disc. Cleared cache. Resynced.
Complications: none.
Case notes: notes on glass injuries. Also, various ISO exceptions, for reference when working with other ISOs. Luckily ISO surface format & circuit energy flow is similar to that of Basic programs; if it'd been a more complicated injury he might have only been able to stabilize it. (Used to have a large library of such exceptions; Clu erased it.)
Follow-up: Patient advised to rest more, as chronic lack of downtime had been impeding her healing.
Disc slice to left shoulder; program's healing protocols inoperative (Anon)
Light scan for code extrapolation. Placed code in a read/write file. Isolated damaged code strings. Repaired, with aid of code copied from either side of the gash. Resynced.
Medium scan for issues with healing subroutines, accessing permissions and directory trees. Discovered truncated subroutines stemming from an upgrade that was reverted when Anon was rerezzed.
Complications: Wulf doesn't have the permissions to rewrite and redirect the truncated subroutines; a User would have to do it.
Case notes: nothing but the incident log.
Follow-up: Patient advised to request help from a User in re truncated subroutines, and to get injuries dealt with promptly until that happens.
Energy depletion due to rerezz (Echo)
Fed her an energy packetand fortunately got away without being derezzed for insolence.
Complications: one of these days his protocols, which don't let him take time to summon backup if a program seems injured, are going to force him to tend to a sentry who, once recovered, will go haywire and disc him. He can just see it. :/
Case notes: nothing but the incident log.
Follow-up: noneunless Echo follows him home.
Severe energy depletion and surface damage after rerezzing (Radia)
(Still working on thread.)
Complications: ISO codes.
Case notes: a ton of data on ISO codes.
Follow-up: none.
Lacerated armor, mildly impacted code, disassociative strain leading to a limp (spybot!Ram)
The usual scanning, writing repairs into a code template, inserting into disc, resyncing.
Complications: none
Case notes: nothing but the incident log.
Follow-up: none
Memory integration seizures due to torture in previous life; facial injury due to fall (Lizor)
Preparations: Cooling blanket for seizure-related overheating; scans to create a code template and isolate the damage; standard repair for facial injury done directly over the disc.
Procedure: lacking permissions to repair traumatized memory files, so couldn't repair shattered memory links directly (a User could do it, but that was up to the patient), but "built up an immunity" so that memories could continue to be reintegrated at the patient's pace without the painful seizures (thread not complete).
Complications: Patient's code linked and intermingled with ISO counterpart.
Case notes: due to patient's initial distrust, only Wulf's own memories, dumped and catalogued upon return to the clinic, of the procedure and the intricacies of the merged code (saved in case of future complications).
Follow-up: visited to check on repairs, though thread is incomplete.
Burns, lacerations, torn circuits, disc cuts, embedded Abraxas-viral shards (Anon)
Preparations: Quarantined program and put a barrier around shedded virally-burned voxels; thick flat patch (slow energy-infusion poultice) on a main circuit to counter severe energy depletion; comprehensive scans (handheld and large hanging scanners); code needles to cut off pain impulses for major injuries and while extracting viral shards; energy patches over the burns.
Procedure: Removed viral shards, cleaned and patched wounds, ran new scans to extract a template to fix and recompile the code; loaded onto disc and resynced. Thread not finished, but probably kept Anon overnight for the repairs to settle.
Complications:
Case notes: retained viral shards, which proved non-infectious; notes on Anon's resistance to actual viral corruption, as opposed to the simpler non-infectious burns.
Follow-up: none.
Abraxas-virus infection and viral burns (Kade)
Applied patches for energy transfusion. Isolated virus to prevent its spread; inserted corrections into the scanned code, feeding parts of it at intervals into patient's disc; then wrote in repairs for the burns, while orderlies stood by to clean wounds as they closed. Patient, in shutdown, processed repairs and was released when he woke.
Complications: patient was a 2001-era modern import; made the case more complicated.
Case notes: details of Kade's modern configuration.
Follow-up: none.
Multiple contusions, one leg nearly shattered, code degradation from exposure to the Sea (Krypton)
Built, from multiple scans, a template file with which to stabilize patient for transport (tricky enough that Wulf's hands were shaking when he finished). Uploaded to disc and resynced. Patched leg further upon arrival at the tank (and decontaminated patient's Basic partner, who'd touched the Sea). Transported to clinic for further repairs (HUGE amount of information to process); put patient on a timed recharge to let recovery take hold; released him to go home when he woke.
Complications: ISO code riddled with wrenching stress fractures due to extreme sensitivity to the Sea's virus; preliminary repairs done without access to patient's prior records.
Case notes:
Follow-up:
Injuries and glitches related to stolen disc (Echo; not threaded out)
Patient lost large chunks of memory and was on her way to being a stray. New disc was synced in time to preserve most of her identity, but some could not be retrieved.
Complications:She did follow him home. XDDDDDDDDDDD
Case notes: nothing but the incident log.
Follow-up: stupid beta newbie recompilers chased her out before she was ready to leave the clinic. >.<
Common form of lingering, escalating glitch in air-circulator containment protocols, aftermath of a virus which had laid him flat for several centicycles (tended by User:Gibbs), causing an incessant hacking cough. (Kip)
Suppressants had been prescribed (medic:Kato) but patient, an import, resisted getting his definitions updated because disc repair "felt weird", leading to the glitch escalating over time.
Tailored standard broad-spectrum antiviral definitions to address his problem.
Complications:
Case notes:
Follow-up:
Injury ()
Complications:
Case notes: incident log and....?
Follow-up:
Kare: one of the Grid's many chief medics; utterly competent. One is assured of the correct steps being taken when she's on a case.
Wyman: another chief medic, Kare's polar opposite. Prone to demanding more information and overanalyzing the data until the patient falls apart.
Wilkes: a burly medic with a yellow-white mustache, belligerent, secretly tender-hearted, and good on a lightcycle.
Lister: is just there. Nobody notices Lister.
Seraph: a compact little medic with mock ISO markings on her temples, placed there in solidarity for colleagues lost in the Purge.
Several betas who really had no business in medical work, but times were hard and Wulf's had to keep them around.... even when they make really dumb decisions.
NPC Casefile:
Patch code for program with puncture wound through hand. Needed patch to stop injury from spreading before resync.
Cosmetic repairs for a program who landed on her nose. Also advised to decrease neat energy intake.
Legless program in a building Rinzler blew up.
Minor lacerations, bruising, and armor damage due to a building collapse (Rinzler)
Wide-frame scan for code extrapolation, fed code into an open file, incorporated necessary patches/rewrites, tested the fix for compatibility. Incorporated changes into disc(s). Had to collapse memories and dump backup templates just to have processing room for the entirety of the information needed to insert the changes into the complex code. Resynced.
Complications: even a surface scan showed evidence of the large-scale tampering that Rinzler's code had endured. Also, incorporating the fixes took longer because of the complex way the two discs interacted. Procedure was exhausting.
Case notes: workspace snapshot, file of notes and exceptions pertaining to Rinzler's configuration, peripheral information ("took longer to resync but stayed partially aware", "could read his own code").
Follow-up: none.
Glass lacerations with debris in the wound (Aadi)
Medium scan for code extrapolation & to locate debris. Placed code in a flat pane/file next to workspace. Immobilized injured area with a code needle that stopped its energy flow. Extracted glass (no details mentioned) & dropped it in receptacle for derezzing later. Removed needle; rescanned for comparison. Rewrote damaged code in pane/file. Decompressed (Stream code. Scan for errata. Save. Reduce to template. Save. File secure. Memory cleared. Ready.); most information now ONLY in pane/file. Incorporated changes into disc. Cleared cache. Resynced.
Complications: none.
Case notes: notes on glass injuries. Also, various ISO exceptions, for reference when working with other ISOs. Luckily ISO surface format & circuit energy flow is similar to that of Basic programs; if it'd been a more complicated injury he might have only been able to stabilize it. (Used to have a large library of such exceptions; Clu erased it.)
Follow-up: Patient advised to rest more, as chronic lack of downtime had been impeding her healing.
Disc slice to left shoulder; program's healing protocols inoperative (Anon)
Light scan for code extrapolation. Placed code in a read/write file. Isolated damaged code strings. Repaired, with aid of code copied from either side of the gash. Resynced.
Medium scan for issues with healing subroutines, accessing permissions and directory trees. Discovered truncated subroutines stemming from an upgrade that was reverted when Anon was rerezzed.
Complications: Wulf doesn't have the permissions to rewrite and redirect the truncated subroutines; a User would have to do it.
Case notes: nothing but the incident log.
Follow-up: Patient advised to request help from a User in re truncated subroutines, and to get injuries dealt with promptly until that happens.
Energy depletion due to rerezz (Echo)
Fed her an energy packet
Complications: one of these days his protocols, which don't let him take time to summon backup if a program seems injured, are going to force him to tend to a sentry who, once recovered, will go haywire and disc him. He can just see it. :/
Case notes: nothing but the incident log.
Follow-up: none
Severe energy depletion and surface damage after rerezzing (Radia)
(Still working on thread.)
Complications: ISO codes.
Case notes: a ton of data on ISO codes.
Follow-up: none.
Lacerated armor, mildly impacted code, disassociative strain leading to a limp (spybot!Ram)
The usual scanning, writing repairs into a code template, inserting into disc, resyncing.
Complications: none
Case notes: nothing but the incident log.
Follow-up: none
Memory integration seizures due to torture in previous life; facial injury due to fall (Lizor)
Preparations: Cooling blanket for seizure-related overheating; scans to create a code template and isolate the damage; standard repair for facial injury done directly over the disc.
Procedure: lacking permissions to repair traumatized memory files, so couldn't repair shattered memory links directly (a User could do it, but that was up to the patient), but "built up an immunity" so that memories could continue to be reintegrated at the patient's pace without the painful seizures (thread not complete).
Complications: Patient's code linked and intermingled with ISO counterpart.
Case notes: due to patient's initial distrust, only Wulf's own memories, dumped and catalogued upon return to the clinic, of the procedure and the intricacies of the merged code (saved in case of future complications).
Follow-up: visited to check on repairs, though thread is incomplete.
Burns, lacerations, torn circuits, disc cuts, embedded Abraxas-viral shards (Anon)
Preparations: Quarantined program and put a barrier around shedded virally-burned voxels; thick flat patch (slow energy-infusion poultice) on a main circuit to counter severe energy depletion; comprehensive scans (handheld and large hanging scanners); code needles to cut off pain impulses for major injuries and while extracting viral shards; energy patches over the burns.
Procedure: Removed viral shards, cleaned and patched wounds, ran new scans to extract a template to fix and recompile the code; loaded onto disc and resynced. Thread not finished, but probably kept Anon overnight for the repairs to settle.
Complications:
Case notes: retained viral shards, which proved non-infectious; notes on Anon's resistance to actual viral corruption, as opposed to the simpler non-infectious burns.
Follow-up: none.
Abraxas-virus infection and viral burns (Kade)
Applied patches for energy transfusion. Isolated virus to prevent its spread; inserted corrections into the scanned code, feeding parts of it at intervals into patient's disc; then wrote in repairs for the burns, while orderlies stood by to clean wounds as they closed. Patient, in shutdown, processed repairs and was released when he woke.
Complications: patient was a 2001-era modern import; made the case more complicated.
Case notes: details of Kade's modern configuration.
Follow-up: none.
Multiple contusions, one leg nearly shattered, code degradation from exposure to the Sea (Krypton)
Built, from multiple scans, a template file with which to stabilize patient for transport (tricky enough that Wulf's hands were shaking when he finished). Uploaded to disc and resynced. Patched leg further upon arrival at the tank (and decontaminated patient's Basic partner, who'd touched the Sea). Transported to clinic for further repairs (HUGE amount of information to process); put patient on a timed recharge to let recovery take hold; released him to go home when he woke.
Complications: ISO code riddled with wrenching stress fractures due to extreme sensitivity to the Sea's virus; preliminary repairs done without access to patient's prior records.
Case notes:
Follow-up:
Injuries and glitches related to stolen disc (Echo; not threaded out)
Patient lost large chunks of memory and was on her way to being a stray. New disc was synced in time to preserve most of her identity, but some could not be retrieved.
Complications:
Case notes: nothing but the incident log.
Follow-up: stupid beta newbie recompilers chased her out before she was ready to leave the clinic. >.<
Common form of lingering, escalating glitch in air-circulator containment protocols, aftermath of a virus which had laid him flat for several centicycles (tended by User:Gibbs), causing an incessant hacking cough. (Kip)
Suppressants had been prescribed (medic:Kato) but patient, an import, resisted getting his definitions updated because disc repair "felt weird", leading to the glitch escalating over time.
Tailored standard broad-spectrum antiviral definitions to address his problem.
Complications:
Case notes:
Follow-up:
Injury ()
Complications:
Case notes: incident log and....?
Follow-up:
