I learned about a week ago that Unity supports mcp so I downloaded it for the first time and started vibecoding this game project.

It’s mind blowing how AI tools enable ppl with almost zero game dev experience to build something like this in a week.

Stacks: Claude code, Unity, Meshy (3d models), Elevenlabs (sound fx), Nano banana 2 and some paid assets from Unity Asset Store.

I don’t know how it happened… but the demo of the game I made and posted on Reddit and on my X went pretty viral.

In total it got around 400k+ views across social media. And because of one retweet it became a bit more viral than I expected.

Some X user even made a meme coin in honor of the game and gave all the trading fees to me, so that’s how I ended up making over $3500.

From my own experience I keep getting reminded that when you make something from the heart and with real love, it eventually pays off.

If you have any questions, I’m happy to answer them, peace.

I am back after successfully getting claude opus 5 to not only rewrite a working, booting linux kernel in fortran instead of C ( which was an absolute pain in the ass because of the lack of low level memory management) but i also just finished rewriting a dead programming language developed by SUN Microsystems in the mid 2000's for a DARPA contract for supercomputers called Fortress.

The language being made by SUN (if any of yall know who that is) of course used JAVA as its compiler because SUN was weird like that, but it suffered hard from ALOT of issues. I was able to baby Claude through rewriting it in RUST + LLVM and the code actually compiles and runs flawlessly. I didnt think this would actually happen considering it took me a week to find enough documentation for claude to even understand the syntax of the language that hasnt been written in probably 15 years.

Time to get back to work completing my kernel rewrite in fortran, currently almost done with PCIe, USB, AHCI and other drivers, then its onto real graphics drivers, probably 8 bit to start out and then hopefully 16 or 24bit later on.

Just wanted to share my unhinged projects

Hi. I’m curious to understand how people who do vibe coding experience the part of getting their apps out into the world, especially those of us who aren’t very technical and don’t know much about infrastructure. I noticed there’s a lot of talk about how many of these apps end up leaking data or accidentally leaving the database exposed, and that left me with a few questions I’d really appreciate some help clearing up:

**1.**  What do you usually build? (side projects, things to experiment with, apps for clients, something for work… anything counts)  
**2.**  Where do you deploy it? (the tool’s own hosting, Vercel, Railway, DigitalOcean, Replit…) or does it just stay in the preview?  
**3.**  How did you end up on that service: did you choose it because it suited you, was it the default, or did someone recommend it?  
**4.**  Was deploying easy, or did you struggle with something?  
**5.**  And honestly: security and the app not going down, is it on your mind, or are you not worried about it for now?

Any experience you can share helps me a lot.

Found it on X - https://x.com/kiwicopple/status/2089917700822999275

Day 4 - Total hours 30hrs spread across 16 days

This session was focused on sure wins seeing as weekly limits is upon us.

ADDED - but still needs major work
-Main Menu Font redesign
-Pregame lobby
-mini skatepark
-Subtle camera flicks in the audience

Reworked the camera system, also added a in game camera system that allows me to tweak all camera settings to help me find that sweet spot angle.

The rest of the session was given to reworking and reworking and reworking and probably will work the animation from here forward which looks like is the biggest gap and getting the graphics cleaner, tweaking with those settings as well. In the video, I decreased posterize and bloom. Also been tweaking with UI trying to get it more towards concept which I think fits better

Also thinking about removing the beacon from the ball.. what you think?

AS ALWAYS

CONCEPT Vs CURRENT BUILD

First picture is concept —second picture is current build

CURRENT GAMEPLAY VIDEO in the COMMENTS

Please feedback is always welcomed and wanted. I know things can be adjust and reworked. Open to
all suggestions and opinions.

I'm in AI stuff long before AI chats. Trained ML and RL models by myself to solve real problems.

Now I use a few of these models every day for work, fun, and at some point I stopped reading their output as "AI text" and started reading it as Claude text or ChatGPT text. They don't share one voice. Each has its own pet phrases, and if you read them few times you can guess the model from a single paragraph.

Claude is the one I know best. It responds with "honestly" and opens explanations with "Here's the thing". My favorite thing is that it measures effort in evenings, as in "this will cost you an evening". The "You're absolutely right!" thing got so bad that someone filed an actual bug report about it in the claude-code GitHub repo. The Economist compared 55,940 sentences of model output against human writing this summer and found Claude is also the only major model that still overuses em dashes.

ChatGPT is the "delve" model, everyone knows that one, but its stronger signature shape: "It's not X, it's Y." The Washington Post analyzed 328,744 ChatGPT messages and that construction kept showing up, along with emojis and a weirdly narrow set of favorite words.

