12 Free Defold 1.14 Upgrade Checks Before a Bundle - 2026

If you searched defold upgrade checklist after Defold 1.14.0, you do not need another highlight-reel paste. You need a numbered free-check kit before anyone runs Bob over the branch that still ships to players.

Defold published Defold release 1.14.0 on 12 October 2026 and the forum thread Defold 1.14.0 has been released. Migrations split across Win32 removal, mandatory shared Lua, accelerometer default flip, generational native handles, editor plugin APIs, cubemap-aware render targets, iOS IAC links, Metal-default macOS, and a gated Xbox track. Missing from the narrative post is a single Discord-pasteable pass that forces a branch decision before the live bundle.

This listicle owns the free kit: twelve checks that cost nothing but time. It is not the what-changed map, not the Win32 Stop, and not a native-handle lab worksheet. Those own facts, refusal, and fill-in evenings. This URL owns the toolkit roundup.

Why this matters now

Studios bump the editor because Xbox headlines, then discover x86-win32 CI, a disabled shared-state project, or a cold-start deep link that died with UIScene. The release notes already listed the breaks. What people skip is a minimum gate before Bob.

Direct answer: Run checks 1–4 before you install 1.14 on the ship branch. Run 5–9 on a throwaway upgrade branch with native/plugins in scope. Run 10–12 before you tell Discord the bump is “fine.” If check 1 fails, stop — that is the point of the kit.

Who this list is for

Time: 20 minutes for 1–4; 90–180 minutes for a full upgrade-branch pass.
Honest limit: Official posts are authority. Hotfixes (Xcode/plist) may follow day one — re-check the forum thread before you freeze a candidate.

Non-repetition

Pair a Discord paste with 25 free game development Discord servers. For Steam desktop save-path discipline after a Windows retarget, keep Your First Defold Steam Desktop Collection and Save Audit nearby.

Four-check minimum (if you only have twenty minutes)

Do not Bob the ship branch until these four are green or explicitly waived with an owner name.

The twelve checks

1. Version-control latch

Do: Tag or commit the last known-good pre-1.14 tip. Open branch upgrade/defold-1-14 (name free). Confirm CI still greens on the tag.

Pass: You can restore yesterday’s Bob without archaeology.
Fail: “We’ll remember” with a dirty main.
Do next: If fail, stop — fix VCS before editor download.

2. Win32 / target-string grep

Do: Grep for x86-win32, Bob win32, and depot copy that claims 32-bit. Retarget to x86_64-win32. Treat Bob win32 as x64 alias only.

Pass: Zero live x86-win32; store copy honest.
Fail: 32-bit intent on 1.14 artifacts.
Do next: Read the Win32 Stop and latch NO_32BIT_BUNDLE.

3. Shared Lua state

Do: If the project ever disabled shared state between .script, .gui_script, and .render_script, plan a refactor. 1.14 makes sharing mandatory; setting is gone.

Pass: Already shared (default) or globals/modules retested on a branch.
Fail: Separate-state assumptions still in design docs.
Do next: Enable shared state on 1.13 first if you have not bumped yet; file repros upstream if blocked.

4. Accelerometer default

Do: Search for acceleration / tilt input. 1.14 disables accelerometer by default. Enable explicitly in game.project if you need it.

Pass: Decision written — enabled or N/A.
Fail: “Mobile still works” without a device smoke after bump.
Do next: Put the toggle change in the same PR as the engine bump when tilt is ship-critical.

5. Generational handles / native extensions

Do: Inventory native extensions and prebuilt dmSDK libs. Rebuild against 1.14. Stop treating opaque handles as raw pointers.

Pass: Extensions rebuild clean; Lua-only projects mark N/A with a note.
Fail: Stale .a / .lib from 1.13 linked into 1.14.
Do next: See what-changed handle section; Lua GO code does not need handle migration.

6. Editor plugins (resource-type API)

Do: If you ship editor plugins that register resource types, update reader/loader signatures per release notes / extension-simpledata migration example.

Pass: Plugins load on 1.14 editor or N/A (no custom resource-type plugins).
Fail: Editor errors on open after bump, ignored as “cosmetic.”
Do next: Isolate plugin upgrade on a branch before content artists flood Discord.

7. Native SetRenderTarget / cubemap readiness

Do: Grep C++ for old SetRenderTarget(context, target, transient_mask) overload. Migrate to cubemap-aware params. Lua ordinary RTs are called out as OK; cubemap adoption is optional lab.

Pass: Native RT code compiles on 1.14 or N/A.
Fail: Extension graphics code left “until Xbox week.”
Do next: Cubemap feature experiments stay off the critical path unless reflections are the milestone.

8. iOS links / IAC

Do: If you use custom URL schemes or universal links, update IAC for UIScene lifecycle. Test cold start and already-running link delivery. Requires Defold/Bob 1.14+.

