Noticed that the mech gestater stays in standby even when gestating.

What version of the mod are you using? It logs the version number when the game starts

It's more a question for other users of the mod than for the author - this mod causes a lot of errors with the hygiene mod and gives out fog all over the map except for a small diamond in the middle. does anyone have a similar error?

May I ask support for Electric Alloying Furnace from Expanded Materials - Metals , or should it be always on?

rimpy claims hugslibs dependency but it hasnt updated yet. ignore?

You can check the log when you first start the game; I print the mod version there for this reason.

The latest version is 2025.7.9.20, if you have 2025.6.X.X then you have the old version and you can unsub/resub the mod to force Steam to update it

It's possible, but it's not possible to easily tell with Steam's jank workshop content delivery. I'll try again later.

Are you on an old version of the mod? That issue sounds like the one fixed in the latest update a couple days ago

Mod is currently nonfunctional with Odyssey, maps start with a rhombus of visible space and anything outside of it cannot be interacted with and it cannot be uncovered.

@The Flesh this mod does turn off workbenches when not in use.

@_baseplate HugsLib is not listed as a dependency for this mod. You do not need it

Is Huglibs actually needed as a dependency for this mod? If not, could you please remove the need to have it alongside this mod?

anybody know a similar mod but for workbenches? basically turn off work bench if they dont work on it

Love this mod! Currently though it makes my game start with a diamond of visible space, the rest is like a cloud of war that doesn't go away. Tried to re-sub and its not fixing it. Hope this feedback helps. Will wait it out for a fix.

Had to un-sub. restart the game. then re-sub. make sure the mod deletes itself from pc. fixed the game crashes for me. Took forever to find this mod was the guilty one :) Thanks for the mod!

it works after resub the mod

Lk:
While RimWorld is closed, unsubscribe from this mod, wait about 30 seconds, then subscribe again. This will apply the latest patch and should work fine.

However, it really does work:

Lk:
While RimWorld is closed, unsubscribe from this mod, wait about 30 seconds, then subscribe again. This will apply the latest patch and should work fine.

This mod generates a lot of errors and creates fog of war on the map that can't be removed.
Here is an example of errors:

https://ibb.co/33DvT9H

Exception printing AncientExostriderLeg46322 at (112, 0, 145): System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
[Ref E09E0495] Duplicate stacktrace, see ref for original
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Error (string)
Verse.SectionLayer_ThingsGeneral:TakePrintFrom (Verse.Thing)
Verse.SectionLayer_Things:Regenerate ()
Verse.Section:RegenerateAllLayers ()
Verse.MapDrawer:RegenerateEverythingNow ()
Verse.Map:<FinalizeInit>b__198_0 ()
Verse.LongEventHandler:ExecuteToExecuteWhenFinished ()
Verse.LongEventHandler:UpdateCurrentAsynchronousEvent ()
Verse.LongEventHandler:LongEventsUpdate (bool&)
Verse.Root:Update ()
Verse.Root_Play:Update ()

currently broken. it create fog of war bug and color glitch on old save

Holy cow took me FOREVER to find the fog of war glitch was from this mod. Not sure if its my end or the mod itself since I have about 160 loaded as well. Very weird because this mod was working perfectly for days.

had no idea this was causing the fog of war error

Working perfectly, thank you for this lovely mod.

While RimWorld is closed, unsubscribe from this mod, wait about 30 seconds, then subscribe again. This will apply the latest patch and should work fine.

Thanks for providing such a great mod!

Did you confirm you have the new update? Check the version in the log when you launch the game

Nah man, still broken, my game looks like a LSD trip

Everything looks fine now, thank you!!

Just pushed an update, I think everything should be working now. Let me know if you see anything else.

Reporting the same issues as others, error log spam and weird fog of war behavior

major graphical errors leading to unplayable saves, everything became black or a mix of blue and red with lots of artefacts overlapping, this was not able to be fixed with uninstalling the mod and errors were permanent on my world no matter I tried.

Me same as everyone else. Hall of mirrors, but only after saving and reloading a game with the mod installed. It worked fine (and works fine) on new maps, but after a reload it craps out. Hopefully fixed soon, as I'll miss all the blinking rooms letting me see the busy nature of my colony. Love the mod!

Also having the inexplicable fog of war that never clears! Occurs even when it's the only mod on the list apart from Harmony

I also have that error where the fog doesn't unfog properly and logs are spammed with out of range exceptions. Tried it with only LightsOut and Harmony (and DLC) and still got the error.

I have the same problem as Mrmarko123 and Vapor.

Same here, this seems to cause some major visual errors on the maps

after some trial and error during the latest 1.6 Rimworld update, I found that this mod is causing an error spam in the debug console:

Root level exception in Update(): System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

Causes the entire map to be black and have a source engine void-like bleeding effect as well. These effects only went away when disabling LightsOut

And then it randomly works right after typing that. I am lost, but hey it's working now.

Don't know why, but the mod started not working all the way. The light will turn off for sleeping, but nothing else. If I toggle the keep on button, they all turn back off but just get left on again next time a pawn goes in. Not sure what might be messing with it.

Ok. Thx!

Those are there to help when troubleshooting issues. They log once when the game initially loads and shouldn’t be too bothersome (they also don’t cause the log to appear on startup, they’re silent — if the log is appearing on startup then you have a mod logging red text that you should investigate).

If you wish to get rid of them you can remove the “mods” word from the mod options. They’re on by default to make logs more helpful and you may want to leave them on for that reason

<color=orange>[LightsOut - Debug]</color> should Modded Glowers specify a target mod?
<color=orange>[LightsOut - Debug]</color> applying mod compatibility patch: Modded Glowers
<color=orange>[LightsOut - Debug]</color> component applied: Patch ShouldBeLitNow for modded glowers
<color=orange>[LightsOut - Debug]</color> patching "PipeSystem - CompGlowerOnProcess" to count as a glower
....

There already is an option for that. What logs are you seeing?

Could you provide an option to disable debug logs?

Haven't had any trouble on my 20 hours of 1.6 with the mod

I mean 1.6 should be supported already. Let me know if there are issues, but it looked fine to me.

1.6!!!!!!!!!

1.6?

This mod needs an update for the Vanilla Furniture Expanded - Spacer Module. Currently doesn't affect the furniture there

You need to confirm you have the updated version of the mod.

Still having issues with it locking the Architect menu up

It's working properly now. Glad I could help with the fix.

Works now.