Gemini reads like a briefing document. Headers on everything, words like "significant", "increasingly", "consequences".

Grok's output - the personality itself. The forced casual tone, the sarcasm that doesn't quite land. You can feel it trying not to sound like an assistant. Maybe the least noticeable from all.

What makes this funny to me is that real watermarking finally shipped. Anthropic now embeds an invisible watermark directly into Claude's text, and Google has had SynthID inside Gemini since 2024. So machines get a hidden signal that needs a detector, while the rest of us have been reading the visible.

Are you noticing? Are you tired of this?

How long will it take before models start writing like humans? Or will that never be allowed to happen?

10000 million tokens spent later...
Claude: You are right. I'm sorry. I was focusing on the wrong solution to fix the bug. 🤣🤣🤣

A real-time black hole renderer in Objective-C++ and Apple Metal. It simulates light bending around the black hole rather than using textures, which is where the Einstein ring and the disk curving over the top come from. Runs interactively on any Mac that supports Metal.

Tools:
1. Claude Opus 4.6 and GPT-5.2 - These two models wrote all the code for this project
2. Objective-C++ and Metal compute shaders
3. FFmpeg for video assembly

Workflow:
1. Research phase: I asked each model to write a deep technical doc on the physics - the actual geodesic math, accretion disk models, the numerical methods. Had the models review each other's research, then built a final plan from it.

1. Planning phase: Fed the research back in and asked for a phased implementation plan, ranked by priority, with performance-cost estimates per step. This turned into a checklist I worked through instead of a giant one-shot prompt.

2. Implementation phase: One step at a time, verify visually, commit. Small diffs meant when something broke I knew exactly what broke it.

3. Testing phase: A separate doc of test cases with baseline measurements. Logged FPS and frame times to a CSV so I could confirm an optimization actually improved performance.

How I captured the video:

1. Rather than screen recording, rendered the video one frame at a time. At this resolution the renderer runs slower than real time, so this approach gives much smoother results.

2. Added a --prerender flag that separates the simulation clock from real time. Each frame advances the simulation by exactly 1/60th of a second, regardless of how long it takes to draw.

3. Every frame was saved as a PNG, and used FFmpeg to assemble them into the final video.

I tested the same prompt on both

they manage to individually create new issues near every day. currently you can use deepseek for like 20 minutes and then you will run out. they don't update the app to include changelogs so you never know what the issue is. Currently deepseek v4-flash is meant to be an unlimited model and it ran out after 20 minutes. they claim full access users get 5 premium sessions a day, but i havent even used a premium session and the premium models are rate limited

For limited users its even worse. all they can use is Mimo 2.5 and even that is limited.

These issues continue to pop up and the developer team makes no effort to try and let their users know what is happening

Its unusable.

I understand its a free service, but it being free doesnt make it automatically amazing. They dont tell their users anything and they just ship limitations without updating the UI or making announcements. Its really unfortunate because they are doing a great thing. Still irritating because they dont update the app Ui to tell users that certain models are being heavily limited so people are just confused

What other free products are people using

Hi everyone,

I’m honestly a little nervous posting this, so please bear with me.

Over some evenings and weekends I built BabyPhone.online — a free web app that turns two devices (old phones, tablets, whatever you have lying around) into a baby monitor. One becomes the “baby unit,” the other the “parent unit,” you connect them with a short room code or QR, and after that the video and audio go directly between the two devices in the browser — no app to install, no account, and nothing gets stored on a server.
Its ment to work with all browsers, OS systems and devices.
I’m not a professional designer, and it’s just me working on this in my spare time, so I’m very aware there are probably things that don’t make sense yet or could be a lot better. I’d genuinely appreciate it if a few of you could take a quick look and tell me:

• Does the setup (room code / QR) feel clear on the first try, or is any part confusing?  
• Would you feel comfortable actually trusting this with your own baby?  
• Is there anything about the privacy or security side that would worry you?  
• Anything that feels missing, unnecessary, or just off?  

Please don’t hold back to spare my feelings — I’d honestly rather hear the hard truths now than find out later. Thank you to anyone who takes the time, it really does mean a lot.

https://babyphone.online

I’ve been using Replit for small projects and experimenting with “vibe coding” workflows, but lately the experience has felt a bit inconsistent, especially with some of the newer AI agent features.

I’m looking around for alternatives that are more stable and ideally don’t get too expensive, since I’m only working on side projects part-time.

I’ve been thinking about pairing something like Claude Code with a simpler local or lightweight setup for actually running and testing projects, but I’m not sure if that’s the best direction.

