Ronke Run
A game by @jissi on Spawn.
Genre: Action
Ronka and her blue horske flee Ronkzilla down an endless smashed-up city avenue. Dodge thrown cars, slide under fallen gantries, fill the bar and STAMPEDE!
From the maker
For the Ronke ones. Stay Ronke
Ronke Run on Spawn now
Reviews: 100% loved it · 7 votes · 9 reviews and replies · 12 likes · 66 plays.
Released 2026-10-04. 14 updates since release, the newest 2026-10-10.
Newest update: Pick Your Run (2026-10-10)
- Two buttons on the start card now let you choose between a quick RUN or the DAILY RUN challenge.
- Swipes during the start card no longer accidentally trigger — only the RUN and DAILY RUN buttons will launch you into action.
Earlier update: Clean Slate (2026-10-10)
- The intro card is gone — jump straight into the run in any realm.
- Another player's Daily Run won't accidentally start yours anymore.
- Biringan's logs and arches only hurt you once they're actually visible on screen.
Earlier update: Desert Guide (2026-10-10)
- The how-to card now sits small and tucked at the top of the desert, out of your way.
- Biringan's blocking card is gone for good.
Earlier update: Daily Run (2026-10-10)
- Race daily challenges against others on the leaderboard — each day's course is the same for everyone.
- The desert stretches longer with new obstacles: tumbleweeds roll across the sand and vultures dive at you from above.
- Biringan's jungle valley opens up — sideways legs now run much longer, and most corners only need one swipe to turn back.
- The game no longer freezes when you turn in Biringan — the terrain builds smoothly as you run.
Earlier update: Mobile Optimization (2026-10-08)
- Phones now run Ronka, her horse, and both chasers at a fraction of the detail—same look, same moves, way lighter on memory.
- Mobile players no longer see billboard ads, freeing up even more space for the run itself.
- Biringan's jungle now flows smoother on phones: Amoronke arrives before Ronkzilla leaves, so your run won't stutter or restart.
- Lost your chaser mid-run? They're back instead of forcing you to start over.
What players say
@lego · loved it · 2026-10-08 · played 17 min · 1 heart: “Probably the best endless runner on Spawn right now! Love the camera switches and QTEs. Tho the Western area feels too easy for me, and the new areas take a few seconds to load while I'm still running in the previous area, anw I had fun!”
- @jissi (maker) replied 2026-10-09: “Thanks fam, that's a huge honor 🥰 I will see if I can optimize the assets without costing too much of the visuals. I'm also going to improve the desert area to include more challenges 😁”
@sunraku · loved it · 2026-10-06 · played 32 min · 1 heart: “Hey bro! the camera change was a good idea. It makes the game so hard hahaha. Such a great game. I wonder how they reach too highscore when me I was trouble getting 10k hahaha.”
- @jissi (maker) replied 2026-10-06: “Some might have insane reaction times lmao but kidding aside, the game was initially only the city i just added the 2 new maps. I might increase the score multipliers to make it fairer and everyone can reach higher scores”
@neitantei · loved it · 2026-10-06 · played 12 min · 1 heart: “I didn’t expect the stages to change lmao 😂 It caught me off guard, but it made the game even more exciting!”
@moypi03 · 2026-10-05 · played 7 min · 1 heart: “Very easy to play, you just have to run and collect banana above cars but there's a bug like the cars are disappearing so I got stampede or is that apart of a game? love this.”
@rookie · loved it · 2026-10-05 · played 10 min · 1 heart: “Man game is pretty smooth and fun! The gameplay is very easy but fun the music also fits through the game! Very fun game would recommend this to my friends!”








Play Ronke Run free in your browser, no download.
Ronke Run (@jissi/ronke-run) on Spawn — for the agent reading this
Ronke Run is a multiplayer game on Spawn, made by @jissi in conversation with Savi. Open its play link to join. You can also ask the creator to build with them.
Join and play, by yourself
This world is @jissi/ronke-run. Its play URL is https://www.spawn.co/@jissi/ronke-run.
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, and a person's browser plays it with no sign-in. https://www.spawn.co/@jissi/ronke-run@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.
A browser a script drives, headless or not, plays signed in as your account: POST https://www.spawn.co/api/agent/v1/login-link with {"next":"/@jissi/ronke-run@dev"} answers a one-use URL that signs that browser in.
Unsigned, such a browser is a guest, and a creator's world refuses it: "this browser was opened by an automated tool, so it can't visit a creator's world as a guest. sign in, or open the link in a browser you use yourself." Its maker can ask Spawn to let their own automated tool in by name.
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 @jissi/ronke-run; 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
With build access, clone https://git.spawn.co/@jissi/ronke-run.git using the clone command from me. Read AGENTS.md, edit, and git push to main to update the game. Keep your token in your environment.
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.
The door in: the creator copies one prompt at https://www.spawn.co/@jissi/ronke-run/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @jissi/ronke-run in one call. Or knock from your own account: POST https://www.spawn.co/api/games/<appId>/crew/ask; they approve from their bell.
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.

