12 Free RimWorld 1.7 Waylith Modder Tools After Engine Swap - 2026

If you searched rimworld 1.7 mod tools after Ludeon announced Waylith, you do not need another “Unity is dead, 4× forever” montage. You need a free modder toolkit: migrate the csproj to net10.0, swap Unity DLL refs for UnityStubs + Waylith, update Harmony 3, smoke with Frame Profiler and -mod=, find the new Player.log path, attach the debugger without Doorstop, and file a receipt before Discord treats a green menu boot as “1.7 ready.”

On October 12, 2026, Ludeon published Announcing the Waylith Engine and Update 1.7. The same week, the community wiki opened RimWorld 1.7 Mod Updates — the technical rebuild guide players and press usually skip. That wiki page is the spine of this listicle.

Engine honesty first: 1.7 is on Steam’s unstable beta while main stays on 1.6. Most 1.6 mods should load; Prepatcher is a notable exception until it is updated. You should see better performance if you move code to native Waylith methods instead of Unity stub calls — that is an optimization path, not a warranty for every Workshop pack.

This URL is not the Waylith modlist smoke worksheet (player/modpack lab gates). It is not the mid-raid unstable Stop (live-colony refusal). It is not the live Unity exit cargo-cult Stop. Those own smoke rituals, player refusal, and industry folklore. This URL owns the numbered free Waylith modder toolkit.

Why this matters now

October 2026 is when modders either (a) open the wiki once and migrate carefully, or (b) paste “99% of mods work” into Discord and ship broken Prepatcher stacks / wrong Harmony / missing net10.0 builds. Without a toolkit, authors miss free instruments Ludeon and the wiki already documented: Frame Profiler, -mod= launch, new log folder, Doorstop retirement, GLSL shader notes.

Direct answer: Adopt a four-tool minimum this week — wiki + Ludeon framing, net10.0 + UnityStubs/Waylith references, Harmony 3, and one Frame Profiler or -mod= smoke — then expand to the full twelve when shaders, logs, LoadFolders, or IDE attach still fail.

Who this list is for

Time: 30 minutes to map the twelve; 90–180 minutes for the four-tool minimum + first recompile on a small mod.
Honest limit: Official Ludeon modder docs are still rolling (“Coming Soon” on the wiki). Re-check 1.7 Mod Updates and the Ludeon post before partner claims. Do not invent APIs the wiki has not listed.

Pair engine craft with the Unity guide / Godot guide when the conversation turns into “should our studio leave Unity.” Community paste: 25 free game development Discord servers. Player smoke stays on the modlist worksheet.

Non-repetition

Selection criteria

A tool is in only if all are true:

1. Free — wiki, Ludeon post, IDE/extension, NuGet, or in-game/dev-mode surface (no credit card).
2. Primary job is a 1.7 / Waylith modder rebuild or smoke surface.
3. Documented on the wiki Mod Updates page and/or Ludeon’s announcement.
4. Honest limits in one sentence.
5. Not a rehash of the player mid-raid Stop or modlist worksheet as the main job.

Waylith modder cheat sheet

Rule: Write the modder job in Discord before you mass-retarget assemblies. “We got Waylith” is not a job. “net10.0 + stubs refs + Harmony 3 + -mod= smoke on one content pack” is a job.

Four-tool minimum (do this before the other eight)

Latch the receipt only when these four are real (or deliberately skipped with reasons). Then add Upgrade Assistant, log path, Doorstop retirement, LoadFolders, GLSL notes, and Prepatcher honesty as needed.

Tool 1 - RimWorld Wiki 1.7 Mod Updates (free)

Type: Primary technical guide
URL: RimWorld 1.7 Mod Updates
Creator job: Separate rebuild steps from press “4× / leaves Unity” headlines.

How to use Monday

1. Read the Special Note aloud (shim, 99% load, Prepatcher exception).
2. Skim General Tips → New Tools → Harmony / Doorstop / Shaders.
3. Link the page in receipt outbound_refs.

Honest limit: Official Ludeon documentation block may still say “Coming Soon” — the wiki tips are the working checklist today.

Tool 2 - Ludeon Waylith 1.7 announcement (free)

Type: Primary product source
URL: Announcing the Waylith Engine and Update 1.7
Creator job: Anchor unstable opt-in, save notes, yellow mod warnings, and performance claim scope.

How to use Monday

1. Confirm: try 1.7 on unstable; main remains 1.6.
2. Write: “Player smoke ≠ mod rebuild” — point players at the worksheet.
3. Do not paste 2–4× as your mod’s marketing line without your own Frame Profiler evidence.

Honest limit: Announcement is not a csproj tutorial — pair with Tool 1.

Tool 3 - Visual Studio Upgrade Assistant (free)

