Stop Shipping Production Worlds on Terrain3D 1.0 After 1.1 - 2026

If a terrain3d 1.1 upgrade thread opened because someone forked a new outdoor vertical slice on 1.0.2 “because the jam already knows that version,” the first sentence is usually wrong. People write “1.1 is just polish,” “we will AssetLib-update after Gold,” or “API changes do not matter if we only sculpt.” After October 30, 2026, that folklore is expensive. TokisanGames shipped Terrain3D v1.1.0 with an explicit note: Changes to the API between 1.0 and 1.1 — plus oceans, C# bindings, displacement, and mobile knobs your 1.0 seed will not grow into cleanly.

The capability map lives on What Godot Terrain3D 1.1.0 Changed for Indies - 2026. Official install/upgrade steps live in Installation & Upgrade. This page is the refusal. Stop shipping new production outdoor worlds on Terrain3D 1.0 after 1.1. Freeze an existing 1.0 title for a near-term milestone if you must — do not seed the next paid world on the old surface.

Direct answer: Print the Terrain3D version in boot or Project Settings. If a new production outdoor branch still pins 1.0.x, latch VERSION_REFUSED, upgrade to 1.1.0+ on Godot 4.5–4.8+, follow upgrade docs, smoke the largest outdoor scene and instancers, then continue art. If you are mid-Gold on a proven 1.0 build with <2 weeks to ship, latch MILESTONE_FREEZE with an owner and a dated 1.1 branch — do not pretend the freeze is a forever strategy.

Why this matters now

1.1 is not a quiet point release. The GitHub notes call out 380+ updates, Godot 4.8 support, generated C# bindings, an ocean mesh, texture displacement, AO packed normals, Max Regions, and an instancer move toward RenderingServer. Community writeups (GameFromScratch, IndieTooling) treat it as a feature beat. Seeding a new world on 1.0 means you will either (a) upgrade mid-content with API friction, or (b) forever miss the 1.1 tooling surface while Discord assumes everyone is current.

The failure mode is classic addon debt: lead laptop on 1.1 from AssetLib, contractor still on a vendored 1.0 zip, scene files diverge, “Terrain3D is unstable this week” becomes the stand-up story. It is not unstable. It is version wallpaper.

Time and prerequisites

Plan 60 to 120 minutes for a refuse-and-smoke pass on a small outdoor project — not a water art rewrite.

Beginners can print the version in five minutes. A tech lead owns the pin in repo. A producer owns the rule that no new outdoor epic starts on 1.0 after Oct 30.

Who this refusal is for

Platform basics: Godot guide. Plugin context: 16 free Godot 4 plugins. This URL owns the Stop — not the map, not the checks listicle, not the ocean worksheet.

Non-repetition

The habit this Stop refuses

Five sentences keep showing up in Godot outdoor channels. Each one skips the version print.

1. “1.1 is just polish.” Release notes disagree — API changes + major features.
2. “We’ll upgrade after the jam.” The jam seeds the production world. Seed on 1.1 or schedule a dated upgrade branch.
3. “Only the lead needs 1.1.” One 1.0 seat re-saves data assumptions and poisons the shared project.
4. “We don’t use oceans or C#, so 1.0 is fine.” API and instancer changes still hit GDScript sculpt/paint pipelines.
5. “AssetLib will fix it silently.” Follow Installation & Upgrade; silent hope is not a migrate plan.

A quieter sixth habit: pin 1.0 in .gitignore folklore while CI downloads latest — humans and pipeline disagree. The refusal treats them as one fleet.

Refuse ladder

Use one code on the ticket. Do not invent a seventh to sound busy.

Discord paste: “Stop seeding new worlds on Terrain3D 1.0 after 1.1. Print the version. Upgrade or dated freeze.”

What the release actually said (read before you argue)

From v1.1.0-stable and docs:

If your appeal is “our sculpt brushes feel the same,” you are arguing past the product’s versioning.

Excuse ladder

Audience ramps

Beginner path (thirty minutes)

1. Open Project → Project Settings → Plugins; note Terrain3D enabled.
2. Check addons/terrain_3d against v1.1.0.
3. If 1.0 and this is a new outdoor project → upgrade per docs.
4. Paste Discord refuse line.
5. Do not start a second biome folder until version is 1.1.x.

Developer path (one evening)

1. git checkout -b chore/terrain3d-1-1.
2. Backup terrain data; replace addon with 1.1.0.
3. Fix compile/API breaks from the change note.
4. Walk the largest outdoor scene; re-smoke foliage instancer.
5. Pin version in README + boot log.
6. Optionally enable ocean on a throwaway scene — do not block upgrade on water art.
7. Leave tessellation at 0 until measured.
8. Cross-link what-changed.
9. Latch FLOOR_MET with screenshots.
10. Schedule checks/worksheet siblings for scorecard/receipt (queued).

Creator Monday checklist

• [ ] Version printed for the outdoor branch.
• [ ] New production world is on 1.1.0+ or MILESTONE_FREEZE documented.
• [ ] No silent 1.0 contractor seats.
• [ ] Upgrade docs followed (not hope).
• [ ] Discord paste sent.
• [ ] CapEx four-liner ready for partners.

Opinion spine

Quotable takeaway: Stop shipping new production worlds on Terrain3D 1.0 after 1.1 — seed on 1.1, or freeze 1.0 with an owner and a dated upgrade branch.

Failure modes

