Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I'm honoured.
Praise unto Randy
- transpiler net.pardeike.rimworld.mods.achtung:
- prefix net.pardeike.rimworld.mods.achtung:
- postfix net.pardeike.rimworld.mods.achtung:
- prefix OskarPotocki.VFECore:
- postfix net.pardeike.rimworld.mods.achtung:
- finalizer net.pardeike.rimworld.mods.achtung:
you have all of these things doing patches in the calling methods so it could be any of those or a combination, hence only happening to you
MiscRobotsPlusPlus.Patches.PatchShit: is a wonderful function name, and I'll use it in the future. But, more importantly, MiscRobots++ is interfering/having issues patching over Achtung and VE:Framework.
Never had your issue though, so could just as well be the cycle of the moon isn't right.
Edit: ninja'd be the one and only Dubwise. Listen to them instead.
whatever happened remains in effect and nothing seems able to remove the stuck bp.
Hey bud, I did figure out a way to remove it in the end sadly what I had to do
was uninstall rimefeller, load game and save it then reload rimefeller and rebuild everything
with dev mode.
I was concerned about this breaking my game completely but it worked perfectly, I'd just recommend taking some screen shots of the layout before hand if you have a complicated setup so you can see how you had things before.
Of course this may destroy your game and is kinda a pain to do but I can tell you it worked for me.
1. Open your save file in a text editor.
2. Find the problematic blueprint in your save file (I found mine by using ctrl-f to search for the coordinates that are printed as part of the error)
3. Delete it.
I can't think of any circumstance where it wouldn't successfully remove the blueprint, so this should solve the problem in all cases.
Edit: Its back, do dig in the files guys...
This works, you just open the save file in the options menu on the home screen, use control f to find the troublemaker and then delete it as Yakubian Supersoldier said