RimWorld 1.7 Waylith Unstable Branch - First Indie Modlist Smoke Worksheet 2026

If you searched rimworld 1.7 waylith after Ludeon announced update 1.7, you do not need another “4× performance, leave Unity forever” montage. You need a fill-in worksheet that locks six decisions before Discord invents a colony-wide “flip unstable with your full 200-mod list tonight” sprint:

1. Lab save only — smoke on a disposable save copy, not the mid-raid live colony
2. Branch honesty — Steam unstable for 1.7; main remains 1.6 until you opt in
3. Yellow-warning inventory — list every “potentially unsupported” mod before you call the list “fine”
4. Rollback path — prove you can return to 1.6 main without guessing
5. Hardware floor — older PCs may fail 1.7; record GPU/OS before blaming mods
6. Decision latch — choose LAB_SMOKE, HOLD, PAIR, or refuse LIVE_FLIP

This URL is that worksheet. It is not the Stop switching live colony to Waylith unstable mid-raid (player refusal). It is not the live 12 free Waylith modder tools (toolkit listicle). It is not the live Unity exit cargo-cult Stop (industry folklore). Those own refusal, instruments, and CapEx-for-studios. This URL owns the first indie Waylith unstable modlist smoke evening with gates outsiders can footnote.

Why this matters now

On October 12, 2026, Ludeon published Announcing the Waylith Engine and Update 1.7: RimWorld moves from Unity to Ludeon’s in-house Waylith engine, with internal tests claiming roughly 2–4× performance gains. You can try 1.7 now — on Steam’s unstable beta branch. The main branch most players use remains 1.6. Saves are described as compatible both ways. Most mods should load; some show yellow “potentially unsupported” warnings because the version number changed. Older PCs (10+ years) may fail to run 1.7.

The RimWorld Wiki 1.7 mod updates page is already collecting rebuild notes (net10.0, UnityStubs, Harmony 3, Frame Profiler, -mod= launch). That is modder surface. Players and small modpack maintainers still lack a single fill-in smoke worksheet: copy the save, opt into unstable, inventory yellow mods, boot, run a short scenario list, decide, file a receipt, rollback.

October 2026 is when colony Discords invent “everyone switch tonight.” Someone flips unstable mid-mechanoid raid with an uninventoried ModConfig, hits a yellow-mod cascade or an older-GPU hard fail, and loses the session — not always the save file. This worksheet exists so the first Waylith night is a lab ritual, not a live-colony bet.

Direct answer: Fill Sections A–F this week on a lab save copy. Choose LAB_SMOKE, HOLD, PAIR, or refuse LIVE_FLIP. Do not treat unstable as your default colony until gates W1–W8 pass and the receipt JSON is filed. If you are mid-raid tonight, read the mid-raid Stop first and sit out.

Who fills this worksheet

Time: 45–90 minutes first lab smoke (plus download); 20 minutes to re-run gates after each modlist trim.
Honest limit: Ludeon’s announcement is the authority for branch policy, save notes, and how to opt in. Performance numbers are their tests — your machine and modlist will differ. Re-read the Ludeon post and the 1.7 mod updates wiki before arguing in Discord. Do not invent Harmony/API contracts the wiki has not documented.

Non-repetition

Pair engine craft later with the Unity guide / Godot guide when the cargo-cult conversation turns into “should we leave Unity.” Community paste lives on 25 free game development Discord servers. Store timing still belongs in Steam worksheets — not this modlist smoke.

Official facts you must quote (not invent)

From Announcing the Waylith Engine and Update 1.7 and RimWorld Wiki 1.7 Mod Updates:

1. RimWorld 1.7 introduces Ludeon’s Waylith engine (Unity exit for RimWorld).
2. Try 1.7 via Steam → Properties → Betas → unstable; restart; choose “Play 1.7 Unstable” if prompted.
3. Main branch remains 1.6 until you opt in.
4. Saves are described as compatible both ways (1.6 ↔ 1.7) — still backup before you smoke.
5. Most mods should load; some show yellow “potentially unsupported” warnings because the version number changed.
6. Older PCs (roughly 10+ years) may not run 1.7.
7. Internal performance claims are roughly 2–4× under Ludeon’s test conditions — not a warranty for your list.
8. Modder rebuild notes (framework targets, Harmony, profilers, launch flags) live on the wiki — use them for modder nights, not as a substitute for this player/modpack smoke.