Pass: Both paths verified on device/simulator or N/A (no iOS links).
Fail: Only tested warm links in editor.
Do next: Duo readiness work in 1.14 does not replace this check.

9. macOS Metal default

Do: Confirm Metal-as-default is acceptable. If you require OpenGL or Vulkan on macOS, set App Manifest explicitly and smoke.

Pass: Manifest decision recorded; one macOS boot smoke.
Fail: “Mac is fine” with no App Manifest glance after bump.
Do next: Pair with desktop Windows x64 smoke from check 2.

10. Multi-platform smoke (ship matrix)

Do: Bob or editor-bundle every platform you actually ship (Windows x64, macOS, Linux, HTML5, iOS, Android, consoles you already have access to). Twenty-minute smoke each: boot, one GUI, one gameplay loop, save/load if any.

Pass: Matrix green on the upgrade branch.
Fail: Only Windows editor Play tested.
Do next: Do not add Xbox to this matrix until check 12 says you have access.

11. Forum hotfix / plist / Xcode pass

Do: Re-open the 1.14.0 release thread for hotfixes (e.g. Xcode 27.1 / plist notes). If you use a custom plist, confirm it matches the hotfixed engine.

Pass: Thread checked within 24h of RC; plist note signed.
Fail: Day-one build frozen forever without re-read.
Do next: Link the forum post in the RC ticket.

12. Xbox track is separate

Do: Confirm nobody blocked the upgrade on “waiting for Xbox target in public download.” Public Defold has no Xbox target; Microsoft approval + Defold middleware access required.

Pass: Xbox is a parallel track with an owner — or explicitly out of scope.
Fail: Ship branch held hostage for middleware that is not in the zip.
Do next: Read Xbox section on what-changed; still finish checks 1–11.

Check card template (copy per row)

Check #:
Owner:
Branch:
PASS / FAIL / N/A:
Evidence (PR / screenshot / grep):
Blocker if FAIL:

Fill twelve cards even when half are N/A. N/A without a reason is a fail.

Beginner evening path

1. Complete four-check minimum on paper (15 min).
2. Create upgrade branch; install 1.14 editor (20 min).
3. Run checks 2–4 fixes in one PR (30–60 min).
4. If no native code, mark 5–7 N/A with notes; still do 8–11 as applicable (45–90 min).
5. Paste Discord brief; do not Bob live until 10 is green.

Common mistakes

• Bundling live because “editor opened.”
• Skipping Win32 because Bob accepted win32.
• Ignoring accelerometer until player reports.
• Mixing Xbox access tickets into the same PR as CI retargets.

Working-dev pipeline order

Discord paste (creators)

Defold 1.14 upgrade — 12 free checks before Bob on live:
1 VCS tag  2 Win32→x64  3 shared Lua  4 accelerometer
5 native rebuild  6 editor plugins  7 SetRenderTarget
8 iOS IAC  9 Metal/macOS  10 ship-matrix smoke
11 forum hotfix/plist  12 Xbox = separate track
Min gate: 1–4 green. Kit: gamineai.com/blog/12-free-defold-1-14-upgrade-checks-before-a-bundle-2026

Receipt block before live Bob

Date:
Engine: 1.14.0 (+hotfix? ):
Upgrade branch:
Checks 1–12: (attach cards)
Ship platforms smoked:
NO_32BIT_BUNDLE: Y/N
Xbox in scope this RC?: Y/N
Signer:
Forum thread checked:

Failure modes

Free vs not free

RACI

Worked example — wrong “quick bump”

Setup: Producer wants cubemap blog screenshots. Engineer installs 1.14 on main, Bobs Windows with historical win32 token, skips mobile. Tilt game ships broken; Steam copy still says 32-bit.

What the kit would have forced: Branch (1), Win32 honesty (2), accel note (4), smoke (10), copy fix — before live Bob.

Receipt after near-miss: Attach failed check numbers to the incident channel; do not “fix forward” on main.

Solo vs studio

Solo: Four-check minimum same night; full twelve over a weekend. Mark native checks N/A only if you truly have zero extensions.

Studio: Producer owns live Bob; CI owns 2/10; do not let Xbox BD block 1–11.

Sibling map

When to re-run the twelve

Re-run 1–4 any time someone merges new CI YAML. Re-run 5–9 when you add an extension or plugin. Re-run 10–11 before every RC. Re-run 12 when leadership mentions Xbox in the same standup as “ship 1.14 Friday.”

Material Editor and “soft” upgrades

1.14 also redesigned the Material Editor and reduced some editor CPU work. Those are real quality-of-life wins — and they are not substitutes for checks 2–8. Do not mark the upgrade “done” because materials feel clearer while x86-win32 still sits in CI. Soft upgrades are a reward after the breaking rows pass, not a reason to skip them.

Collection capacity note (check 5 adjacent)