Type: Project migration GUI
Docs: Wiki → csproj Migration (Upgrade Assistant in Visual Studio)
Creator job: Convert old-style csproj toward SDK-style before net10.0 retarget.

How to use Monday

1. Open the mod project in a VS build that supports .NET 10 (wiki notes VS2026 / modern Rider).
2. Run Upgrade Assistant toward SDK-style.
3. Diff Assemblies paths (1.6 → 1.7) before you celebrate.

Honest limit: Assistant is a helper, not a guarantee — you still remove Unity DLL refs and add stubs.

Tool 4 - upgrade-assistant CLI + migration helpers (free)

Type: CLI / third-party migrate helpers
Examples: upgrade-assistant upgrade project.csproj -o feature.sdkstyle -o Inplace · Project2015To2017.Migrate2019.Tool (wiki-listed)
Creator job: Scriptable migration when GUI is awkward or CI needs a noted path.

How to use Monday

1. Prefer one migration path per repo (GUI or CLI — not both fighting).
2. Commit the csproj diff alone before code changes.
3. If duplicate System attribute errors appear, delete obsolete Properties/AssemblyInfo.cs per wiki troubleshooting.

Honest limit: Third-party migrate tools vary; verify against the wiki sample diff.

Tool 5 - net10.0 target (+ IDE that can build it) (free)

Type: Framework retarget
Creator job: Leave net472 / net481 behind; target net10.0 (the .0 matters).

How to use Monday

1. Set TargetFramework to net10.0.
2. Consider AppendTargetFrameworkToOutputPath=false so Assemblies stay clean.
3. Consider suppressing .deps.json generation RimWorld ignores.
4. Confirm IDE: wiki states VS2022 and older Rider lack .NET 10 support — use VS2026 or Rider 2026-class tooling.

Honest limit: “I installed an SDK” ≠ your IDE project system can target it.

Tool 6 - Assembly-CSharp + UnityStubs + Waylith references (free)

Type: Reference set
Creator job: Remove Unity engine DLL refs; keep using UnityEngine; source if needed; reference Assembly-CSharp.dll, UnityStubs.dll, and Waylith.dll.

How to use Monday

1. Strip Unity DLL references from the csproj.
2. Add the three 1.7 assemblies from the game install.
3. Rebuild dependent libraries for the new engine.
4. Recompile; fix errors top-down.

Honest limit: Stub methods can keep old code compiling while native Waylith paths perform better — plan a later native pass; do not claim “fully native” after a stubs-only build.

Tool 7 - Harmony 3.0 (free)

Type: Patching runtime
Docs: Wiki Harmony section · NuGet 3.0-rc2 · Steam Workshop Harmony
Creator job: RimWorld 1.7 requires updated Harmony 3.0; type checks on __instance / __result are stricter.

How to use Monday

1. Update Workshop / NuGet to Harmony 3.x (3.0-rc2 as wiki-noted).
2. Rebuild patches; fix type mismatches Harmony 3 rejects.
3. Smoke with Tool 9 (-mod=) before publishing “1.7 Harmony ready.”

Honest limit: Harmony 3 rejecting bad injections is a feature — not “Waylith broke Harmony.”

Tool 8 - Frame Profiler (free, in-game)

Type: Dev-mode profiler
Path: Actions/tools → General → Frame Profiler (wiki New Tools)
Creator job: Measure before/after when you claim performance wins from native Waylith methods.

How to use Monday

1. Enable developer mode on a lab save / tiny test colony.
2. Open Frame Profiler; capture a baseline with stubs-heavy code if you still have it.
3. After a native pass, capture again; paste numbers into the receipt — not Ludeon’s 2–4× blog line.

Honest limit: Profiler proves your scene — not marketing for every machine.

Tool 9 - -mod= launch argument (free)

Type: Launch smoke
Creator job: Run the game with a specific mod id list (, or ;) plus base game and installed DLCs, sorted like the in-game manager.

How to use Monday

1. Build a minimal id list: your mod + Harmony + required frameworks.
2. Launch with -mod=... from a shortcut or IDE run config.
3. Confirm load order matches intent; fix errors top-down.
4. Only then expand to a fuller list — players still use the modlist worksheet for colony-facing smoke.

Honest limit: -mod= is not a substitute for Workshop dependency graphs players actually use.

Tool 10 - New Player.log location (free)

Type: Diagnostics path
Path (Windows wiki example): ...\Ludeon Studios\RimWorld by Ludeon Studios\Logs\Player.log
Creator job: Stop grepping the old log path when Discord asks for logs after a 1.7 crash.

How to use Monday

1. Update your README / issue template with the new Logs folder.
2. Reproduce one fail; confirm the file updates.
3. Pin the path in your modding Discord.

Honest limit: OS paths differ; verify on macOS/Linux before you paste Windows-only instructions as universal.