Pasteable diligence line:

We are evaluating RimWorld 1.7 Waylith on Steam unstable using a lab save copy, with yellow-mod inventory, hardware floor check, rollback to 1.6 main, and a filed smoke receipt before any live colony depends on 1.7. Live colony stays on 1.6 until W1–W8 pass. Mid-raid flips are refused.

Section A — Colony + branch lock (fill in)

A-gate: If lab save equals the only live save and you have no backup folder, stop. Duplicate the save (or copy the Saves folder entry) into a clearly named *_waylith_lab file first. If you are mid-raid on the live colony, do not start Section C — sit out per the mid-raid Stop.

Section B — Hardware + OS floor (fill in)

B-gate: If the machine is roughly 10+ years old or you already struggle on 1.6 with a huge list, default to HOLD or a tiny lab list — not “full Ideology + Biotech + 180 Steam Workshop packs on night one.” Hardware fails look like “Waylith broke mods” in Discord.

Section C — Opt-in + rollback rehearsal (fill in)

C-gate: Screenshot the title-screen version. If you cannot write a rollback plan in one sentence, you are not ready to smoke. Preferred drill: after first boot confirmation, switch back to main once on a throwaway evening so the muscle memory exists before a softlock.

Beginner opt-in steps (do once)

1. Finish or pause any live raid on 1.6.
2. Copy your save to ColonyName_waylith_lab (exact folder paths vary — use RimWorld’s Saves location for your OS).
3. Steam → RimWorld → Properties → Betas → unstable.
4. Restart Steam / let the 1.7 download finish.
5. Launch; confirm 1.7 / Waylith-era version string.
6. Load only the lab save (or start a tiny new colony for first boot).
7. After smoke, switch Betas back to none / default and confirm 1.6 still opens your live save.

Section D — Modlist inventory (fill in)

D-gate: A yellow warning is not automatically a crash — and a green load is not automatically “raid-safe.” Inventory every yellow row before you claim the list is fine. Prefer trimmed core on night one: DLC you actually use + Harmony/framework + 5–15 favorite content mods. Full 200-mod mirrors belong on night two after W1–W8 pass on a thin list.

Yellow-warning triage table

Section E — Boot + scenario smoke (fill in)

E-gate: If boot fails, do not “fix it” by flipping the live colony. Capture the log, trim the list, or HOLD. Save/reload is mandatory smoke — Waylith nights that “look fine until you save” are how people lose evenings.

Minimum scenario list (W5–W7)

1. Cold boot — title → mods acknowledged → menu.
2. Load path — lab save or new tiny colony.
3. UI sanity — Architect / Work / Assign still open.
4. Persistence — save, quit to OS, relaunch 1.7, reload.
5. Optional combat stub — draft two pawns, force a tiny fight or manhunter if safe.
6. Optional log skim — note repeating exceptions tied to yellow mods.

Section F — Decision + receipt (fill in)

Decision meanings

Gates W1–W8 (pass / fail)

Fail closed on W1–W4 before you mass-enable the full Workshop list.

Beginner path — 75 minutes

1. Read Ludeon’s Waylith 1.7 post aloud — especially unstable vs main.
2. If mid-raid: stop; paste the sit-out Stop.
3. Copy save → *_waylith_lab.
4. Fill Sections A–B.
5. Opt into unstable; record version (Section C).
6. Trim to core list; inventory yellows (Section D).
7. Run minimum scenarios (Section E).
8. Latch LAB_SMOKE or HOLD; file receipt (Section F).
9. Rollback to main; open live save once to prove 1.6.

Common beginner mistakes:

• Treating unstable as the “required update” because Steam downloaded something.
• Flipping mid-raid “just to see FPS.”
• Calling yellow warnings “harmless” without listing names.
• Smoking only on a brand-new colony and declaring the 200-mod live save safe.
• Skipping save/quit/reload.
• Blaming Waylith when a 2013 GPU fails Ludeon’s older-PC warning.
• Pasting Ludeon’s 2–4× as your personal result without a before/after note.

Developer / modpack path — ordered smoke and honesty

List strategies (pick one tonight)

Write the strategy in Section D before you click Play. Switching strategy mid-evening without resetting the receipt is how Discord gets contradictory “it works / it doesn’t” posts from the same person.

