Hacker News new | ask | show | jobs
Show HN: LMAO – Temu League of Legends, Built with Opus 4.8 (lmaomoba.com)
4 points by jonnyasmar 9 days ago
Fun weekend project just to test out 4.8 against a pretty vanilla setup.

Started out with a simple prompt, "build a temu league of legends, web-only with online, room-based multiplayer".

It built it... fully functional in one shot! Then I went kinda ham and started iterating on every aspect little by little. I made it spin up subagents to each focus on designing a character. Spun up subagents to focus on designing abilities and their SFX/VFX. Did a few passes over the map, mobs, minions, etc.

Then I put Ultracode Workflows to task and, across a handful of prompts, had it optimize performance, balance, and a variety of other things. Workflows is insane btw...

I also used /goal pretty heavily as well. I'd sit and play and make note of like 10-15 tweaks, bug fixes, etc at a time and just let it go to town.

4.8 is a one shot machine... 5.5 ain't doin this...

Anyways, figured I'd share. Happy to answer any questions in the comments!

Try it out solo (with bots) or with friends! https://lmaomoba.com

Stack - Web: React/TypeScript - Game: Canvas - Server: PartyKit - Harness: Claude Code - Model: Opus 4.8 - IDE: atrium (getatrium.dev)

2 comments

Amazing and Atrium looks great too! Where is it better to follow your work?

For Atrium you said that you save everything on disk. What usecases did you find toy have your old sessions saved?

Thanks! So the persistence is universal. atrium allows you to instantly pick up where you left off across all of your projects/sessions/etc. Start a conversation, leave it to work on something else, restart, and it auto-resumes so you can pick it up again later. Additionally, your sessions are indexed to allow for FTS and every interaction is stored in a timeline that you can use to easily (re)orient yourself in any project.

Happy to go into more detail, but that's kinda the high-level of the persistence story.

How long did it take you to make this? Are you going to write about your process and any challenges you had?
Honestly, it was about 4-6 hours of hands on keyboard. Bout a day and a half overall with a handful of smaller tweaks/bugfixes since then. I am definitely planning on writing about it. tl;dr this was sort of glorified vibe-coding and intentionally so in order to really see what 4.8 was capable of. But I do have some interesting observations that I made along the way that I'm going to go into more detail about.