Development log · UEFN · Director’s Cut

King of
the Cinder

Race the canyon. Survive the Killing Fields. Claim the tower. Three acts, one continuous battle.

Fortnite island code: 7230-6949-1801

By COLTRAN Studios · Living dev log · Latest post November 16, 2026

Latest post · November 16, 2026

It is rough. It is real. It is fun.

We shipped something unfinished—and found the reason to keep building. A full illustrated look at the jam, the cuts that helped us finish, and what comes next for co-op, Epic support and a dependable MVP.

Read the full post → · Game on itch.io ↗ · The contest ↗

Earlier post · November 15, 2026 · Development retrospective

The director’s cut

We interpreted “Director’s Cut” as giving the creator the final say over a game idea that hadn’t yet been built. The founder’s vision was a battle royale that changes its movement and combat across three connected acts: a vehicle-combat race through a canyon, an on-foot crossing of the Killing Fields, and a vertical fight to claim the Power Tower.

The theme influenced both pacing and production. Players leave their cars without ending the match. The distant tower gives the journey a destination. During development, the human creator directed the design and tested the results, while AI agents helped implement and revise it. We cut back an elaborate garage to protect the driving-and-shooting core and make the complete journey playable.

The target is 64 players competing in one shared themed slice per match. Additional slices and randomized courses remain part of the larger vision, not a claim of completed content.

Iteration 01

Prove the vehicle combat

The first requirement was specific: one player must steer and shoot from the driver’s position. We explored a sports car with custom driver firing, a tank, a motorcycle-based car body, and a boat with cosmetic wheels. Each exposed a different trade-off in handling, aiming or presentation.

We returned to the original sports car. Repeated parked and moving target tests led to aiming that the creator confirmed matched the crosshair. A decorative cannon slid and flipped, so it was replaced with a native roof-mounted launcher attachment. The creator confirmed the mount stayed attached and both weapon modes fired.

Make every shot readable

Custom blue rocket and tracer meshes made shots easier to follow. Blue rocket bursts and sharper machine-gun hit flashes added feedback at impact. The creator confirmed that the projectiles and effects were visible and aligned. Those are recorded playtest results, not a guarantee that every later revision has been retested.

Iteration 02

Build the three-act route

  • Zone 1 — Canyon race: a main road, an off-road branch, checkpoint boosts and a chasm shortcut. Vehicle weapons and mods are collected while driving.
  • Zone 2 — Nuke1 / the Killing Fields: a desert testing-site town with combat, obstacles, weapon supplies and vertical traversal toward the tower.
  • Zone 3 — Power Tower: a neon landmark with stairs, grapple targets and elevated platforms, ending in uncontested summit defense.

The creator completed the route and reported that summit victory worked. Boost pads were revised to expire after four seconds without stacking or extending; that expiry was also confirmed in a playtest. Vehicle handling and overall race pacing remain tuning work.

Iteration 03

What we changed—and what we cut

A simpler start

The staged, live-preview customization garage became slow and unreliable. Missing car previews and failed handoffs interrupted testing. We simplified the frontend to choosing one of three cars, confirming READY, and entering a flat starting grid. Weapons and mods move into the race as pickups.

Public camera compatibility

A cockpit camera went through several positioning and stability revisions. Experimental camera APIs then blocked public publishing. The creator approved the standard third-person vehicle camera for the public release, preserving driving and weapon functionality.

Latest build notes

Pickups, replay and persistent clocks

0.11.7 — Supplies and replay

Added 27 native weapon spawners across nine exposed Zone 2 supply clusters, including rocket launchers and rifle, shotgun and sniper choices. Added 16 vehicle weapon crates across eight starting lanes. Recorded real driving pickup events for the rocket, machine gun and off-road tires.

A private test verified that a Zone 1 timeout returned the player to car selection and started another race without reconnecting or reloading the world. Summit victory uses the same reset function, but that path was not separately reverified in this revision.

0.11.8 — Keep time visible

Persistent UI replaced transient timing messages: Zone 1 has a two-minute deadline, Zone 2 has one minute from entry, and Zone 3 displays its existing 30-second summit-defense timer. The defense timer counts during uncontested control; there is no separate tower-climb deadline.

Verse compilation passed, and the Zone 1 display was observed counting down in private play. The Zone 2 and Zone 3 display logic compiled but was not separately replayed in that verification pass.

Release checkpoint

Recorded November 15, 2026: Release 1 was publicly playable under island code 7230-6949-1801. The 0.11.8 update was submitted for automatic publication after Epic review; its last recorded state was pending / processing.

The update passed Creator Portal validation: 2.24 MiB download, 117.91 MiB against a 300 MiB memory limit, no reported asset issues, and completed Verse compatibility checks. Memory validation is not an FPS benchmark.

This is a dated development record, not a live release-status feed. Search the island code inside Fortnite to find the currently published version.

Tools and human direction

Built with Unreal Editor for Fortnite, Verse, Fortnite Creative devices and standard Epic assets, UEFN Scene Graph and asset reflection, editor MCP tools, Python and PowerShell scripts, Fortnite private sessions, and Epic Creator Portal. The blue rocket and tracer geometry was generated procedurally in Python and imported into UEFN.

OpenAI Codex/ChatGPT assisted with implementation, debugging, editor automation, procedural asset scripts, documentation and test coordination. The creator supplied the vision, made manual map edits and performed hands-on acceptance tests. OpenAI inference is not integrated into gameplay; enemies use Fortnite’s native AI. Historical model identifiers are not reliably recorded.

No Hyper3D Rodin use is recorded. No RTX Mega Geometry, DLSS Frame Generation or Ray Reconstruction integration is claimed. Game VFX and engine graphics capabilities are not evidence of a verified RTX implementation.

What still needs proving

Two-human countdown synchronization, vehicle combat and contested summit defense still need a verified multiplayer pass. The 64-player setting is a configured target, not a completed 64-human load test. Full-route timing, handling across hardware and later release approval require additional evidence.

This retrospective was consolidated from versioned build notes, implementation artifacts and creator playtest reports. It distinguishes what was built, what was tested and what remains open.