Stop Shipping Godot 4.8 C Sharp Projects Without .NET 10 - 2026

If you searched godot 4.8 dotnet after 4.8-dev7 raised the C# floor, you do not need another “C# just works if you have any recent SDK” thread. You need a refusal.

Stop shipping Godot 4.8 C Sharp projects without .NET 10. On September 29, 2026, Godot published Dev snapshot: Godot 4.8 dev 7 and the matching download archive: the .NET build (mono) still includes C#, and the page is explicit — .NET 10.0 or newer is required, changing the minimum supported version from .NET 8 to 10. That sentence is the whole refusal. Feature freeze did not grandfather your old SDK checklist. Evaluating 4.8 C# on a machine that only has .NET 8 is not diligence — it is folklore.

This is not the live Stop shipping production Godot on 4.8-dev (refuse Steam pins on pre-release). It is not the live Godot 4.8 .NET 10 C# migrate worksheet (fill-in lab gates). It is not the AccessKit mobile smoke worksheet. Those own production branch refusal, migrate smoke, and a11y lab. This URL owns the SDK floor refusal: do not treat 4.8 C# as “same as 4.7 .NET 8” because Discord still has last year’s install notes.

Platform cousins (Stop Spark closed beta as ship plan, Stop DEVELOPMENT_BUILD diagnostics folklore) refuse premature lanes. This refusal refuses SDK wallpaper — treating an old Target Framework floor as still valid after the download page moved.

Why this matters now

October 2026 sits weeks after 4.8-dev7 feature freeze. C# teams chase animated decals, symbol renaming, and AccessKit on the .NET editor build — then burn an evening on cryptic restore failures, IDE “works on my machine” fights, and CI agents still pinned to .NET 8. Someone declares “Godot C# is broken again” when the failure was a documented minimum bump.

Direct answer: Run the honesty ladder. Prefer SIT_OUT, LAB_SDK on a disposable C# project with .NET 10 installed, or PAIR with a second machine that proves the SDK. Refuse SHIP_NET8_48 — shipping or solemnly evaluating 4.8 C# without .NET 10 evidence. Production Steam pins still belong on the 4.8-dev production Stop — this Stop only owns the SDK floor.

Who this refusal is for

Time: 20 minutes for the ladder; 10 minutes for the Discord paste.
Honest limit: Godot’s snapshot and download pages are authorities for the .NET 10 floor. 4.8 is still pre-release — SDK honesty does not authorize production pins. Re-read 4.8-dev7 and the archive page before arguing. Fill-in migrate steps live on the worksheet sibling.

Non-repetition

Pair community paste with 25 free game development Discord servers. Store timing stays on Steam worksheets — not this SDK refusal.

The claim I am refusing

Claim (false): “We already have .NET 8 from Godot 4.x C# work, so 4.8-dev7 .NET builds will just work — feature freeze means the toolchain is settled, and CI can stay on last year’s SDK image.”

Counter-claim: The 4.8-dev7 download notes change the minimum from .NET 8 to .NET 10. That is a hard floor for the .NET editor/export path called out on the archive page. Keeping .NET 8-only agents is not “conservative” — it is evaluating the wrong dependency graph. Feature freeze does not freeze your host SDK requirement at the previous major.

Same disease as other Stops: freeze-as-stable, checkbox folklore, partnership wallpaper. This is SDK wallpaper.

What Godot actually says (read before you argue)

From 4.8-dev7 and 4.8-dev7 downloads:

If your board strategy is “C# on Godot never needed SDK upgrades mid-cycle,” you skipped the download page paragraph.

Excuse ladder