Framework-first order (modpack leads)

1. Harmony / library mods that everything depends on.
2. DLC-dependent frameworks you actually use.
3. UI / quality-of-life packs with yellow warnings.
4. Content packs (races, biomes, weapons) last.
5. Experimental or abandoned Workshop items — HOLD or disable for night one.

Cross-check rebuild notes on the 1.7 mod updates wiki when you are the author of a mod. Player smoke still uses this worksheet; author rebuild nights use wiki + the tools listicle when shipped.

Multiplayer / shared-colony note

If you share a colony with friends:

• PAIR means everyone smokes the same lab copy / same list notes — not “one person flips live and hope.”
• Host and clients should match branch intent (all 1.6 main vs all lab-unstable experiments).
• Do not invent dedicated-server guarantees Ludeon’s post did not make for your setup — write what you actually tested.

What not to automate yet

• Scripts that force-enable every Workshop item on unstable.
• CI that claims “Waylith compatible” from a green menu boot alone.
• Public modpack changelogs that say “1.7 ready” without W5–W7 evidence.
• Discord bots that ping “switch unstable” during raid nights.

Failure modes this worksheet catches

Anti-patterns (reject in review)

• “Saves are compatible, so mid-raid flip is safe.”
• “Yellow means outdated but always works.”
• “Main is outdated — unstable is the real game now.”
• “Ludeon said 4×, so my 200-mod list is free performance.”
• “I booted once; ship the modpack as 1.7-ready.”
• “Rollback is just verify files if something breaks.”
• “This worksheet is the same as the mid-raid Stop.” (Refusal ≠ fill-in smoke.)
• “This worksheet replaces the modder tools listicle.” (Instruments ≠ player smoke.)

Worked decisions

Player A — mid-mechanoid raid, Discord says “switch for FPS”

Do: HOLD; finish raid on 1.6; read the mid-raid Stop.
Don’t: LIVE_FLIP for a screenshot.

Player B — quiet Tuesday, 40-mod list, decent PC

Do: LAB_SMOKE on *_waylith_lab with trimmed core; inventory yellows; persist smoke; stay on 1.6 for live.
Don’t: Full mirror on night one.

Modpack lead C — community asks “is the list 1.7 ready?”

Do: Publish W1–W8 results + yellow inventory; label LAB_SMOKE until persist passes on the published list.
Don’t: Changelog “1.7 supported” from a menu boot alone.

Modder D — needs Harmony / net10 rebuild notes

Do: Use the wiki 1.7 mod updates + queued tools listicle; keep this worksheet for player-facing smoke of your test list.
Don’t: Pretend a Frame Profiler session is a colony smoke receipt.

Studio-adjacent E — quoting Waylith as “we should leave Unity”

Do: Separate tracks — colony smoke here; industry refusal on the Unity-exit Stop when shipped; engine craft on Unity / Godot guides.
Don’t: One ticket titled “RimWorld proved our Unity exit.”

CapEx four-liner

1. Asset at risk: Live colony session integrity + mod-order trust + evening goodwill.
2. Change proposed: Flip Steam unstable with a full uninventoried list on the live save (often mid-raid).
3. Cost if wrong: Softlocks, yellow-mod cascades, hardware fails, rollback panic, Discord blame spirals.
4. Decision owner: Colony / modpack lead; default = LAB_SMOKE on a copy or HOLD until W1–W8 pass.

Two-week calendar

Discord shortlist (paste)

RimWorld 1.7 Waylith — first modlist smoke
1) Lab save copy only (not live mid-raid)
2) Steam Betas → unstable; main stays 1.6 for live
3) Hardware floor noted (older PCs may fail)
4) Inventory every yellow “potentially unsupported” mod
5) Boot + save/quit/reload before calling it fine
6) Decision: LAB_SMOKE / HOLD / PAIR — refuse LIVE_FLIP by default
Receipt: rimworld_waylith_modlist_smoke_receipt_v1.json
Notes: Ludeon Waylith 1.7 post · Wiki 1.7 mod updates
≠ mid-raid Stop (refusal) · ≠ modder tools listicle · ≠ Unity-exit industry Stop

Receipt — rimworld_waylith_modlist_smoke_receipt_v1.json

