Posting your game to Showcase

Where should I post?

Projects & Feedback is for a specific game project you are developing. Early prototypes, jam games, experimental mechanics and unfinished projects are welcome. You do not need a polished game or months of development. Show what is actually implemented or explain the concrete design question you need help with.

A playable game has something the player can do: interact with controls or a gameplay loop, even if it is only a small prototype. A rendered scene, a set of AI assets, an environment walkthrough without gameplay, or a character mash-up is not automatically a playable game.

If you only want to share a screenshot, visual scene, AI-art experiment, UI idea or progress clip without requesting critique, use Work in Progress. We welcome that kind of work, but it should not be described as a playable game when it is not.

Do not open several short, low-context posts in succession or copy the same link into multiple channels to attract attention. Use each channel for its intended purpose. A one-day prototype is fine; repeated link-dropping without clear work or engagement is not. Contributing useful feedback to other developers is encouraged, not a prerequisite for a first legitimate post.

One thread per game

Use the game name as the thread title. Keep later versions, screenshots and feedback in the original thread, rather than making a new thread for each build or milestone.

Good title: Frith & Fell.

Less useful title: PLEASE TRY MY AMAZING NEW GAME!

If you have several genuinely distinct games, they can each have their own thread. Make each one substantial enough for someone else to understand and respond to.

Start with something useful

Explain in your first paragraph:

• What the game is and what the player actually does, or which mechanics are being built.
• What is functional now and what is only planned.
• Whether the current build is playable, invite-only, unavailable or still in development.
• What specifically you want other members to assess.

For a playtest, add the supported platform, approximate time needed and a working link. If people must request access, create an account, download an installer or join a waitlist, say so directly. Don’t describe a store page or trailer as a playable build unless there really is accessible gameplay.

Example:

I’m making a browser puzzle game where the player folds sections of a small city to connect roads. The first four puzzles are playable and take about ten minutes. Can you tell me whether the mechanic makes sense before the tutorial explains it?

Play: your external game link

Platform: desktop browser

Try asking about controls, difficulty, pacing, onboarding, readability or a specific implemented feature. “Thoughts?” alone usually isn’t enough context for meaningful game feedback.

Forum tags and playable status

Use Looking for testers when you want people to play and report back. A proposed Playable build tag is for builds that members can access now; it is separate from the request for testers. Tag names and availability depend on the Discord forum configuration. An alpha or short prototype can be playable; a pretty video does not prove playability.

Devlog and Update describe the purpose of a post, not whether a build exists. Keep them on the relevant ongoing project.

If your project is already in the forum, you can use /projecturl to save its external playable URL as Discord thread metadata. This does not certify access or publish a site Project.

Screenshots and other media

Attach a clear gameplay screenshot or short GIF to your game thread. One landscape image is a useful start. Where possible, show the game rather than purely promotional artwork.

Upload it yourself in the opening post or as a new reply. The Bot looks for owner-uploaded images when choosing automatic media; another user’s image and an external link preview are not substitutes for an owner upload. Existing hero/cover images may keep priority.

The Gallery images editor in your Project tools can explicitly select up to 12 images for a Project gallery. It does not change the automatic cover/Showcase thumbnail.

Credit and rights

Be accurate about which parts you made and which assets or AI tools you used. Franchise characters, music and ripped game assets may have rights restrictions; do not imply you own someone else’s IP or that an unlicensed build is endorsed by its rights holder.

A fan project may still be a game, and a visual mash-up can still be shared in WIP. Moderators assess posting purpose and rights concerns separately. No routine moderator check is a legal clearance or a guarantee of safety.

Ask for a public website Project

The Discord forum and the public AIGAMEDEV website are different approval surfaces. To request site review, apply Siterequest to your original game thread.

Only a moderator applies Publish to site after review. That tag is not yours to self-apply; a jam tag, Playable build tag or saved URL does not bypass approval.

After approval, run /mygame publish in the same thread. Choose your game’s current status the first time. Use /mygame manage to edit the Project page. Site publication needs both the current moderator approval and your own publication request. Exports are normally scheduled every six hours, and publication follows a successful export and build.

You can browse approved games through the site’s game directory and Showcase, where playable-link filters are available. Discord projects that have not been submitted and approved for publication will not necessarily appear there.

Keep discussions together

Answer follow-up questions when you can and update your original thread when you release a new build or fix problems reported by testers. Useful feedback belongs with the game rather than in a separate promotional post. Read How to give feedback for the other side of the exchange.