Tool 11 - IDE process attach (Doorstop retired) (free)

Type: Debug workflow
Creator job: Doorstop is no longer required to debug — attach to the RimWorld process from your IDE.

How to use Monday

1. Launch 1.7 (unstable lab).
2. Attach debugger to the process from VS/Rider.
3. Break on a known Harmony prefix; confirm symbols load for your assembly.

Honest limit: Wiki notes specifics may still be thin (“instructions would be useful”) — file what worked on your machine in the receipt.

Tool 12 - LoadFolders, About.xml, Prepatcher + GLSL honesty (free)

Type: Version freeze + exception awareness
Creator job: Update supportedVersions; consider LoadFolders to freeze 1.6 content; know Prepatcher breaks until updated; treat new shaders as GLSL (Linux Vulkan load path); asset bundles from 1.6 often still work but are less necessary.

How to use Monday

1. Bump About.xml versions for 1.7 testing.
2. Freeze prior content with LoadFolders if you dual-support.
3. If your stack needs Prepatcher — HOLD ship claims until Prepatcher updates.
4. For new shaders: place GLSL source for Waylith compile-on-load; remember Linux shader variants matter under Vulkan.

Honest limit: “99% of mods work” does not include “Prepatcher mods work.” Say the exception out loud.

Beginner path — first rebuild evening

1. Read Tools 1–2 (wiki + Ludeon).
2. Copy the mod repo; do not migrate only on main without a branch.
3. Tools 3 or 4 → SDK-style csproj.
4. Tool 5 → net10.0.
5. Tool 6 → stubs/Waylith refs.
6. Tool 7 → Harmony 3.
7. Compile; fix errors.
8. Tool 9 → -mod= smoke; optional Tool 8 profiler.
9. Update log path in README (Tool 10).
10. File the receipt; keep player colonies on the worksheet / Stop rails.

Common beginner mistakes:

• Targeting net10 without .0.
• Leaving Unity engine DLL refs “because using UnityEngine still compiles.”
• Shipping with Harmony 2.x.
• Claiming 1.7 ready after menu boot without -mod= or lab load.
• Ignoring Prepatcher.
• Pasting Ludeon 2–4× as your mod’s FPS proof.
• Telling players to flip live mid-raid “to test my rebuild.”

Developer path — ordered rebuild

Suggested order

1. Framing (1–2)
2. csproj migration (3–5)
3. References (6)
4. Harmony (7)
5. Compile
6. -mod= (9) → Frame Profiler (8)
7. Logs + attach (10–11)
8. About/LoadFolders/shaders/Prepatcher (12)

Stubs vs native Waylith

Library cascade

Framework mods and shared libraries must rebuild for Waylith too. If your content pack depends on an unupdated library, your green compile still fails in-game — treat dependency authors as Tool 7/9 partners, not afterthoughts.

What not to automate yet

• CI that stamps “1.7 compatible” from compile-only.
• Scripts that force-enable Prepatcher stacks.
• Public changelogs that quote Ludeon 2–4× as your result.
• Discord bots that ping players to flip unstable mid-raid for your nightly.

Failure modes this toolkit catches

Anti-patterns (reject in review)

• “99% works — skip the wiki.”
• “Keep net472; stubs will save us.”
• “Harmony 2 is fine if it loaded once.”
• “Frame Profiler is only for Ludeon.”
• “-mod= replaces Workshop testing forever.”
• “Tell players to LIVE_FLIP for QA.”
• “This listicle is the same as the smoke worksheet.”
• “Our studio should leave Unity because RimWorld did” (different Stop).

Worked decisions

Author A — small QoL C# mod, no Prepatcher

Do: Four-tool minimum; Tools 5–7 + 9; LAB publish notes.
Don’t: Claim native Waylith rewrite after stubs-only.

Author B — Harmony-heavy framework

Do: Tool 7 first-class; fix __instance types; -mod= matrix.
Don’t: Blame Waylith for Harmony 3 type enforcement.

Author C — Prepatcher dependency

Do: Tool 12 HOLD; communicate blockers.
Don’t: “1.7 ready” on the store page.

Pack lead D — players ask “is the list safe?”

Do: Point to modlist worksheet; use this toolkit for author rebuilds.
Don’t: One URL for both jobs.

Studio-adjacent E — quoting Waylith as Unity exit

Do: Keep this toolkit for RimWorld mods; industry Stop when shipped; Unity/Godot guides for your engine choice.
Don’t: Merge CapEx stories into a Harmony NuGet bump.

Discord shortlist (paste)

