AI Assisted Indie RPG Development: One Developer's Two-Week Start on a Childhood Dream RPG, and the Questions About AI Use

AI assisted indie RPG development has a new public test case in a post on r/aigamedev. A developer posting as u/edm-4-life says they have finished two weeks of work and are now "fully committed on the dream RPG" they have wanted to make since they were a kid. The original thread is on Reddit.

This Specimen reports only what the post's title confirms. It lists the questions about AI use that the title leaves open. It also compares the project with one documented AI sprite workflow, to give readers a sense of what is realistic for a project like this.

What did the creator post?

The thread title gives three facts:

• Time spent: about two weeks of work so far.
• Commitment: the creator says they are now fully committed to the project.
• Genre and motive: it is an RPG, and one the creator has wanted to make since childhood.

The post is in r/aigamedev, a community about making games with AI tools. That suggests AI plays some part in the project, but not which part. The title doesn't give an engine, art style, scope, platform or release plan, so this Specimen doesn't name any of them. Credit for the project and any media in the thread belongs to u/edm-4-life. This page links to the thread and doesn't reproduce its images or video.

Two weeks is an early milestone. RPGs are known for large asset counts and long content pipelines. At this point the project is starting production, so there are no results to judge yet.

What do we still need to know about AI use?

These are the questions worth putting to the creator. Each one stays open unless the thread answers it. Readers who follow the thread can check whether the creator has replied.

These questions matter because "AI RPG" can mean very different things. One developer might hand-draw every sprite and use an AI assistant only for code. Another might generate most of the art and write the code by hand. A third might use AI for everything. Each approach brings a different workload, different quality risks and different licensing questions.

If the code is mostly written by an agent, our guide on how to set up Claude Code for game development explains how to keep a growing project easy for an agent to follow. That gets harder as an RPG adds more systems.

How are AI sprite animation workflows documented elsewhere?

For a reference point, here is one published workflow. It is only for comparison and doesn't describe how this RPG was made.

A DEV Community article by the maker of a tool called SpriteFlow explains how to turn a text prompt into a sprite sheet. The author is promoting their own product, so the claims below are advice from a seller, not independent measurements.

The consistency problem

The article names consistency as the main problem with AI sprites. According to the author, colour, line weight and proportions drift from one frame to the next. A character that changes shape between walk frames looks broken in motion.

The proposed fix: lock the style first

The author's approach runs in this order:

1. Gather reference images that define the target look.
2. Lock a style from those references before generating anything else.
3. Generate every animation frame against that locked style instead of writing a fresh prompt for each frame.
4. Assemble the frames into a sprite sheet for the engine.

The idea works with any tool: set the reference first, then generate against it. Separate prompts rarely match on their own.

Time and frame-rate claims

The article says a full character with walk, idle and attack animations can take 20+ hours to make by hand. The author suggests generating most of the work with AI and polishing the "hero" characters by hand, since players see those most.

For playback speed, the author suggests:

• 8 to 12 FPS for retro pixel art
• 12 to 24 FPS for smoother 2D animation

These are the author's recommendations. The 20-hour figure comes from someone selling a tool that shortens it, and the article doesn't present it as a measured benchmark.

For more on where AI fits in 2D pipelines, see our AI pixel art side-scroller specimen and the sprite generators tag.

What trade-offs does a solo RPG dev face with AI assets?

The points below are analysis based on the sources above and on the genre in general. They don't describe u/edm-4-life's project.

Volume makes drift expensive

RPGs usually need a lot of matching assets: party members, enemies, NPCs, items, tiles, portraits and UI. A short arcade game might need only a handful of sprites, while an RPG can need hundreds. If the drift the SpriteFlow article describes appears across that many assets, cleanup costs rise with every asset. Setting up a style lock or reference sheet early costs less than fixing mismatches across hundreds of finished assets.

Hand cleanup is the usual compromise

The documented workflow doesn't claim AI output can ship untouched. It suggests generating most assets and polishing key characters by hand. In an RPG, that could mean careful work on the main cast and less on background enemies or filler items. The open question for this project is where the creator draws that line.

Animation is a separate problem from stills

A good character portrait doesn't guarantee a usable walk cycle. Keeping frames consistent with each other is harder than producing one striking image, which is why the SpriteFlow author builds the whole workflow around it. Our AI animation editor specimen covers what game-ready animation tools still need to offer.

Licensing and disclosure

Two issues apply beyond the art itself:

• Licensing: each AI tool's terms decide how you can use its output commercially. Terms vary by provider and change over time.
• Store disclosure: some storefronts ask developers to disclose AI-generated content. The rules differ by platform.

The thread title mentions neither issue, and this Specimen doesn't state any specific platform's rules. Anyone planning a commercial RPG should read the current terms of every tool and storefront they use.

How does this compare with other AI RPG specimens?

This isn't the first RPG on the site where the open questions about AI outnumber the answers. Our write-up of a 2.5D pixel art online RPG followed the same pattern: an interesting project with little detail on where AI fits. On the 3D side, our concept art to a playable 3D game specimen covers a developer who did explain their art style pipeline. That kind of detail is what makes a project useful to learn from.

Verdict: who should watch this project?

Based on what is public, this project is worth following for:

• Solo and small-team developers considering AI-heavy asset pipelines for genres that need a lot of content, like RPGs.
• Developers who want to see whether style consistency holds as a project grows past its first few weeks.
• Anyone interested in the commitment side, as a long-held game idea turns into a real production.

It is too early to treat as a case study. Two weeks of work is only a start. The useful lessons will come if the creator shares which assets are AI-made, which tools they use, how much hand editing each asset needs, and whether the style holds as the asset count grows.

If u/edm-4-life posts follow-up devlogs with that detail, the project could become a practical reference for AI assisted indie RPG development. Until then, it is a promising start. Updates will be in the original thread, and more community projects are in Specimens.