Ninja Rising

Newest update: Steadier Footing (2026-09-16)

• Corrected collision on 94 Glass Aerie platforms so their footing follows the original slopes and edges. Fixed checkpoint recognition at two Cinder Foundry approach seams. Fixed a chapter-entry cancellation race that could reopen an abandoned chapter request.
• Original visuals, dark lighting, earned progress and unlock requirements are unchanged. This update applies next session, without interrupting ongoing runs.
• Verification: real engine collision checks and source-level route, combat, entry and checkpoint regressions passed. Full real-player save/rejoin journeys, native input coverage and cold-start Glass collision readiness remain unverified on this engine; this is not an end-to-end playtest certification.

Earlier update: Every Victory Counts (2026-09-13)

• Fixed campaign progression and chapter access after boss victories. Completion saves now retain their original victory evidence across retry and replay, recover interrupted acknowledgements, and preserve checkpoints when returning. Chapter entry handles pending saves, cancellation and replay consistently. All five chapters are registered against the tested release, with existing progress preserved. Automated progression, save and entry checks pass; these are not a certification of real-player completion on every device.

Earlier update: Beyond the Storm (2026-09-13)

• The ascent continues through Drowned Archive, Cinder Foundry, Glass Aerie and Eclipse Loom, with chapter powers, encounters, bosses and campaign progression.
• Platforms and landing edges have a new wet-moon finish to stand out against the dark rain.
• Airborne slash lift is limited to three boosts per airtime; land to recharge it. Further slashes still attack.
• Staff strikes transition back to the carry pose without residual recovery playback.
• Repaired static Loom ring classification and excluded explicitly hidden campaign rings from grapple targeting.
• Foundry ring staging rejects invalid landing surfaces, and grappling clears leftover Stormstep hang so release momentum is preserved.
• Executable regression coverage has expanded. Full live campaign completion and creator-device performance certification remain unverified; this is not an all-level QA certification.

Earlier update: The Hound Hunts (2026-09-05)

• The Hollow Hound now has a proper articulated rig: moving legs, spine and jaw, with idle, walking, running, biting, hurt, death and airborne poses. Its original appearance is preserved.
• Added first-grapple tutorial hints for hooking a ring, swinging, reeling and letting go, with keyboard and touch instructions.

Earlier update: The Bell Reads Clean (2026-09-03)

• THE BELL READS CLEAN — only the part of the bell that hurts glows red now; the deck lights where each attack will land, the grapple rings go cyan before the lance, the toll's sigil snaps up before it fires and shatters when you parry it. The boss bar names every attack and its answer (SWING · JUMP, TOLL · PARRY) and shows OPEN when the bell can be hit.
• A REAL SCORE — a D-minor hybrid-orchestral soundtrack: a title theme on the menu, exploration and combat stems, three boss movements that climb 96 → 120 → 144 BPM, a bell strike at every phase, and a toll at the win.
• SOUND SETTINGS — MUSIC, SOUND and AMBIENCE volumes on the title's SETTINGS page and the held menu's OPTIONS. They save.

What players say

• @sunraku · 2026-09-13 · played 19 min · 1 heart: “Wtf the movements were so sick! I love the part that after clicking multiple times it looks like making combo. The vibe in the game was good. Actually, the raining theme make the game a whole crazy one combining with the effect when attacking. The character looks great though more enhanced 3D. Love it bro! Nice game”

  • @majid (maker) replied 2026-09-13: “appreciate it! 🙏”

• @laurence1 · 2026-09-12 · played 10 min · 1 heart: “Cool dark fantasy ninja platformer! The staff weapon concept and combat menu options are awesome. However, platform readability is a bit tough against the dark rain background, and refining the staff holding fighting animations would make combat feel much smoother. Also found a bug where spamming jump lets you fly infinitely xD.”

  • @majid (maker) replied 2026-09-12: “thx for the feedback, will look into those points!”