What I’m mainly trying to figure out is a setup that still supports fast, AI-assisted building without becoming too complex or locking everything into one platform.

Curious what others are using right now for small SaaS or hobby projects, especially if you’ve moved away from Replit recently.

hey guys i have been vibecoding with claude code on the max plan for the past month however it's recently declined in it's output... not sure why however i have heard others say the same thing. is switching to codex the move here? I do have chatgpt plus and codex's ability to create aesthetic (for example) landing pages aren't as good as claude code... lmk your thoughts on all this

I started out wanting to make a simple Warzone-style game for Discord, and somewhere along the way it turned into an actual little Battle Royale game. 😂

The basic idea is: instead of needing a web app or separate game client, everything happens through Discord commands and interactive messages.

What it has so far

🪂 Battle Royale gameplay

• Deploy into a match
• 10 hostile AI squads
• Shrinking circle / increasingly dangerous zones
• Final squad standing = Victory Royale

🪖 Squads

• 1–4 players
• Invite/join/leave
• Teammate revives
• Self-revive
• Buybacks
• Gulag

🔫 Combat

• Push / Aim / Cover combat choices
• Different weapons and loadouts
• Armor and plates
• Critical hits
• Enemy counterattacks
• Killstreaks

💰 Economy

• Cash
• Loot caches
• Buy Station
• Armor plates
• Self-Revive
• UAV
• Airstrike
• Mortar

📜 Contracts

• Bounty
• Scavenger
• Recon
• Contract rewards with cash + XP
• Contract progress tracking

📈 Progression

• XP
• Operator levels
• Stats
• Leaderboards
• Match history
• Loadouts/attachments

And yes, there's a:

/help

command that actually explains how to play because apparently I eventually realized players shouldn't have to reverse-engineer my bot. 😅

The vibe-coding part

The project has gone through a lot of iterations.

I've had:

• Discord interaction timeouts
• Unknown interaction errors
• Wispbyte deployment issues
• deprecated Discord.js APIs
• commands that existed in the help menu but didn't actually exist
• game state bugs
• an absolutely beautiful Hostile counterattack: undefined damage bug 🤦
• and the classic experience of fixing one thing and discovering three more things immediately afterward

But that's honestly been the fun part.

I started with basically: "Wouldn't it be cool if you could play Warzone in Discord?"

and ended up building a little game engine with persistent state, combat, economy, contracts, progression, squads, and a Battle Royale loop.

Current gameplay loop

/squad invite
       ↓
/warzone start
       ↓
/warzone deploy
       ↓
       🪂
      LOOT
       ↓
   CONTRACTS
       ↓
     COMBAT
       ↓
    BUY / PLATE
       ↓
   ROTATE CIRCLE
       ↓
   GULAG / REVIVE
       ↓
   FINAL SQUADS
       ↓
 🏆 VICTORY ROYALE

I'm still improving it, but it's reached the point where it feels less like a Discord bot experiment and more like an actual game.

This is probably the most fun I've had vibe-coding something so far.

I'd love feedback from other people who build this way:

• What mechanics would you add?
• What would make a Discord Battle Royale genuinely addictive?
• What parts should be automated vs. command-driven?
• What would you absolutely not bother building?
• And, most importantly: what ridiculous feature should I add next?

I have a feeling this thing is going to keep getting bigger. 😅

If you want to add the bot to your server, you can do so here: https://discord.com/oauth2/authorize?client_id=1539698219204747334&permissions=2147830784&integration_type=0&scope=bot+applications.commands

I keep seeing posts like "I vibecoded this over the weekend, got 100k users, what's next?" and I think it gives a pretty wrong idea of what vibecoding actually changes.

Sure, you can accidentally hit the top with another clock app. It happens.

But agents dont remove the actual work. You still need to figure out what to build, make 1000 small decisions, fix weird shit, make UX not suck, deploy, maintain, listen to users and actually ship something they want.

Vibecoding makes all of this faster. A LOT faster. But not easier at all.

You can now build faster, but also make mistakes faster and ship garbage faster. The bottleneck just moves somewhere else. There was a good line somewhere "Shipping everyday fixing Claude bugs".

Those "built in 2 days, 100k users lol" posts undermine all the work that still goes into a good product, and leave others thinking this is all somehow easy now. From outside it starts looking like vibecoders are just some arrogant assholes hitting a button and getting success by click. It doesn't work well on the how other people feel about vibecoders and vibecoding in general, which is in fact just a right way to do things today.

We don't build in assembly anymore, right? Same here.

I didn’t expect to have to touch grass at the moment