{
  "receipt_type": "rimworld_waylith_modlist_smoke_receipt_v1",
  "colony_live": "REPLACE",
  "lab_save": "REPLACE_waylith_lab",
  "filled_at": "2026-10-13",
  "steam_beta": "unstable",
  "version_string_1_7": "",
  "main_branch_remains_1_6": true,
  "hardware_age_years_approx": 0,
  "mod_count_lab": 0,
  "yellow_warning_count": 0,
  "yellow_mod_names": [],
  "boot_pass": false,
  "persist_reload_pass": false,
  "rollback_plan_written": false,
  "rollback_drilled": false,
  "decision": "LAB_SMOKE",
  "live_flip_refused": true,
  "gates_w1_w8_pass": false,
  "owner": "",
  "notes": ""
}

Latch the same hour you finish persist smoke (or HOLD).

Key takeaways

1. RimWorld 1.7 Waylith is on Steam unstable; main remains 1.6.
2. This worksheet owns the first modlist smoke evening, not the mid-raid refusal alone.
3. Smoke on a lab save copy — never mid-raid live-first.
4. Inventory every yellow “potentially unsupported” warning.
5. Pass W1–W8 before calling a list 1.7-ready.
6. Default decision: LAB_SMOKE or HOLD.
7. LIVE_FLIP is refused by default — see the sibling Stop.
8. Save → quit → reload is mandatory smoke.
9. Older PCs may fail 1.7 — record hardware before blaming mods.
10. Ludeon’s 2–4× claims are their tests, not your warranty.
11. File the receipt JSON.
12. Primary keyword: rimworld 1.7 waylith.

FAQ

How do I try RimWorld 1.7 Waylith without risking my live colony?

Copy your save to a lab name, set Steam Betas to unstable, smoke only the lab save, then switch back to main for the live colony. Follow Ludeon’s opt-in steps.

Are 1.6 and 1.7 saves compatible?

Ludeon states saves work both ways. Still backup and prefer a lab copy before unstable. Compatibility reduces one disaster class; it does not make mid-raid flips safe.

What do yellow “potentially unsupported” mod warnings mean?

They often appear because the version number changed. List every yellow name, trim aggressively on night one, and do not equate “loaded” with “raid-safe.”

Should I switch mid-raid for the performance boost?

No. Refuse LIVE_FLIP mid-raid — use the Stop Switching Your Live RimWorld Colony to Waylith Unstable Mid-Raid sit-out, then return here for a quiet lab smoke.

Is this the same as the modder tools listicle?

No. The tools listicle covers free instruments after the engine swap. This URL is the player/modpack fill-in smoke worksheet.

What primary keyword does this page target?

rimworld 1.7 waylith — first indie unstable-branch modlist smoke worksheet.

Related reading

• Stop Switching Your Live RimWorld Colony to Waylith Unstable Mid-Raid - 2026 — refusal sibling
• 12 Free RimWorld 1.7 Waylith Modder Tools After Engine Swap - 2026 — toolkit sibling
• Stop Quoting RimWorld Waylith 4x Gains as Your Unity Studio Exit Plan - 2026 — industry cousin
• Stop Upgrading Unity Mid Steam Next Fest Week - Pin 6.3 LTS 2026 — engine FOMO cousin
• Stop Shipping Production Godot Games on 4.8-dev After Feature Freeze - 2026 — pre-release pin cousin
• Stop Expecting DEVELOPMENT_BUILD Diagnostics on Default Unity 6.6 Dev Builds - 2026 — checkbox folklore cousin
• Steam Winter Sale 2026 Prep Worksheet - Lock Before Dec 17
• Unity Guide
• Godot Guide
• 25 Free Game Development Discord Servers

Primary sources: Announcing the Waylith Engine and Update 1.7 · RimWorld 1.7 Mod Updates (Wiki) · Steam news mirror.

Conclusion

Waylith 1.7 is a real Ludeon milestone — and an unstable opt-in while main stays on 1.6. Performance hype does not replace lab saves, yellow-mod inventories, persist smoke, or rollback drills. Fill the worksheet. Latch LAB_SMOKE or HOLD. Refuse mid-raid LIVE_FLIP. File the receipt.

Print Sections A–F. Paste Discord. Treat the first Waylith night as a smoke ritual, not a live-colony bet.