RimWorld 1.7 Waylith — free modder toolkit (minimum 4)
1) Read Wiki 1.7 Mod Updates + Ludeon Waylith post
2) net10.0 + Assembly-CSharp / UnityStubs / Waylith refs
3) Harmony 3.0 (NuGet 3.0-rc2 / Workshop)
4) Frame Profiler OR -mod= smoke on a tiny id list
Then: Upgrade Assistant, new Logs\Player.log path, IDE attach (no Doorstop),
LoadFolders + About.xml, Prepatcher HOLD, GLSL shader notes
Player smoke: rimworld-1-7-waylith-unstable-branch-first-indie-modlist-smoke-worksheet-2026
≠ mid-raid Stop · ≠ Unity-exit industry Stop

CapEx four-liner

1. Asset at risk: Broken Workshop trust + wasted rebuild sprints + false “1.7 ready” labels.
2. Change proposed: “Ship 1.7 update tonight” without wiki migration or isolated smoke.
3. Cost if wrong: Harmony/Prepatcher hard fails, empty log tickets, player LIVE_FLIP pressure, partner FPS claims you cannot defend.
4. Decision owner: Mod author / pack tech lead; default = four-tool minimum before public 1.7 claims.

Two-week calendar

Receipt — rimworld_waylith_modder_toolkit_receipt_v1.json

{
  "receipt_type": "rimworld_waylith_modder_toolkit_receipt_v1",
  "mod_id": "REPLACE",
  "filled_at": "2026-10-13",
  "steam_beta": "unstable",
  "four_tool_minimum_pass": false,
  "tools_used": [1, 2, 5, 6, 7, 9],
  "target_framework": "net10.0",
  "unity_stubs_referenced": false,
  "waylith_referenced": false,
  "harmony_version": "3.0-rc2",
  "frame_profiler_smoked": false,
  "mod_launch_arg_smoked": false,
  "prepatcher_hold": false,
  "player_live_flip_refused": true,
  "owner": "",
  "notes": ""
}

Key takeaways

1. Twelve free tools beat a raw “leaves Unity” headline.
2. Four-tool minimum — framing, net10.0+refs, Harmony 3, profiler/-mod= smoke.
3. Most 1.6 mods load; Prepatcher is a named exception.
4. Stubs compile ≠ native Waylith performance claims.
5. Harmony 3 type checks will reject sloppy patches.
6. Frame Profiler owns your FPS proof.
7. -mod= isolates smoke lists.
8. Player.log moved under a Logs folder.
9. Doorstop is retired — attach from the IDE.
10. This listicle ≠ player modlist worksheet ≠ mid-raid Stop.
11. CapEx favors free wiki rebuilds before hype.
12. Primary keyword: rimworld 1.7 mod tools.

FAQ

What free RimWorld 1.7 Waylith modder tools should I use first?

Start with the four-tool minimum: read the wiki Mod Updates + Ludeon post, retarget net10.0 with UnityStubs/Waylith refs, update Harmony 3, then smoke with Frame Profiler or -mod=.

Do I need to rebuild every mod for 1.7?

The wiki Special Note says ~99% of 1.6 mods should work without rebuilding, with Prepatcher as a notable exception. Rebuilding still helps native Waylith performance and dependency clarity.

Is Harmony 2 enough for 1.7?

No — 1.7 needs Harmony 3.0 (wiki points at Workshop updates and NuGet 3.0-rc2).

How is this different from the modlist smoke worksheet?

The worksheet is the player/modpack lab smoke latch. This page is the numbered author toolkit for rebuild instruments.

Should players flip unstable to test my rebuild?

Not mid-raid on a live colony — use lab saves and the mid-raid Stop. Prefer -mod= and disposable colonies for author smoke.

What primary keyword does this page target?

rimworld 1.7 mod tools — free Waylith modder toolkit after the engine swap.

Related reading

• RimWorld 1.7 Waylith Unstable Branch - First Indie Modlist Smoke Worksheet 2026 — player smoke sibling
• Stop Switching Your Live RimWorld Colony to Waylith Unstable Mid-Raid - 2026 — refusal 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
• Stop Shipping Production Godot Games on 4.8-dev After Feature Freeze - 2026
• Stop Expecting DEVELOPMENT_BUILD Diagnostics on Default Unity 6.6 Dev Builds - 2026
• Steam Winter Sale 2026 Prep Worksheet - Lock Before Dec 17
• Unity Guide
• Godot Guide
• 25 Free Game Development Discord Servers

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

Conclusion

Waylith 1.7 is a real engine swap — and a free toolkit night if you read past the headlines. Retarget net10.0. Swap in UnityStubs and Waylith. Update Harmony 3. Smoke with Frame Profiler and -mod=. Fix your log path. Attach without Doorstop. Say Prepatcher’s name when it blocks you. File a receipt.

Run the four-tool minimum this week. Expand to twelve when the failure mode demands it. Ship verified rebuild craft, not “leaves Unity” folklore.