CapEx four-liner (diligence zip cover)

1. Scope — New outdoor production worlds on Terrain3D 1.1.0+ (Godot 4.5–4.8+).
2. Cost — one upgrade smoke vs mid-content API migration.
3. Evidence — version string + outdoor walk note + README pin.
4. Owner — human who refuses new 1.0 seeds after Oct 30, 2026.

Worked example — refuse a new 1.0 open-world pitch

1. Pitch: “Clone last year’s 1.0 template for the new zone.”
2. Latch VERSION_REFUSED.
3. Create project from 1.1.0 template / upgraded addon.
4. Import height data if needed; smoke walk.
5. Only then assign biome artists.

Worked example — honest milestone freeze

1. Demo Friday on proven 1.0 build.
2. Latch MILESTONE_FREEZE with producer name + date.
3. Open chore/terrain3d-1-1 the following Monday.
4. No new biomes land on the freeze branch after the demo.
5. Merge when FLOOR_MET.

Scheduling table

Red flags that mean “stop the 1.0 seed”

These flags are cheaper than repainting three biomes after a forced mid-year upgrade.

What “production world” means in this Stop

This refusal is about shipping intent, not hobby sandboxes.

If you are honest that the project is throwaway, 1.0 practice is fine — label it throwaway. The Stop fires when the folder quietly becomes the ship folder.

Upgrade smoke checklist (minimum)

Copy into the PR that bumps the addon:

• [ ] Godot version is 4.5–4.8+
• [ ] Addon replaced with 1.1.0+ from release or AssetLib
• [ ] Installation & Upgrade steps followed
• [ ] Project opens without script errors on terrain autoloads/nodes
• [ ] Largest outdoor scene loads
• [ ] 60-second character (or free cam) walk on sculpted ground
• [ ] Foliage/instancer density spot-check
• [ ] Terrain3D version string committed in README or addons note
• [ ] No tessellation experiment mixed into the smoke PR

If any box is unchecked, you have API_UNSMOKED, not FLOOR_MET.

Ninety-minute refuse evening

Do not spend the evening designing foam. Foam is not the refuse.

Incident script — “Terrain broke after someone updated”

1. Freeze commits that mix 1.0/1.1 data blindly.
2. Print Terrain3D version on every seat.
3. Classify FLEET_DRIFT or API_UNSMOKED.
4. Align fleet to 1.1.0 (preferred) or documented freeze.
5. Smoke outdoor path + instancer.
6. Postmortem one-liner: who vendored which zip.

Company diligence — questions

Partners funding open-world scopes should treat a 1.0 pin after October 30 as a process smell, the same way they treat an unpinned engine minor. You are allowed a freeze; you are not allowed amnesia. Put the freeze ticket ID next to the version string in the diligence zip so nobody “forgets” the upgrade Monday.

Freeze vs refuse — decision card

If the team cannot point to which row they are on, they are in folklore mode. Folklore mode is what this Stop exists to end. Print the card in the project channel once; react with the emoji that matches your row; then do the work that row demands before anyone paints another cliff. A reacted card plus a version screenshot beats another meeting about whether “1.1 feels necessary.” Necessity is already documented in the release notes; your job is compliance with a dated plan, not vibes about polish.

How this pairs with siblings

Do not paste this essay as proof. Paste a version string + smoke note.

Internal links

Map: Terrain3D 1.1 what-changed. Hub: Godot guide. Plugins: 16 free Godot 4 plugins. DCC cousin: World Machine spike. Resources: 25 Discords. Courses: /courses.

Key takeaways

1. Terrain3D 1.1.0 shipped Oct 30, 2026 with API changes.
2. Stop seeding new production outdoor worlds on 1.0.
3. Near-term Gold may use MILESTONE_FREEZE — not forever 1.0.
4. Print the version on every seat.
5. Follow Installation & Upgrade — not silent AssetLib hope.
6. Smoke outdoor scenes + instancers after upgrade.
7. Oceans/C#/displacement are reasons to prefer 1.1 — API is enough alone.
8. Fleet drift is a refuse code, not a personality clash.
9. Displacement is optional; do not blame 1.1 for unbudgeted tessellation.
10. Mobile claims need Platforms + 1.1 knobs.
11. CapEx four-liner belongs in diligence zips.
12. Quotable: seed on 1.1, or freeze 1.0 with owner and date.
13. This URL owns the Stop — not the map/checks/worksheet.
14. World Machine exports do not replace the addon pin.
15. Re-read the GitHub release when you argue.

FAQ

Should every project upgrade immediately?

New outdoor production worlds: yes, target 1.1.0+. Existing near-ship 1.0 titles may freeze briefly with an owner.

Where is the official upgrade guide?

Installation & Upgrade

What is the primary keyword this Stop answers?

terrain3d 1.1 upgrade — refuse staying on 1.0 for new worlds.

Does this ban 1.0 forever?

No. It bans new production seeds on 1.0 after 1.1 without a dated freeze exception.

Capability map?

What Godot Terrain3D 1.1.0 Changed for Indies - 2026

Release notes?

Terrain3D v1.1.0

What refuse code for a new 1.0 open world?

VERSION_REFUSED

What about tutorials still on 1.0?

Update the template; do not clone stale jam zips into paid work.

Sources

• Terrain3D v1.1.0 (GitHub)
• Installation & Upgrade (ReadTheDocs)
• Platforms · Displacement
• Godot Asset Library — Terrain3D