All-Purpose Glitch Report Thread

[bustedcasuality]

I can't believe I didn't think of this before. Right, the idea is this is "junk drawer" or "slush pile" of known glitches. Since Sburb has more bugs than your average swamp, I thought it would be a good idea to collect all those odd little glitches that get mentioned in passing, or are scattered among various subject-specific guides. Anyway, if you run into a glitch, you can report it here. Here's the format.

[Glitch Name]

The name of the particular glitch, obviously.

Description: Describe the glitch. This can be an abstract description, an personal anecdote, or both.
Make sure your description is enough to differentiate the Glitch from glitches with similar causes or effects.

Handling the Glitch: Here, you explain how to end, circumvent, and/or exploit the effects of the glitch. Make sure to take note of any dangers involved in this.

Addendum 1,2,3, etc.: Anything important that you forgot to mention when earlier goes in an addendum, along with anything that doesn't quite fit.

[Non-Player Uncertainty Bug]

Description: A rarely-seen glitch associated with the Doubt Aspect, which governs uncertainty. It messes with the Game's ability to determine whether non-players who enter the medium are timeline-Doomed are not. As a result, the game won't try and kill them off. Generally, if a non-player doesn't need constant babysitting and you've got a Doubt player in your session, this is likely what's happening. This glitch can be very good for the mental health of First-Time players. I've personally seen this glitch twice; once with a single person (a troll's buddy), and once in my first session, where the non-players outnumbered players something like 4-to-1. In the former, the non-player was lowly abstracted. In the latter, the non-players were mostly highly abstracted.

Handling the Glitch: Non-players typically don't have an echladder, health vial, or a strife specibus. On one hand, this makes them fragile. If you have firearms (such as hunting rifles, pistols, submachine guns, assault rifles, etc,) give them to the non-player; because they're not subject to the nerfing effect of Strife Sbecibi, firearms are typically more dangerous in the hands of non-players. If this isn't the case, non-players can be great for coordination, mission control, organization, and research. If you can pull it off.
Another issue is that non-players can have a variable level of game-abstraction, which changes how they interact with the game.
Low-Abstraction Players typically tougher to handle. They can trigger dangerous bugs if they try and interact with game abstractions like portals, consorts, carapaces, etc. Don't give them alchemized weapons. On the other hand, they can blithly ignore some harmful game abstractions (such as some poison gas or "energy" effects) and they can sometimes slip into restricted areas because of the way the game's ability to tag them is bugged. Because they often lack stats, they can have secondary bugs typically associated with Void (or in some cases, Saccharine Dopplegangers). The best place for them is an empty ruin or dungeon. If you're flow, freeze all the enemies in an area, and use it as a "safe place" where your buddy can hang out unmmoletsted. Don't bring them to the dream moon or a consort village; they fuck things up there like you wouldn't believe. They're role is limited strictly to coordination, planning, web-searching, and data analysis.
Highly abstracted non-players are easier to handle, since they can wield alchemized weapons and are highly unlikely to cause secondary glitches through interacting with other game. They can also use alchemical items, and can grind the Item-Mastery, so give them an item with a good attack ability. If you can get them on the Dream Moons, you can keep them both fairly safe and have them handle any Dream-Moon business that's not exactly a quest. They're exceptionally good for babysitting players who haven't woken up yet, or whose sleep ratio is low enough that they're crazy loopy when dreaming.

[draconicKey]

[Role-Invertion Bug]

Description:So,,, This happened on my first playthrough. astonishingly enough, We of course didnt know what we were supposed to do. but i still cant believe how our soon-to-be waste of doom actually thought about pouring both poison and blood into the kernelsprite before entering to the medium, Wow, Just wow, It caused a huge. session-wide glitch that inverted our roles to fit our personalities, It only changed us however, We were permanently locked out of dungeons. god-tiering and anything that checks for our role, Which is to say. pretty much all the game, Except fraymotifs, Fraymotifs changed to suit our roles, Luckily. the roleplaying system does change with the role, I wouldnt be able to tell this to you if it didnt, When i learned about how sburb treats its players. i decided to search for the triggers. which have been spoiled above, In my second session. i pre-entry double-prototyped a bit of water and some earth. and the effect. though now applied to the original player of the session. is the same, Luckily those sprites are gamebreakingly overpowered. while the prototypes are really weak, That part of the glitch also contributed to my survival,
Handling the glitch:I,,, Dont have the slightest idea what use could this glitch have to somebody after their first session, I mean, in the first session, you only have to roleplay what you want to. and thats cool. but afterwards. its exactly the same except that you have a lot less features. you have no quests. you have to grind a lot for fraymotifs. you have overpowered sprites that wont leave and the reckoning will probably start prematurely,

[iD/sR/sT]

The Alchemonster Bug

Description Turns out Sburb doesn't like you abusing free stuff One of our players forgot about their client before their client got to the first gate They then panicked and put down a lot of alchemiters The alchemiters merged into a huge monster that regenerated and caused huge problems

Handling the Glitch Just beat it up and dont give it a chance to regen We managed to cut it in half

[horrorTerror]

[Post-Corruption Irrational Fear Glitch]

Description: So, you've got corruption problems, and by some miracle you got cured. Say, I (a horrorterror) licked you repeatedly and you didn't clean off the ichor for days and then you alchemized a ton of corrupt items and ate them whole. Then when you were grimdark and babbling in broodfester, one of your coplayers with sanity kicks you in the gut, you barf out the corrupt stuff, then they spray you with a hose and a tank full of high-pressure purifying fluid, then hug the corruption out of you. However, every non-player abstraction thinks you are still a scary corrupted monster boo spooky scary gamebreaking. Or perhaps you went to the Underworld and started hugging random angels until you wanted to save everyone by killing them and your shiny almost completely ceased to exist. Then you got FALCON DROPKICKED!!!, drowned in psybuffs, and hugged repeatedly, and a Heart player replaced the missing biological functions parts of your shiny to make you not a vegetable when you got torn from the hivemind of the angels, and added a part that makes you have some semblance of a personality resembling who you used to be, on top of making you act like whatever X of Y you were assigned to make the game easy for you until you make it to the door and your soul shall be healed. Yet everyconsort and everycarapace etc. etc. is still like WHY ARE YOU SCREAMING AT US AAAAAAAAAA WE'RE SCREAMING BACK TOO YAY WHY ARE WE SCREAMING TOGETHER? and you're not screaming. No matter how much you don't even have mild personality changes and can recognize corruption as a legitimate threat (read: you are totally purified because your coplayers saturated you back up with good old player sanity purity whateverthehellitisSburbwantstokillyoufor) yadda yadda you're clean. And the game is still utterly horrified at you and may or may not still break at your touch despite the lack of eldritch or angelic ichor seeping from your pores. Also, the Queens may or may not attempt to throw you in the vault and erase you from existence on sight.

tl:dr you're not corrupted anymore but game people still think you are. Formally, this glitch is a result of retaining the stat that indicates you are corrupt....despite not being corrupt anymore.

Its value spectrum always varies by session due to metahereditary anti-corruption measures that still fail, but it will be in whatever spot indicates you have no corruption and for the most part the player can usually 'safely' interact with abstractions that would not care about you being a corrupt babbling monster or have separate methods of discerning players from standard game detection tactics, like Denizens (they can see through Mist shapeshifting and that fools underlying game scripting for Jenna's sake), or Jack Noir (He has a very special script to help him stab people more that allows him to identify people and determine how when (not if) and how much they should be stabbed, very script heavy smartcarapace). Normally, this is a result of getting rid of corruption by non-mentally-healthy methods (like exposing them to a source of the opposite type of corruption, or attempting to drown them in a bathtub because you were trying to murder them but the water was replaced by liquid purity somehow in an unrelated shenanigan), or if the session has incomplete overcorruption attacks and death doesn't fix corruption except when it does because this game is so buggy even eldritch hijacking can't fix it.

Handling the Glitch: You should get a Vo d player (or Mist displacement or general Mist fogging) to erase that stat entirely. Failing that, have everyone else on standby to hug the shit out of you, then get corrupted then get cleaned again (use the opposite corruption type if doing the same type doesn't work or is why it's not working). Finding an instance of the Weird Bug used to cure Rangoon and eating it is also an alternative, as it gets rid of corrupting influences in general and seems to ironically debug certain other problems as well.

Addenum 1: Kissing a frog has worked apocryphally but a Prince of Rain was involved then the frog turned into one of the Prince's dupliclones who spat out the original frog and nobody knows how the hell or why that worked and chalked it up to Rain being Rain.

Addenum 2: In general, if your Whisperings suddenly decide they know how to make you 'clean up yourself' in the words of the Voices and then promptly drag you on an aspect quest, do that quest even more than you already really should do aspect quests. This generally consists of going to a Skaian Summoning and then getting a mouthful of aspect-mutated Weird Bug all over your face or doing really weird things that your aspect quirkily insists upon, but it does tend to inexplicably destroy the problem stat.

[horrorTerror]

[Dancing Lich Queen Bug]

Description: Sometimes a Lich Queen gets horribly confused and starts tap dancing and firing off abilities randomly at things that aren't necessarily you. They are also displaying the flashstepping motion blur effect. This is usually caused for the same reason as spinning consorts: Land gen put something down (another underling most likely) where they were going to move to and their pathfinding AI broke. It can happen with other underlings but Lich Queens are more prone to it. The hitbox of the lich queen herself is not always where she is standing due to failed relocation attempts failing again.

Handling the Glitch: For the sake of grist and not getting randomly shot, just start waving around your weapon wildly in her general area until you collide with her actual hitbox, then kill her off.

Addenum 1: If your prototypings or a quest gives a Lich Queen dialog options, it is possible to reset their pathfinding AI manually by trying to talk to them, just like consorts. Unless you plan to go all Captcha Cardmonsters and make them an ally IMMEDIATELY, that's usually not a good idea because you are now standing in front of a Lich Queen in full command of her faculties.

[Material Conflict Bug]

Description: Whenever you find a certain material type for enemy-making on a Land, there are always very few underlings (who have specific prototypings to promote survivability or lack specific prototypings related to material choice or self-destruct abilities) and a lot of grist lying around, mostly of two material types that would not drop together from an enemy with decent material type choice. Technically, this bug occurs when either the prototyping data conflicts with the established spawn material or the underling spawned on two neighboring material types, however it happens they do not meld well and Sburb cannot figure out how to make the Underling without it self-destructing on spawn, but it makes the self-destructing imp or whatever anyways. It is easily induced by prototyping a material that Sburb uses in underling construction that would conflict with others, such as ice on hot worlds, though the 772 Materials may have been expanded on in the last few mutations and hotfix patches. The land may be damaged and regenerating whenever it is near this material type even if none of the underlings are intentionally attacking the land if the nature of the design conflict is literally explosive in results (chemical reaction imps or explosive imps are often nasty little suicide bombers in your dwelling spire, and if a giclops or something blows up you risk toppling if you're not out of Land gravity yet).

Handling the Glitch: Collect the grist. Enjoy relative sparsity of enemies, though be wary of explosions.

[Reality Is Jpeg Artifacts Glitch]

Description: You prototyped one of your friends' stupid poorly-drawn badly-spelled jpeg-artifact-covered shitty comics, didn't you. Or you flooded the session with artifact-grist items and their reality-distortions are composing the majority of the session. At any rate, the entire session is now covered in shitty jpeg artifacts, and now Sburb thinks you must pay. Basically, reality's top-level optimization codes are suppressed by jpeg artifacts' tendency to disobey the laws of abstraction, then are replaced with a half-written drunkenly-made emergency backup to spread terrible memes. Certain memes may cause this if they are infectious to spacetime but only if they encounter jpeg artifacts to assimilate or coincidentally attack the underlying coding sources (possibly by interfering with the Skaian Shiny). Roughly, you can tell that this is going to be a problem if you cannot look up into the general incipisphere without seeing jpeg artifacts, or Skaia has become artifacted, or over roughly half the incipisphere is generally jpeg artifacts instead of standard Sburb abstractions. It was originally supposed to be some form of 'quest' judging by the commented out drunken love letter poetry jammed in between lines, but was clearly scrapped improperly if and when whatever created it sobered up.

All aspects will royally flip the fuck out about this, but Ploy, Flux, Rage, Heart, Mind, Stage, Space (though they are particularly *itchy* about it and the World may do seemingly random things in her quest to "FIX THIS"), Law, Dreams, sometimes Breath and in rare cases Time in that approximate order from most to least will take it way harder/weirder than anybody else. Rain will staunchly polarize into the Voices who vaguely support the change and the Voices who absolutely hate it, with very few neutral opinions making their way to the now-double-shattered mind of a Rain player, while Mist will devolve into gibbering insanity that sounds more like the Voices are cannibalizing the Strife while everyone is on fire and the Faith is in the background taking pictures like a voyeuristic cameraman. Void is virtually a 50-50 flip, being either totally immune or the source of the problem, almost never anything in the middle (The Null never has an opinion, as usual).

A game effect/disease/THING vaguely similar to the hatebaby of DERP and Octoroon Rangoon will start messing around with everybody and everything's spelling, thoughts, actions, and then start distorting spacetime around them, making everything feel just like the terrible comics from whence it originates. Players of the aspects that are taking it harder or general scrying classes will say that whenever the problem approaches that the 'art style' of reality itself shifts to something resembling what it would be like to live in those terrible comics.

Dealing with the Glitch: Immediately get rid of as many jpeg artifacts as possible to stop them from suppressing normal reality. Throw them into the Furthest Ring if you can, or destroy them entirely. Whisperings of aspects that disapprove of jpeg artifacts doing may create concentrated pulses of stabilizing energies to give you moments of sobriety as opposed to acting like a passive stabilizer during other optimization code breaches (i.e. causality errors, doomed timeline cohesive separation failures) or personally start blowing them up with random aspect blasts near their Skaian Summonings, aspect-charged items, or other heavy shenanigans like players. Like with other times reality begins to bug out a little, Space, Time, and Rage can force the session back into line, Flux, Ploy, and Law can provide sanity-bolstering restrictions and stable meta-archetypes to cling onto, and Mist/Heart/Rage/sometimes Law/Space/situationally Void but mostly with displacement classes/players who hack Sburb/etc. can be used to repair the overarching coding so it will stop running the jpeg artifact scripts. Once you are below the half-incipisphere-is-jpeg-artifacts level or Skaia is not pixellated anymore or the majority of the incipisphere is mostly clear of jpeg artifacts or every single thing with that jpeg artifact prototyping is dead, the problem glitch should stop manifesting or at least be vastly reduced. It is possible to complete the session normally with this glitch being not dealt with, but why would you want to do something like that to that poor genesis frog?

If the cause of the glitch was prototyping, your best bet is to get your Denizen finished or make a Deal with them to ban the spawning of that particular underling type before they go completely bonkers from constant exposure, and then speedrun the session, or be willing to spend the next few months/years as a poorly-drawn DERP-infected drowning-in-rangoon aspect-going-WTF mockery of yourself.

[Weapon-Object Duality Glitch]

Description: Whenever you try to use a particular innocuous object/deadly weapon, it randomly turns into a deadly weapon/innocuous object! Keys turn into guns, guns turn into keys, what is going on!? This glitch, *PROBABLY*. A slightly different version of this glitch occurs with Makeupkind, as anyone with a lipstick/chainsaw can attest. Death's Scythe intentionally exploits this to be all the weapons all of them and the Midnight Crew Deck does this to turn into different items as hotcarded, though they use different methods.

Besides those exceptions, the standard cause of Weapon-Object Duality is having an excessive number of captchalogue codes. Meaning you or some other factor (utterly excessive levels of incestuous frog overlap or massive alchemy sprees from a Smith with a ton of supplies, a penchant for Rain's captchalogue rule violations, and an Intellibeam Laserstation tend to be at fault first, and time shenanigans soon after that) has filled all 281,474,976,710,656 default captchalogue codes with an item from the game's perspective, and the create-object-for-abnormal-combination scripts have not turned off and nobody is using an alchemiter alternative (troll production synthesizer, 'alchmy thang', cookchemiter, saccharinized-[Psychogenesis], etc.) for additional options. The real cause of this bug is Sburb trying to make amends with the excessive number of captcha codes by stacking them on top of each other, causing the game to get confused when the item is referenced. Because of a quirk in the expendable-code-determination algorithm, weapons are paired with regular objects and regular objects are paired with weapons for the vast majority of the time. Non-player game abstractions will treat the item as whichever one is presently visible is the only one it ever was, meaning that if you talk about this key and it turns into a gun for some reason the consort right there will say "what key? you're not holding a key" and it will probably turn back into a key when you look back at it and you flip it back into a gun and call it a gun it becomes a key again and they're like "what gun I've never seen you with a gun" despite the fact they just saw the gun right freaking there rinse and repeat until the narrative complies. It is slightly more stable inside your inventory (especially if the weapon-form is sitting in your strife specibus) due to the lack of meta-referencing on most stored objects, and even when taken out if it's critically plot-relevant the latent Flux and Ploy beneath all sburban narrativium will come to your aid and bitchslap the game into complying most of the time. If the item you are weaponizing gets stuck in harmless object mode (either form you attack with turns into/stays the harmless one) and the plot won't help you, you're kind of screwed and will probably die shortly. Trade out for a glitch-free or mostly-weapon object if possible.

Dealing with the Glitch: Avoid objects/weapons that have become double-formed. Change to a weapon that does not suffer from this effect or if it does favors the weapon-form over the item-form. Try to find an alternative to standard alchemy for procuring items you didn't alchemize before.

[horrorTerror]

[Improper Captchalogue Code Bug]

Description: This glitch is what usually suppresses the excesses of the Weapon-Object Duality Glitch in particularly long or 'creative' sessions. Captchalogue codes start including abnormal symbols outside their usual alphanumeric-and-friends selection, such as letters in other languages, emojis, Sburban code-c0da imagery, corruption-esque zalgotext, font changes, unicode symbols not normally used in captchalogue card codes, or random pictures. The main way to cause this glitch is to use an alternative item creation system (especially one which is a viable alternative to alchemy as far as creating new things) to excessive or highly abnormal levels (i.e. use an 'alchmy thang' and then continuously and irresponsibly go full Smith-of-Rain tier bonkers with creative power and violate the laws of reason until you have a card which has holes leading to the Magicant or floating bits of card outside of the card proper), thus forcing Sburb to use its alternative system to captchalogue code generation immediately as the item you created cannot be logically assigned a physically possible captchalogue code yet it has to have one because you made it despite that being by dodging the physicsset code. It's hard to explain.

Handling the Glitch: You don't honestly have to unless alchemizing something with a bugged code is vital and you have to punch the holes in with traditional equipment. If you have to, have a Heart player mod the appropriate characters into the alchemy machinery shiny or have a reality hacker matrix it in. WORD OF WARNING HOWEVER quests which rely on captchalogue codes being in the normal spectrum for math puzzles or some other BS will fail or forcefully do something else. At least once I have seen the offending puzzle violently explode, though whether this solves it depends on whether or not Sburb wanted it to fail somehow. We're not exactly sure either.

[ Ragey McRagelanth ]

Description: A rare bug that happens when a crystalanth, almost invariably in a Skaian Summoning of Rage, bugs out and gets an inappropriate Rage charge somehow, but doesn't explode immediately somehow because the error in order reception doesn't occur right away because the inappropriately applied Rage charge doesn't do anything all ordery in the wrong place. This can also be caused by having a Life player spawn a crystalanth in a Skaian Summoning of Rage, especially if it's without permission (since having a free healing crystal in the nice place gives the player more incentive to come back sometime so Rage usually objects more quietly if at all).

The explosiveness of the so affected crystalanth varies wildly, from exploding when touched, exploding when activation is attempted via Song of Life, providing pluck restoration instead of health vial restoration (), exploding when looked at, exploding when reloaded into activefocus via a player returning after having left it well enough alone for a while, exploding randomly a long time later (possibly caused by a delay in triggering the errors resulting in explosion meta-level script lag from large amounts of prophecy abilities, location reloading, and/or generally processing-intense scripts like generating a long slew of complex new seemingly random items at the same time), exploding when a quest relevant to the main plot of its host Land is sufficiently progressed or completed and something is terraformed, exploding when a different Song of Life is played, exploding when the correct Song of Life is played but it's played wrong and would normally just fail, exploding when player commands at all are used nearby, exploding when a session-altering event goes down (i.e. a cataclysm, the Reckoning, player ascension/permadeath), exploding when the Denizen shows up just to mess with everybody, exploding if it would make someone nearby cry (what is wrong with you Sburb), exploding for any number of other reasons, and finally firing deathrays when their light is drawn out by [Flare] from Light players as would be expected before most likely also exploding because order did not expect the [Flare] glitch either.

Handling the Glitch: Stay out of crystalanth explosion range as possible and hope that when it detonates it does not do so problematically. If necessary or expedient, set off an update flag by throwing a rock at it from a safe distance away when nothing that won't be covered by verdancy regeneration (i.e. consorts with specific important roles) is in explosion range to try and set it off so it won't be a problem again later.

[ Underlings Appear Visibly Bug ]

Description: This bug causes the not-visible requirement of underling spawns to fail, though usually only for one player as the others will be fine and have normal field-of-vision effects. This has the effect of underlings simply popping into existence in front of or otherwise uncomfortably near you instead of their usual behind-corners-or-scenery shtick, which can be a problem. The usual cause is something causing an abnormal field of blindness or overvision or a spawnrate dilation and that being removed abnormally, such as a Seer using an omnidirectional sense ability to override their predisposition to blindness, a Space player looking at the entire session at once via Spacey means, and then that ability being interrupted. Alternative causes include broken blinding effects, manipulation of spawnrates to such an extent they simply cannot be jammed into spaces they can't see and then not stopping with the more and more, etc.

Dealing with the Glitch: Get the effect fixed, by having the effect start up again and expire or be cancelled normally, removing the nonfunctional blindness effect, or stopping the excessive manipulation of spawnrates.

[ Whoops, All Berries ]

Description: This bug causes a consort village with a fruit farm to be full of berry bushes clogging up the place for no discernible reason. The berries are usually a fruit type normally found on the land and count as regular verdancy for the purposes of being regenerated on removal. The specific reason is that a variable in land generation tries to plop down a fruit farm on top of a previously planned/extant fruit farm and it kind of bleeds into the rest of the settlement and the berry bush model locally stacks onto a normal tile subtype choice texturomateria model, resulting in overplacement of berry bushes when they get genned with the rest of the tile. Oopsie. The berry bush models are more prone to this than larger fruit trees' models due to a combination of name shenanigan, size, and a mis-pathing error with the berry-bush-extends-onto-tile models.

Dealing with the Glitch: Assuming the berries are edible and nonharmful to your species, enjoy the excessive free fruit as the bushes not part of the fruit farm area proper don't count as owned for purposes of taking so you don't have to get it cleared with the owner first. If they aren't edible or are harmful, then don't eat them. Relatively simple.

[Player Modeling Consorts]

Description: For whatever reason, the scripts that handle cross-session referential procedures (usually tied somewhere in the mythology/zodiac/inheritance/packet delivery/metacule/creation management/lore management/etc. script series) bug out every now and then on reception of interfrog referential plot design hivedata (what exactly this is used for when it's NOT bugged we are still investigating, but appears to be partially tied to pacifying the aspects of Flux, Stage, and Ploy with narrative references and tropes only the Audience will understand) and consorts will cosplay as players from a wildly unrelated session, spouting their classic  lines and mimicking their great actions like some sort of trashy memetic plague.

Dealing with the Glitch: Do not aggro the consorts, as besides all the normal reasons you should not attack consorts a wide selection of them randomly hold mythological role powers assigned to the current and past versions of the player they're cosplaying as (indicated by what specific outfit they are in). It appears to be some form of bugged event and will usually show up and go away on its own rhyme and reason that we cannot comprehend without a severe analysis of the relevant scripts.

[ Wacky Whacky Queens ]

Description: A Queen or both Queens go insane, are aggro'd, and run around bonking or more seriously attacking people they do not like (usually the Dersite agents because of their propensity to be near and annoying to BQ or griefing Prospit) with random objects for often completely random reasons. They may or may not still be bound to their thrones, but in the event they are not (often because BQ [RED MILES]'d her throne in an attempt to kill CD, or WQ broke hers with a ceremonial sword when she tried to stab Jack Noir as revenge for his stabbing of her guards, or something normally excessive and out of character for them) they will usually wander their dream moon whacking those that displease them for whatever reason with whatever weapons and prototypings they have available. Provided sufficient mobility prototypings and their thrones have been removed from functional restraining bolt status, the queens may move to the Battlefield in pursuit of seeking their husbands' counsel on personal matters that sound like they came from the mouth of a Rain player on drugs, or to the Lands in pursuit of an Agent on a mission, and begin griefing accordingly. If the prototypings are not sufficiently overpowered or resistant to stabbing this glitch can rapidly result in noirjacking or others ringwraithing like crazy.

The specific cause of this glitch is usually a prototyping resulting in a personality trait that conflicts violently with the Queen's preset personality and even their prototyping acceptance training cannot make them acknowledge it properly or simply makes them not unequip their ring, or simply a prototyping causing extreme aggression and insanity. In some cases the Queens may realize their ring is the problem and disable and attempt to dispose of it resulting in a wraith problem when they fail due to being in a bad situation to get to the vault without interference to delete their ring, but in many cases prototyping acceptance training or a prototyping-related ring obsession will make them disregard the blatantly negative part of their new prototyping or try and fail to work around it.

An alternative cause may be psychologically traumatizing the royal in question (such as a particularly disastrous assassination attempt), attempting to ruin their day in a very special way (causing wide-scale destruction to their property or dream moon in general), or other issues on their ends such as going into full-blown session defense mode from dealing with large amounts of corrupted items in rapid succession.

Dealing with the Glitch: Try not to die. If you want a more active option and/or the queen(s) is (are) being proactive about killing you, your coplayers, or something important related to either of those, attempt to disable the queen(s) (destroying is a valid option for the Black Queen of Derse but whether that's possible when she's gone bonkers and probably is flinging around [RED MILES] is another matter entirely) and pilfer the ring(s) and dispose of it (them) quickly in appropriate fashion(s). 

[ Chunk Corruption ]

Description: There is/are glaring near-cubic missing section(s) of your incipisphere, usually empty, popping in and out of existence, composed entirely of a (usually purple) missing-item-identifier-abstractionmatter area, a giant Magicant entry, full of rapidly shifting colors and strings whipping about wildly, filled with furthest ring timey wimeyness, glitching, a fiery screaming hell full of angelic light, or any combinations of the above, and it's not shrinking. If you can see code, you may notice that one or more of the reality management scripts, usually a spatiotemporal stability generator or item creator type is having a seizure/missing/is not operational/has been disabled somehow/isn't running in a local area. The usual cause is that something either flat-out broke in your session with no internal interference (considering the high number of glitches Sburb exhibits in its spare time, if you have a heavily modded session this will only get more likely as you go) or someone is actively attempting to break your session through a session disc abstraction or localized spacetime damage. In the case of the former, once one shows up more follow.

Dealing with the Glitch: If it's popping in and out of existence, DO NOT GET ANYWHERE NEAR IT even more so if you're session-critical or don't want to get Scratch-tier annihilated. You risk you and your shiny getting error 404'd and severely damaging the session on the level of a small void catacylsm or an angelic infestation if you're not careful. Otherwise, if it displays characteristics of corruption, usual corruption disclaimers apply. It counts as a small bit of home territory for the side it represents and will be reclaimed/destroyed vehemently by the appropriate side(s) once the session barrier breaks down enough towards the end (or earlier if it's broken beforehand).  The giant magicant entryway and purple missing item are usually fine however unless your magicant contains something dangerous. The purple missing item usually has very high verdancy regeneration and can thus be mined out for infinite supplies of the appropriate color of lolwutty broke-material abstraction matter. The wholly empty locations are only noticeable if they're partially or wholly embedded in a larger session-relevant body. Try leaving the location and coming back later forcing it to reload in the activezone, which may cause a correction mechanism to trigger. If nothing happens, you can presumably guess it's going to stay that way and it can be exploited.

Addenum 1: If more chunk corruption happens over time, it is in your best interest to get you and your coplayers speedrunning before the session is unwinnable, unplayable, or just crashes completely.