I mean fair point but there's literally a missing comma in the removal mod that breaks it...

@spudozaurus it's not design on the part of the mod maker, the code used in game for roaming bosses is that made to begin with. The reason the mods are hard to remove is because the roaming boss (whoever it is) is likely referenced in next weeks quest because it's present in the lobby save data, but if you remove the boss then it causes a vacuum in the save data reference and stops loading. The only method of removing such bosses without a removal mod is to have the roaming boss not always present in the base mod (say, every other week instead of every week) that way it can be removed in between weeks. In terms of design around that issue, you can have the roaming boss not be an actual roaming boss like the Thing, and instead act as a special condition mesh (like the collector on high inventory, the priest on CC hero, or the shambler in low light), or have it be tied to a specific curio or mission (like the corvian's nest, or the shamber's altar).

It's a bit annoying to install a mod that's pretty intrusive (eg the Roaming Raiju is around every single week), then find out the way to delete it that's already complex doesn't even work. Please try to not design mods like you would design malware lol

instructions are either incorrect or misleading. finishing a quest with this mod active didn't do anything, the raiju was still roaming.
what I found did work though is going to a quest that isn't haunted by lobster fanatics, exiting to the menu while still in the mission, disabling this mod and then completing the mission. (I assume retreating wouldn't work because that doesn't refresh quest generation but idk)

Np brother thanks for fixing it!

FIX FOR THE JSON FAILED TO PARSE ERROR:
* Add a comma to the end of line 37 in this file: "..\Steam\steamapps\workshop\content\262060\2238054087\loot\chape_SI_export.loot.json"

Thank you.

The previous error still exists. The issue is allegedly in chape_SI_export.loot.json according to my crash message which is shorter.

Checking it myself I can't see any issue with it, but I'm also not an experienced modder.

@Shaokere I'll look into it but can't promisse anything

Whenever I try to use this, I get this error: https://i.imgur.com/PDBLQ0w.png

Since no one else seems to have a problem with this mod I assume it's something on my end, but I don't suppose you have any idea what might be causing it?

(And no, I can't figure out how to get my screen to not cut off that message unfortunately. Changing the resolution doesn't help)

Truly a bruh moment