mNo edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
}} | }} | ||
'''Debuggers''' are [[protector]]s that make sure the [[system]] does not slip back into old patterns of abuse (or rather, being abused). They | '''Debuggers''' are [[protector]]s that make sure the [[system]] does not slip back into old patterns of abuse (or rather, being abused). They work with [[headmates]] such as [[Instructed-Persecutor]]s, [[Double Agent]]s and [[Structural Dissociation|fawn response holders]]. | ||
Debuggers may have or gain some control over their [[system]] in order to overwrite another [[headmate]]s [[trigger|triggered response]] or [[script]]. | Debuggers may have or gain some control over their [[system]] in order to overwrite another [[headmate]]'s [[trigger|triggered response]] or [[script]]. | ||
=Related Terms= | =Related Terms= | ||
Revision as of 01:25, 25 July 2022
 | This article contains sensitive or potentially triggering content regarding abuse. Please take care when reading if you are sensitive to such content. |
| debugger ( n.) | |
|---|---|
| Applies to | headmates |
| Coiner | Flexacone Pack |
Debuggers are protectors that make sure the system does not slip back into old patterns of abuse (or rather, being abused). They work with headmates such as Instructed-Persecutors, Double Agents and fawn response holders. Debuggers may have or gain some control over their system in order to overwrite another headmate's triggered response or script.
Related Terms
Debuggers may be necessary to balance enforcers and similar headmates as well as making a system less vulnerable to abuse.
Programming is (inversely) associated with this role.