Honesty ladder (run before any 4.8 C# ticket)

Fail H3–H5 and you do not get to lecture Discord about “Godot C# regressions.”

Decision table — SIT_OUT / LAB_SDK / PAIR / SHIP_NET8_48

Default after this article: LAB_SDK or SIT_OUT. SHIP_NET8_48 is never a diligence outcome. Production pins stay refused on the sibling Stop.

CapEx four-liner (paste to board)

1. Asset at risk: Eval evenings, CI green folklore, and false “C# is broken” narratives.
2. Change proposed: Evaluate or ship Godot 4.8 C# on hosts/agents still at .NET 8.
3. Cost if wrong: Lost weeks, wrong bug reports upstream, and partner demos that only open on one laptop.
4. Decision owner: Tech lead; default = LAB_SDK after .NET 10 evidence — never SHIP_NET8_48.

What the .NET 10 bump actually teaches

Beginner path — 25 minutes (refusal) + handoff

1. Open the 4.8-dev7 archive; read the .NET 10 sentence aloud.
2. Run dotnet --list-sdks (or equivalent) — note presence/absence of 10.x.
3. If missing: latch SIT_OUT or schedule LAB_SDK install — do not “try the .NET editor anyway.”
4. If present: open a disposable C# project only; refuse Steam pin (production Stop).
5. Paste Discord shortlist; file refusal receipt.
6. Hand migrate fill-ins to the live worksheet.

Common beginner mistakes:

• Equating “I have Visual Studio” with “I have .NET 10 SDK.”
• Mixing GDScript success with C# readiness.
• Pinning Steam to 4.8-dev because the SDK upgraded.
• Updating one laptop and declaring the studio ready.
• Filing upstream C# bugs without SDK evidence.
• Using this Stop as the full migrate tutorial.

Developer path — failure-mode separation

Fail taxonomy

Evidence minimum before any “4.8 C# ready” claim

No evidence → SIT_OUT.

CI / agent anti-patterns

• Reusing 4.7-era .NET 8 containers for 4.8 C# jobs.
• Caching global.json that pins net8.0 for 4.8 eval.
• Green GDScript export jobs labeled “C# pipeline OK.”
• Matrix that skips Linux/macOS agents where SDK install differs.

Failure modes this Stop catches

Anti-patterns (reject in review)

• “.NET 8 is fine for 4.8 C#.”
• “Feature freeze means no toolchain changes.”
• “IDE version implies SDK version.”
• “CI green on GDScript = C# ready.”
• “This Stop replaces the production 4.8-dev pin Stop.”
• “This Stop replaces the migrate worksheet.”
• “One developer laptop = studio standard.”
• “Ship Steam on 4.8-dev because .NET 10 installed.”

Worked decisions

Studio A — three C# indies, still on .NET 8 SDKs

Do: SIT_OUT / schedule LAB_SDK; CapEx four-liner for image upgrade.
Don’t: SHIP_NET8_48.

Studio B — lead laptop has .NET 10, CI does not

Do: HOLD CI C# claims; PAIR after image bump.
Don’t: “Works on my machine” as board status.

Studio C — GDScript production, curious about C

Do: Separate lanes; this Stop only if evaluating .NET builds.
Don’t: Block GDScript milestones on C# SDK politics.

Studio D — wants AccessKit + C# on 4.8-dev Steam

Do: Production Stop for pin; this Stop for SDK; AccessKit worksheet for a11y lab.
Don’t: One megathread titled “just upgrade everything.”

Studio E — worksheet ready, needs refusal first

Do: Latch refusal; open migrate worksheet for fill-ins.
Don’t: Skip H1–H8 and jump into half-migrated csproj thrash.

Studio F — Rider/VS2022-era tooling

Do: Confirm IDE supports .NET 10 workflows; upgrade or HOLD.
Don’t: Assume last year’s IDE notes still apply.

Studio G — NuGet private feed + SDK bump

Do: Fix feed auth and prove .NET 10 — two classes.
Don’t: Blame only NuGet when TFM is net10.0.

Discord shortlist (paste)

Stop shipping Godot 4.8 C# projects without .NET 10
1) 4.8-dev7 .NET builds require .NET 10.0+ (was .NET 8)
2) Quote the download archive note before arguing
3) Evidence: dotnet --list-sdks shows 10.x on eval + CI if claimed
4) Decision: SIT_OUT / LAB_SDK / PAIR — refuse SHIP_NET8_48
5) Production Steam pins still refused on 4.8-dev (sibling Stop)
6) Migrate fill-ins: godot-48-dotnet-10-first-indie-csharp-migrate-worksheet-2026
Receipt: godot_48_csharp_dotnet10_refusal_receipt_v1.json
Sources: Godot 4.8-dev7 snapshot · 4.8-dev7 download archive
≠ production 4.8-dev pin Stop · ≠ AccessKit worksheet

