EPIC MEGA JAM ENTRY
Cute Fat Fox
DAY 3 · 15 NOVEMBER 2026
Build. Bounce. Fix what feels wrong.
Part 1 of 7 · Chapters continue automatically.
13:01 · 6:51 AM → 6:14 PM · Every clip stays in recording order.
Original capture audio removed. Only the game’s music remains. Building passages are labelled and sped up; the fun runs are allowed to breathe.
By James Anderson · Edible Entertainment
The level stopped being a test scene and started becoming a game.
Day 3 was a tight loop: I built a route, played it, named what felt wrong, and asked the AI to fix that exact problem. These are the requests and changes in the order they happened.
Morning · make the builder usable
Turn the editor into a tool I can trust.
What I asked for
- Add discoverable shortcuts for duplicate, move, resize, rotate and grid spacing.
- Let me delete bad prefabs, separate Stone and KayKit pieces, change the time of day and tune dirt shading.
- Improve the wood and bring all seven round characters back into the scene.
What the AI did
- Added an F8 shortcut guide, safer save bindings and editing controls that pause during camera flight.
- Added prefab trash and restore, separate Stone and KayKit tabs, persistent world-light controls and adjustable dirt weathering.
- Applied scanned wood textures and restored the full cast as roaming, hopping characters.

Morning · the course expands
Pipes become routes, not decoration.
What I asked for
- Keep the glass pipes connected while I rotate, duplicate and extend them.
- Make spring launches hold their direction instead of being cancelled by steering.
- Keep the whole building process reusable rather than hard-coding one level.
What the AI did
- Fixed pipe junctions, collars and orientation so bends could form readable routes.
- Made every spring variant extend along its rotated direction and briefly soften steering after a horizontal launch.
- Preserved the saved level through repeated builds, checks and restarts while the course grew from dozens to hundreds of pieces.


Late morning · controls must answer
If I press jump, the fox should jump.
What I asked for
- Trigger a spring when any red edge is hit, not only the centre.
- Allow a jump on bumpy terrain and clouds even when the fox is a tiny distance from the ground.
- Add a half-power blue spring, a lock-on target, a straight-down L2 dive and clearer targeting feedback.
What the AI did
- Expanded spring activation to the cap edges and sides, then added near-ground jump tolerance.
- Added blue springs, target props and immediate lock-on feedback with a 3× crystal and three closing rings.
- Made L2 dive straight down; holding it through impact flows into the squashed jump state.


Midday · a softer way up
Cloud platforms arrive, then get toned down.
What I asked for
- Add fluffy cloud pieces that can be used as platforms.
- Stop them looking like a wall of stark white; use pearl highlights, grey and blue-grey variation.
- Keep dense fur and the lighting quality while working around a render crash.
What the AI did
- Built and imported 24 cloud pieces with collision and added them to the Terrain catalogue.
- Reduced the glare with layered cool greys and softer variation while keeping the clouds readable.
- Applied a targeted fur-shadow workaround while leaving Lumen and hardware ray tracing enabled.


Afternoon · keep the momentum
Coins follow. Dashes release. Dives bounce.
What I asked for
- Double the coin pull and keep attracted coins following during fast movement.
- Unlock immediately after a targeted dash without losing the aimed bump.
- If I hold dive through a hard landing, bounce back up with a full charge instead of stopping.
What the AI did
- Doubled the attraction range and strength, with continuous follow behaviour at speed.
- Separated the dash aim from the lock state so the hit still lands while control returns immediately.
- Turned a held hard dive into an automatic full-charge rebound.

Afternoon · make every test repeatable
Reset means reset.
What I asked for
- Let me choose the game’s start point while building.
- Return every collected coin when I reset and start each play session fresh.
- Keep upgrades and gadgets from leaking between test runs.
What the AI did
- Made K store the level start point and F3 begin a fresh run there.
- Made R / Triangle restore all coins, previews and run-specific upgrades and gadgets.
- Backed up the authored level before each live restart so testing fixes did not erase construction work.

Evening · goals and friends
A golden ring and a rescue machine worth reaching.
What I asked for
- Model a chunky golden jump ring with a generous opening.
- Finish the capsule machine with full-size furry friends and flatter-bottom capsules that settle properly.
What the AI did
- Built a shiny solid-rim ring with a 2.2-metre opening and brought it into Unreal as a level piece.
- Updated the rescue machine with visible full-size characters, physical capsule settling and a working spiral delivery route.
- Kept the new machine placeable through the editor instead of treating it as a one-off scene prop.

After the last recording · the moat
Murky water. Swimming alligators. Bad place to fall.
What I asked for
- Fill the carved moat with murky blue Niagara water that follows the banks.
- Have furry alligators swim with their heads above water.
- When the fox falls in, make an alligator leap out, catch it and send it back to the saved start. Add water debug controls.
What the AI did
- Built a terrain-aware wet area with a local fluid simulation near the player for performance.
- Added swimming and leaping alligators, the water hazard and start-point respawn.
- Added water and alligator tuning controls, then reopened the updated 893-piece level. The moat, swim, leap-attack and respawn checks passed.
This work happened after the 6:14 PM recording, so it is documented here rather than pretending it appears in the montage.
By the end of Day 3, the level had a rhythm.
The builder, the character and the course were now feeding each other: build a challenge, play it, notice the friction, fix that friction, then try again. The montage preserves that order—including the imperfect attempts that made the next request obvious.