Log inGet started
World

Lantern Peak: A Storybook Mountain Platformer

Branchmain
Branchesmain
Commit10d91b3870

README.md

Lantern Peak — polish pass, before and after

Every row is something seen or measured before the change and after it, on this machine: the desktop editor on an integrated GPU, at 2097×1409. Pictures are in this folder or the listed path.

AreaBeforeAfterEvidence
Lighting per levelEvery level showed the same purple menu twilight while the keeper talked and at the startEach level has its own time of day on your machine: rosy dawn meadows, midday gorge, golden afternoon lake, violet dusk ridge with snow, starry night summit. The mood now follows the level you picked from the moment the keeper starts talkinglighting-before-one-mood.jpg → lighting-after-meadows.png, -gorge.png, -lake.png, -ridge.png
Summit horizonFrom the summit the far ranges rose as a bright summer-green horizon at eye levelThe far ranges are off, so the lantern stands on a snowy spire above a sea of haze. That is also one terrain fewer to drawsummit-mood-v1.jpg → summit-mood-v2.jpg
ControlsSeveral installed controlsKit copies kept switching each other's platformer scheme off, so the apprentice walked at the engine's 2.5 m/s and the kit-sized gaps couldn't be clearedThe scheme stays on; the controller reads 6.0 m/s at full stick (measured velocityZ = 6.0)fix sent upstream (controlsKit PR #1, Summit Sprint PR #1)
First minutesThe game dropped a new player straight into level 1 on joinThe title screen comes first, then the trail map, then the keeper's send-off and the 3-2-1-GO (platformer3dKit autoStart = false)played in the editor: title → map → send-off → intro → countdown → run
Juice: jump, landing, checkpoint, deathSilent: no kit played themEach has its own sound (audio/sfx_*), plus the kit's dust puff, landing kick, checkpoint flag, confetti and slow-motion finishshell/audio
Juice: hazardsAll 8 hazards were silent14 spatial sounds: snowball roll and burst, icicle crack and shatter, wind gust, vent rumble and burst, avalanche, rockfall, thin-ice crack and break, frost spikesfrostHazards 1.1.0 sounds/
ModelsBox-built stand-ins for the great lantern and the 13 finish lantern postsA generated stone-and-brass lantern tower (~11 m) and a carved post with a brass lanternlook/captures/polish-greatLantern*.jpg, polish-lanternPost-meadows.jpg
SurfacesSnow deck tops rendered tan-brown under dusk and night light; the lake floes read as stoneSnow-white decks with lavender shade; teal ice floes with snow on top; storybook steam ventslook/captures/ (polish-surfaces)
Story flowPressing Next on the summit's results card before the keeper finished skipped the whole ending and looped to level 1; after the ending the apprentice stood back at the trailheadNext on the summit's card goes to the finale, and the apprentice stands by the great lantern while it is litplayed: results:summit → finale:summit
Performance: coins177 coins each ran their update every frame: 9–20 ms a frameCoins more than 60 m from every local player update one frame in ten: 1.4 msprofiler scripts; fix sent upstream (pickupsKit)
Performance: shadowsThe shadow raster was 160 ms of a 225 ms GPU frame; 322 shadow pages and 2.88 M triangles drawn each passDistant shadow detail one step coarser, with small and far casters cut off: 26 pages and 0.83 M trianglesrenderer.shadowPageStats()
Performance: platformsAfter a scene rebuild, every moving platform logged hundreds of errors a second writing to its deleted partsPlatforms rebuild their look when it was removed, and the error stream stoppedfix sent upstream (platformsKit 1.6.2)

Still slow on this machine

On the integrated GPU in the editor, frames still run 60–300 ms: the forested mountain at full window size, plus the editor itself. alpineKit's own README measures its showcase mountain at about 70 ms a frame on the same class of GPU. The game's own scripts now come to about 15–40 ms a frame, most of it the kits' per-frame work. A dedicated GPU, or a smaller window, is what a smooth frame rate needs here. The web build also carries #20750 and #22751.

Polish pass 2 (2026-11-08 afternoon)

AreaBeforeAfterEvidence
Controlsplatformer3dKit's feel option promised coyote time, a jump buffer and air control, but applied nothing (engine defaults 0.1 s / 0.1 s / 0.3)0.15 s coyote time, 0.15 s jump buffer, 0.6 air control on every playerread back from the controller in play; platformer3dKit 1.3.4
CameraThe follow camera's sweep stopped on every trigger (232 kill zones, coins, flags, finishes) and snapped in toward the apprentice whenever one sat between them; no look-aheadTriggers are see-through; the view leads the run by up to 1.8 m so the next platform is in frame before the jumpcamera follow = lead point, cameraIgnore 232 in play; 1.3.4
Camera hitchThe see-through list was rebuilt by scanning every entity every 5 s: up to 1,029 ms framesRebuilt from the component index in ~0.2 msprofiler scripts max; 1.3.5
JuiceJumps, checkpoints and deaths had sounds onlyTake-off dust on every jump, a sparkle burst at each flag, a smoke puff and a light shake on a fall (landing dust, confetti and slow-motion finish were already there)juiceKit effect count +2 per jump in play
First levelFirst pit 1.7 m (a running jump reaches ~2.1 m: 0.4 m margin); four stepping stones zig-zagging up to 1.6 m sidewaysPit 1.2 m, stones nearly in a line (0.6 m wiggle), same 1 m hopsmeasured in play: gap 1.2000 m; levels/meadows
Touch controlsA diamond of four buttons (jump, dash, interact, crouch), two of which do nothing in this gameOne big jump button; dash and crouch removed from the schemeGameDirector scheme override
Mood arcLake: plain afternoon; summit: starry nightLake: golden hour; summit: aurora night, so the day climbs dawn → midday → golden → snowy dusk → auroramoodkit-lake-after.jpg → look-lake-after.jpg, moodkit-summit-after.jpg → look-summit-after.jpg; art-direction.md
MenusAfter play → edit → play the title never came back (campaign resumed a stale state); title "Play" with a save skipped the map; lives hearts showed with unlimited livesEvery session opens on the title; Climb! opens the map; no lives HUDcampaignKit 1.0.1, campaign-title-after.jpg, campaign-map-after.jpg
Par timesGuessed: 75 / 110 / 120 / 140 / 160 sFrom measured speed (4 m/s), jump (2.1 m) and each route's length and climb: 55 / 75 / 55 / 90 / 130 s (Meadows 136 m, Gorge 128 m + 34 m climb, Lake 99 m, Ridge 145 m + 46 m, Summit 150 m + 128 m)LanternPeak.game
Clock kitAn update mixed two versions of worldClockKit; WorldClock failed on start (no time of day, no moods)Consistent 1.6.2 files; WorldClock wakes at 6.6 h on Meadowsmodules.diverged() empty, WorldClock enabled

Frame time and memory on this machine

The engine here is a debug build on an integrated GPU, running the editor plus the game: 175–215 ms frames in a level (Luau scripts ~10 ms, render ~30 ms, the rest engine and editor), 200–750 ms on the title (menusKit's MenusHost ~70 ms). Memory: 6.5 GB process (editor + game), 3.8 GB graphics, 610 MB Luau heap. These numbers are for comparing before/after only; a release build in a browser tab runs the game without the editor.