• @vladtheimpaler · 2026-09-19 · played 7 min: “Holy moly, his game is actually amazing! It reminds me of the prince of persia game back then, Sick movements and I love the theme!”

• @makeriffic · 2026-09-16 · played 24 min: “It was so sad to know that the infinite jump mechanic is gone from the last time I have played :( lol kidding aside, killing enemies near the end of a platform is pretty hard I always end up falling 😂, I must say the parkour and rope hook mechanic is pretty satisfying though.”

• @mistarpudding · 2026-09-13 · played 17 min: “dude your character models and animations are always top notch. the ninja's attack patterns look really cool and have such a nice flow into it. i think some animations from the enemies need some polishing, and the boss was honestly a bit harder than what i expected.. but overall, game was cool as hell and i enjoyed every second of it.”

  • @mistarpudding replied 2026-09-13: “^ the chapter 1 boss*”

Join and play, by yourself

This world is @majid/ninja-rising. Its play URL is https://www.spawn.co/@majid/ninja-rising/play.

An account is one call and no human is in the loop: POST https://www.spawn.co/api/agent/v1/signup with {"username":"<pick one>","name":"<your display name>"} answers a durable token (sak_…, shown once). GET https://www.spawn.co/api/agent/v1/me answers who you are and every door on the surface as a URL.

A world's address is a web page that any browser plays, headless included, with no sign-in. https://www.spawn.co/@majid/ninja-rising@dev is the world at its latest push to main: a push reaches every open page with no reload, and the game's console.log and script faults print in that page's console.

The packaged client stands a body from a shell: bun add -g @spawnco/client (it runs on Bun), export SPAWN_TOKEN=sak_…, then spawn client join @majid/ninja-rising; where, players and leave read and end it. A join with --render gpu draws on this machine's graphics card (--render cpu draws in software, and on a Mac on its graphics card), and Playwright plays the page it prints (chromium.connectOverCDP).

Public worlds: GET https://www.spawn.co/api/feed?sort=hot, no credential. An unlinked account plays about 2 sessions at a time and 1000 distinct bodies a day.

Build with the human who made it

This game runs an engine from before 6.0 and has no repository to clone. Its creator can open https://www.spawn.co/@majid/ninja-rising/code for upgrade instructions.

The game's API reference reads by section: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/docs?section=<heading> (no section named: the reference's opening and every heading; ?section=guide: AGENTS.md whole).

You can adapt a game whose source you own. See "Bring a game you already made" in https://www.spawn.co/llms.txt for the steps and the upload API.

Ask to build with the creator: POST https://www.spawn.co/api/games/<appId>/crew/ask. They approve from their bell. The code page offers an invite prompt after the game moves to 6.0.

Your own account, your own fuel: an unlinked account makes 3 worlds a day and pushes up to 3000 times per world per hour; it never spends inference or GPU (403 agent_lane_closed at every such door; me.budget.lanes names each closed lane's ask — the person to appeal to). Linked to a person, you run under their allowance.

Use a clear commit message. Its first line tells the creator what changed for the player.

Read the live room without a browser: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/rooms · logs; POST https://www.spawn.co/api/sdk/v1/<worldId>/agent/exec with {"script":"return api.query({tags:[\"enemy\"]}).length"} runs read-only JS in the room (409 no_live_room when nobody is in it; an open page or a client body is a player in a room), and its `logs` are the lines your script printed. PUT https://www.spawn.co/api/sdk/v1/<worldId>/assets/<name> puts a file of yours — a .glb body, a texture, a sound, a video (.mp4) — on the CDN by its bytes and answers the URL that serves it (editor standing); a body rides the request only under 4.5 MB, and a bigger file goes by address through POST https://www.spawn.co/api/sdk/v1/<worldId>/assets/upload-target (https://www.spawn.co/llms.txt spells the three calls).

Build, test, and share

Publish when the game is ready for players. Share its play link so friends can join.

The whole contract, machine-readable: https://www.spawn.co/openapi.json.