Two-week calendar (if you insist on evaluating C#)

Night-of runbook (Discord “C# broken” spiral)

1. Freeze the claim. Paste: “4.8 C# needs .NET 10 — check SDKs before blaming Godot.”
2. Ask for H1–H3. Archive quote + dotnet --list-sdks.
3. Separate production pin — point to production Stop if Steam talk starts.
4. CapEx four-liner aloud if a producer is present.
5. File the receipt the same hour.

Company diligence appendix

What success looks like after this Stop

Success is not “everyone on .NET 10 tonight.” Success is “we never claimed 4.8 C# readiness on .NET 8 folklore.”

Receipt — godot_48_csharp_dotnet10_refusal_receipt_v1.json

{
  "receipt_type": "godot_48_csharp_dotnet10_refusal_receipt_v1",
  "filled_at": "2026-10-14",
  "archive_net10_requirement_quoted": true,
  "dotnet_sdk_10_plus_on_eval_machine": false,
  "godot_dotnet_build_flavor": true,
  "ci_claims_csharp": false,
  "ci_agents_net10": false,
  "production_48dev_pin_refused": true,
  "decision": "SIT_OUT",
  "ship_net8_48_refused": true,
  "gates_h1_h8_pass": false,
  "owner": "",
  "notes": ""
}

Latch the same hour you paste the sit-out.

Key takeaways

1. Stop shipping or solemnly evaluating Godot 4.8 C# without .NET 10.
2. 4.8-dev7 archive: minimum moved .NET 8 → 10.
3. Feature freeze does not grandfather old SDKs.
4. Default: LAB_SDK or SIT_OUT.
5. Refuse SHIP_NET8_48.
6. Prove dotnet --list-sdks — IDE folklore is not evidence.
7. CI agents need the same floor if they claim C#.
8. Production Steam pins stay on the 4.8-dev production Stop.
9. GDScript success ≠ C# readiness.
10. Migrate fill-ins → live worksheet sibling.
11. File the refusal receipt.
12. Primary keyword: godot 4.8 dotnet.

FAQ

Does Godot 4.8-dev7 really require .NET 10 for C#?

Yes for the .NET builds — the download archive states .NET 10.0 or newer, changing the minimum from .NET 8 to 10. See also the dev 7 snapshot.

Can I keep using .NET 8 for Godot 4.7 C#?

Supported 4.7.x workflows are a different lane. This Stop targets 4.8 C#/.NET evaluation and ship claims. Do not mix floors.

Does installing .NET 10 mean I can pin Steam to 4.8-dev?

No. SDK readiness ≠ production pin. See Stop shipping production Godot on 4.8-dev.

How is this different from the migrate worksheet?

The worksheet is the fill-in smoke. This URL is the refusal when teams claim 4.8 C# readiness on .NET 8 folklore.

What about GDScript-only teams?

This Stop is N/A for GDScript-only evaluation. Do not block GDScript milestones with C# SDK politics — and do not claim C# readiness without the .NET build path.

What primary keyword does this page target?

godot 4.8 dotnet — Stop opinion against 4.8 C# without .NET 10.

Related reading

• Godot 4.8 .NET 10 First Indie C Sharp Migrate Worksheet 2026 — lab sibling (live)
• Stop Shipping Production Godot Games on 4.8-dev After Feature Freeze - 2026 — production pin sibling
• Godot 4.8-dev AccessKit Mobile Smoke - First Indie Worksheet 2026
• Godot 4.8 Dev Snapshot - What Changed for Indie Devs July 2026
• Stop Quoting Unity Spark Closed Beta as Your Studio Ship Plan - 2026
• Steam Winter Sale 2026 Prep Worksheet - Lock Before Dec 17
• Godot Guide
• 25 Free Game Development Discord Servers

Primary sources: Dev snapshot: Godot 4.8 dev 7 · Download Godot 4.8 (dev7).

Conclusion

Feature freeze moved Godot 4.8 toward beta — it did not leave your C# host SDK at .NET 8. Stop shipping or solemnly evaluating Godot 4.8 C# without .NET 10. Prove the SDK. Align CI. Keep production pins on supported lines. Hand migrate steps to the live worksheet.

Paste the sit-out. Install the floor. File the receipt. Ship C# claims you can evidence — not last year’s install folklore.