Troubleshooting

1. Check the folder depth. The game needs Mods\OptimizedLocalHousing\version-1.1\manifest.json. A doubled OptimizedLocalHousing\OptimizedLocalHousing folder is the usual mistake; see the folder layout.
2. Check the Mods folder. It must be the one your other mods are in, normally Documents\Timberborn\Mods.
3. Check the game version. The mod needs Timberborn 1.1 or newer.
4. Fully quit and restart the game.

1. Make sure you're reading the right session. The log is overwritten at each launch; the previous one is Player-prev.log.
2. Find the mod list near the top of the log. Optimized Local Housing (v1.2.0) should be in it. If it isn't, enable the mod and restart.
3. If it's listed but there's no loaded. line, look further down for an error loading the mod's DLL, and report it with that log.

1. Unpause and let the game run. A pass takes about 150 to 200 ticks on a colony of a few hundred beavers: roughly 90 seconds to two minutes at normal speed.
2. Don't quit too early. The line is written when the pass ends.
3. Wait for the next day on a save the mod has seen before. Only a save it hasn't seen starts a pass straight away.
4. Look for "Disabled because…" or "Pass abandoned…" in the log.

Disable the other housing mod in the Mods menu and restart. Two housing mods would keep undoing each other's moves. The message ends with the ID of the mod it found:

• BobHousingOptimize (Bobingabout's Housing Optimize)
• BobCommuteBalancer (Bobingabout's Commute Balancer)
• housingoptimize (a mod.io listing of Housing Optimize)

Reading the line: Pass 34: 345 adults, 104 homes, 167 workplaces; 5394 route queries over 183 ticks; 4 move cycles applied (1 rejected, 2 stale), 0 disconnected commutes repaired, route cost saved 717.

• adults / homes / workplaces: how many the pass considered.
• move cycles applied: groups of beavers who swapped beds. Zero is normal once the colony is as good as it can be.
• rejected: cycles the fresh route check threw away, because a beaver would lose its route to work or the cycle saved too little. The costs it found are remembered, so the same cycle isn't proposed every day.
• stale: cycles skipped because something changed during the pass: a beaver's home or job, a death, or a home that could no longer take them. Small numbers are normal; those beavers are reconsidered the next day.
• disconnected commutes repaired: beavers who couldn't reach work from their old home and can from the new one.
• route cost saved: how much shorter the movers' walks got in total. Repaired commutes aren't counted, since they had no route before.

Zeros on a colony that clearly needs help usually mean the beavers aren't eligible. They have no job, or their homes are paused, blocked or switched off by automation, and those are left alone by design.

• Beds are limited. The mod minimizes the total. Someone has to live farther away, and it may be the beaver you're watching.
• Route cost isn't distance. Stairs and ziplines can make a home that looks close costly, or a far one cheap.
• Commute means home to assigned workplace. Trips to haul goods or visit other buildings don't count.
• Timing. New jobs, new homes and births show up in the next pass.
• Breeding comes first. A move into a closer empty bed is skipped if it leaves fewer homes able to have a kit. Adults never take a kit's bed (more).
• Only nearby homes are priced. Each workplace checks its 32 nearest homes; farther ones are estimated. A far home made cheap by a zipline could be missed.

That's expected on the first pass of a badly housed colony. Children never move, so a child may end up living with different adults. No move leaves fewer homes able to have a kit. Later passes move only a few beavers.

If you dislike the result, load your backup and remove the mod.

Most of a pass is spread over many ticks, but two moments happen in a single tick: taking the snapshot when a pass starts, and applying the moves when it ends. On a large colony either could cause a brief blip.

Frame-time impact hasn't been measured. If you see a real stutter, report it with your colony size and the pass line; until it's fixed, you can disable the mod.

An error stopped the pass. No beaver is left half-moved, the game keeps running, and the mod tries again the next day. It's a bug: copy the full message and report it.

The game refused one of the moves in a cycle, so every beaver in it went back to its old home. Nothing is lost. If it keeps happening, report it with the message.

The mod couldn't read its own data from the save. It starts fresh, at no cost to your colony.

1. Check that every player has the same mod version and game version. If only some players have the mod, or versions differ, the games will disagree about where beavers live.
2. Restart the session from the host's save.
3. If it happens again, report it with every player's Player.log, and say when it happened relative to a Pass line.

One live co-op session, on the code the stable release started from, showed no desync. This release hasn't been played live by two players yet, so a report helps.

The mod is built against Timberborn 1.1.2.4, and a game update can change the parts it relies on.

1. Look in the log for an error mentioning OptimizedLocalHousing.
2. Disable the mod until a matching release is out.
3. Check the releases page.

Load a save from before you installed it. Disabling the mod stops further moves, but doesn't move anyone back.