Generational handles come with a higher documented ceiling (up to 1,048,576 game objects per collection, subject to capacity settings and resources). That is not a license to spawn without budgets. If your design docs assume old hard limits, update them — but do not treat the new ceiling as a migration task that replaces rebuilding native libraries. Capacity is a footnote; ABI rebuild is the check.

Bundle vs editor Play

Editor Play on the upgrade branch is necessary and insufficient. Check 10 means Bob (or your real bundle path) for each store OS. Several 1.14 breaks are packaging- and lifecycle-shaped (Windows artifacts, IAC cold start, Metal default). A green Play button with a red Bob is still a failed kit.

Opinion spine (quotable)

Stop bundling Defold 1.14 over live because the editor changelog looked friendly. The free checks were always the migration list — numbered so Discord cannot skip Win32, Lua, and IAC.

Key takeaways

1. Twelve free checks before a live 1.14 Bob.
2. Minimum gate: checks 1–4.
3. Win32 → x86_64-win32; Bob win32 is x64 alias.
4. Shared Lua is mandatory.
5. Accelerometer default is off.
6. Rebuild native extensions for generational handles.
7. Update editor plugins and native SetRenderTarget if you use them.
8. IAC for iOS links; test cold and warm.
9. Confirm Metal / App Manifest on macOS.
10. Smoke every ship platform.
11. Re-read forum for hotfixes/plist.
12. Xbox is a separate gated track — primary keyword defold upgrade checklist.

FAQ

What is a Defold 1.14 upgrade checklist?

A numbered pass covering the migrations in 1.14.0 before you bundle a live project — Win32, shared Lua, accelerometer, native/plugin APIs, IAC, smoke, and Xbox scope.

What is the four-check minimum?

VCS latch, Win32 retarget, shared Lua plan, accelerometer decision — checks 1–4 on this page.

Does Bob still support win32?

As an alias for x86_64-win32, not as 32-bit. See the Win32 Stop.

Do I need Xbox access to upgrade?

No. Finish checks 1–11 without it. Public downloads omit the Xbox target.

Where are official notes?

defold.com release post and forum thread.

Is this the same as the what-changed article?

No. What-changed is the essay map. This URL is the numbered free kit.

Producer ten-minute path

If leadership only has ten minutes, force checks 1, 2, 10, and 12 aloud in standup:

1. Is there a pre-1.14 tag?
2. Did we kill x86-win32 and honest-label Windows?
3. Did we smoke every store platform — not only editor Play?
4. Are we blocking the bump on Xbox middleware we do not have?

Those four stop the most expensive failure modes (no rollback, wrong arch, untested mobile, Xbox hostage). Still run the rest before live Bob; the ten-minute path is triage, not a substitute.

HTML5 and Android notes inside check 10

When your ship matrix includes HTML5, boot once in a clean browser profile after the 1.14 Bob — watch for console warnings you already fixed on an older engine (metadata, MIME, first frame). When Android is in scope, note that 1.14 can shrink unused resources alongside Java in R8 flows; that is optional upside, not a reason to skip a store-signed install smoke. Neither platform gets a free pass because “Defold is mostly desktop for us” if the store page still lists them.

Extension author addendum (check 5 deep)

If you maintain a public native extension:

Ship the extension rebuild before you tell game teams “just upgrade.” Otherwise every studio rediscovers check 5 as a panic.

Copy-paste CI assert sketch

Not a full pipeline — a reminder to put architecture honesty next to Bob:

# After Bob emits Windows artifact:
# 1) Refuse paths containing /x86/ without x86_64
# 2) Record platform string used (prefer x86_64-win32)
# 3) Fail the job if release notes still say "32-bit Windows"

Exact shell differs per OS runner; the point is a machine-checked companion to check 2, not another honor-system checkbox.

What this listicle is not

It is not a rewrite of what changed. It is not the Win32 Stop opinion spine. It is not permission to skip reading the official migration paragraphs. Use those for narrative and refusal. Use this URL when someone asks for a numbered free check kit they can paste into Discord before Bob.

Time-box table (honest)

If your estimate is “thirty minutes including native rebuilds,” you are planning theater.

Lab doc skeleton

Date:
Lab owner:
Pre-1.14 tag:
Upgrade branch:
Check1 VCS?: 
Check2 Win32?: 
Check3 shared Lua?: 
Check4 accel?: 
Check5 native?: 
Check6 plugins?: 
Check7 RT API?: 
Check8 IAC?: 
Check9 Metal?: 
Check10 smoke platforms:
Check11 hotfix/plist?: 
Check12 Xbox scope?: 
Live Bob allowed?: Y/N

Where to leave the ship branch

Keep live Bob on the pre-1.14 tag until the twelve cards are honest. Point the team at the what-changed map for narrative and the Win32 Stop when someone proposes ia32 “compatibility.” Use the Defold guide for ongoing orientation. Paste the Discord brief if your team only reads one message. Re-run check 11 the morning you cut the candidate.