I’ve tried launching/promoting a few small web game prototypes on Reddit, and a recurring issue is that commenters almost immediately focus on whether the project was “vibe coded” or AI-assisted rather than the game itself. Sometimes the feedback is useful, but it can also derail the entire thread into accusations about AI usage.

I’m genuinely unsure what the best norm is here. On one hand, being honest about using AI tools seems better than pretending they weren’t involved. On the other hand, saying “vibe coded” upfront seems to make some people instantly dismiss the project as low-effort slop, even if there was still a lot of iteration, debugging, system work, UI cleanup, balancing, and manual decision-making involved.

For solo devs making small web games/prototypes with AI-assisted workflows, what do you think is the best approach?

• be fully transparent upfront?
• mention AI only if asked?
• avoid the term “vibe coded” and say “AI-assisted” instead?
• focus only on the game unless the workflow comes up?

Mostly trying to figure out where honesty helps versus where it just causes the whole discussion to become about AI instead of the actual project.

Imagine in like 10 years, the quantity of games we will have that are made at least partially by AI. At that point that will lower the value of these games if not by sheer amount of offer.

So the standards will rise and the value will shift towards something that is either harder to do or more rare...

This is hard to predict...Anyways, let me know what you thinkk

Im tired of all the new limits, just unsubscribed from everything, any help is much appreciated!

You can decide everything:

- Genre

- Gameplay

- Story

- Multiplayer or singleplayer

- Progression system

I’m currently building a game and looking for ideas from real players instead of copying trends.

Drop your idea I might actually turn it into a real feature

What would be the best ai workflow for a 2d top down preferably pixelated game.

I tried gemini and chatgpt, they either look too AI or if given a reference inspiration photo, they basically copy paste it.

Not talking about graphics or performance I mean game design itself.

For me, it feels like too many games focus on:

• aggressive monetization
• daily grind systems
• endless currencies
• FOMO mechanics

instead of just making a genuinely fun game people WANT to keep playing.

Curious what everyone else thinks.

What’s the biggest thing holding mobile gaming back right now?

With the recent explosion of ternary (1.58-bit) models and sparse Mixture of Experts (MoE), we are rapidly approaching a massive paradigm shift in how games are built. Right now, companies like Ubisoft are actively pushing the boundary with runtime GenAI prototypes (like their NEO NPCs project and the recent first-person shooter prototype Teammates that interprets voice commands and intent dynamically).

But right now, they are still treating AI as an accessory bolted onto a traditional, rigid C++ engine (Unreal/Unity).

What happens when the Game Engine ITSELF is a local Ternary World Model?

Think about the math. Right now, a lot of us are jumping through insane optimization hoops just to squeeze 35B MoE models with high context windows onto consumer hardware like an 8GB VRAM 3070. But once native 1.58-bit (ternary) architecture becomes the standard for high-parameter MoE world models, multiplication is replaced entirely by basic addition/subtraction. The processing bottleneck completely shifts away from floating-point compute over to memory bandwidth, making standard CPU/System RAM incredibly fast at local inference.

The Game Engine as a "Model Mixer"

In this setup, game files on Steam wouldn't be 150GB of static texture files, uncompressed audio, and bounding-box collision code. The game client is a lightweight runtime wrapper hosting a highly optimized, local foundational world model trained entirely on the semantic physics, logic, and visual aesthetics of that specific universe.

Traditional game development transforms into Semantic Model Layering. Instead of writing code, you stack low-bit, modular adapters—exactly like LoRAs:

• Base Layer: The historical world model (understands the core physics, structural logic, and environmental art style).
• Mechanics LoRA: A ~250MB adapter injected to teach the base model specialized logistical rules (e.g., automated belts, item factory logic).
• Movement LoRA: Overrides the kinematics layer to synthesize fluid wall-runs or parkour animations on the fly.

The Ultimate Cross-Game Interoperability: The "Online Animus"

Imagine a publisher like Ubisoft taking this architecture for an Assassin’s Creed game and introducing a web foundry called the "Online Animus."

Instead of an in-game character slider, players upload their own mixed-media data (voice clips, photos, or raw bone-rigging proportions from an FBX file). Ubisoft's cloud cluster runs a rapid Quantization-Aware Training (QAT) run, distilling your semantic DNA into a tight, highly compressed Identity LoRA Layer.

When you boot your local game client, you pull your identity packet down from the Animus cloud and hot-load those weights directly on top of the local historical world model:

1. Visual Synthesis: The local model seamlessly integrates your physical traits into the era's art style, naturally draping period-accurate robes over your exact, custom proportions.
2. Native Audio Processing: When you speak into your headset to distract an enemy guard, the local engine synthesizes your exact vocal timbre, translated flawlessly into conversational Latin or Japanese.
3. Contextual Memory: When you log off, the local engine updates your personal LoRA weights based on your gameplay choices and stealth habits. Your identity retains memory of the simulation.

The Bottom Line

By moving from post-training quantization to native 1.58-bit world models, we completely decouple the creative assets from the runtime logic. Big studios can focus millions of dollars of compute on training the massive foundational historical sandboxes (the destination), while the players fully own the decentralized, luggable identity vehicles (the LoRAs) they use to explore them.

No more rigid collision bugs, no more blurry textures when you press your face against a wall, and no more walled-garden cosmetics.

How far away are we from an open-source framework or indie engine attempting this type of runtime model mixing? Are there any pipelines out there right now making modular weight-layer hot-swapping viable in an interactive loop?

Hi !

Months ago, actually probably closer to one year ago i had developed a tool for my workflow to remove background from images using latest open source tech, it worked great, much better than local photoshop even, started using it and that was it. Then times changed and the UI tool got a second life as headless mcp service for my agents. Yesterday was writing about my workflow and somebody mentioned i should opensource the tool, and so i did. The end...

Hope it will serve others as it did with me.

https://github.com/frozenpepper/FP-Background_Obliterator

P.S. first opensource release for me, and the readme file and general code / folder cleanup was done by the new Gemini Flash model... so... let me know if it needs fixing

I’ve been thinking about how many great game ideas never get explored, especially on mobile.

So I’m curious

If you could design your ideal mobile game, what would it look like?

You can decide everything:

* Genre

* Gameplay

* Story

* Multiplayer or singleplayer

* Progression system

Would you go for something competitive, story-driven, co-op, or something completely unique?
Drop your idea below
I’d love to see what kind of games people actually want instead of the usual trends.
Let’s see what the community comes up with