Poke Party: A Mario Party-Style Game Built in a Month-Long AI Session

An AI-built Mario Party-style game with a Pokémon theme is the kind of project many solo developers have thought about and few have finished. Poke Party, shared by u/TowelPretend on r/aigamedev, is presented as one: a party game in that mould, described as the result of a month-long AI session. This piece gives the context the post doesn't: what the genre actually needs, where long AI sessions tend to struggle, and what a fan game built on Nintendo and Pokémon characters runs into.

What did the maker post?

The original thread is Made my own version of Mario Party - POKE PARTY! by u/TowelPretend on r/aigamedev. All credit for the project goes to the maker. Go to the thread for the game itself and any screenshots or video.

The body of the post could not be retrieved while this article was being prepared. So this write-up confirms only what the title and listing show: a Mario Party-style game, called Poke Party, framed as a month-long AI-assisted build. The following details are not confirmed here:

• which engine or framework the game uses
• which AI tools or models were involved, and in what role (code, art, audio)
• whether a playable build or a repository is linked
• the target platform
• what the month covers: the full game, a prototype, or one stage of a longer project

Check these in the maker's post and comments rather than assuming them. Nothing below should be read as a description of how Poke Party works inside.

What does a Mario Party-style game actually require?

"Mario Party-style" covers a specific set of systems. According to Wikipedia's Mario Party article, the series has up to four local or computer-controlled players competing on a game board interspersed with minigames.

The same article describes the core loop:

1. A fixed turn count. Games last a set number of turns, usually 20, 40 or 60.
2. Die-roll movement. Players roll a die to move around the board.
3. Space events. Landing on a space triggers an effect. Blue spaces give coins and red spaces take them.
4. Stars as the win condition. The player with the most stars wins, with coins as the tiebreaker. Bonus stars are awarded at the end.
5. A minigame after each round. Minigames can be free-for-all, 2v2, 1v3 or duel formats, and winners earn coins.

The content load is the part that stands out. Wikipedia lists minigame counts from 56 in the first game to 112 in Super Mario Party Jamboree. Each of those is a small game with its own controls, rules and win state. Nintendo's studio work also shows the format being reworked over time: Wikipedia's Super Mario Party article says NDcube developed that 2018 Switch entry, and describes it as a "complete refresh" of the series.

Why the genre looks like a fit for AI-assisted coding

Analysis: the genre breaks down into small, testable systems: turn order, board spaces, items, scoring, and handing control to and from a minigame. Coding agents tend to work best on bounded tasks with clear inputs and outputs, and a board game loop has plenty of those. A single minigame is also a self-contained prototype, which is a common size for AI-assisted builds.

The catch is that none of the sources here show how well any particular tool handles this kind of project. The fit is plausible, not proven.

Where is a month-long AI session likely to be stretched?

The points below are questions to check against the maker's post, not findings about Poke Party. They come from what the genre requires and from patterns in other community AI builds.

CPU opponents

The Mario Party format assumes up to four players, some of them computer-controlled. A CPU player has to make board decisions (which path, when to use an item) and also play every minigame at some reasonable skill level. That is separate AI logic for each minigame. Check whether Poke Party has CPU players, and whether they play minigames or only move on the board.

Local multiplayer input

A couch party game needs several controllers or shared-keyboard input, plus menus that more than one person can navigate. Browser and desktop builds handle gamepads differently. Check whether multiplayer is local, online, hot-seat, or single-player against CPUs.

The star and coin economy

Coins buy stars, minigames pay out coins, and spaces add or take them. If one source pays too much, the game is decided early. Balancing this takes repeated playthroughs, which an agent cannot do for you without a test harness. Readers interested in automated playtesting can see the test plan in Can an AI Agent Playtest Your Godot Game?.

Minigame variety

With the official series running from 56 to 112 minigames per game, the useful question is how many Poke Party ships with and how different they are from each other. Ten minigames that play distinctly may matter more than thirty reskins of the same mechanic.

Art and audio consistency

Mixed asset sources, whether AI-generated, placeholder or borrowed, often show up as uneven style. Check whether the post says where the art and sound came from.

How other long AI builds compare

A few earlier specimens give useful reference points for scope and timeline:

• A Claude-Built 3D Terraria Rebuild covers a project spread across 109 chats and where the result falls short.
• Vibe Coded Racing Game, Six Months On follows a racer over a much longer timeline than one month.
• A 12-Year Game Dev's First AI Game looks at an eight-day Unity 6 jam build and where human QA still fits.

If you plan a similar project, a long session works better when the agent can find its way around the codebase. How to set up Claude Code for game development covers project notes, structure and conventions that help an agent keep context over weeks.

What is the IP question for fan-made party games?

Poke Party mixes two of Nintendo's best-known properties: the Mario Party format and a Pokémon theme. This matters if you plan something similar.

Nintendo does publish rules for fan content, but they cover a different use. According to Siliconera, Nintendo updated its Game Content Guidelines for online video and image sharing in September 2024. Mondaq's summary says the guidelines first appeared on 29 November 2018 and are aimed at streamers and creators who broadcast Nintendo games.

Those guidelines are about sharing footage and images of Nintendo's own games. They are not a licence to make fan games, and they don't settle the legal status of a Pokémon-themed party game. None of the sources read for this article address fan-game legality directly.

A reasonable approach for anyone building something similar:

• Read the rules that apply to each character or brand you use, and don't treat a streaming policy as permission to make a game.
• Don't charge money, take donations against or otherwise monetise a game built on Nintendo or Pokémon IP.
• Consider original characters or clear placeholders if you want to share the game publicly or carry the systems into a commercial project later.

The maker's post may say how they handled this, for example with original art, placeholders or a private-only build. Check the thread before drawing conclusions.

Verdict: who is this specimen for?

Analysis of the post as a reference:

Useful for solo developers wondering whether a board-plus-minigames game is a realistic AI-assisted project. The month-long framing gives a rough timeline and scope reference, provided the post makes clear what that month produced.

Less useful for anyone who needs steps they can repeat. Unless the post includes prompts, a tool list or a repository, it is a showcase rather than a method.

When you read the thread, look for:

1. A playable link. Can you actually try it, and on what platform?
2. The minigame count. How many, and how varied?
3. Multiplayer mode. Local, online, or against CPUs only?
4. Bug handling. Does the maker describe what broke over the month and how they fixed it with the AI?
5. Tooling. Which engine and which AI tools, and what the human did by hand.

For more community AI builds, browse Specimens or the coding agents tag.