How to Build a Game Community Before Launch (2026)

A game community is not a crowd. Before launch, it is a short list of people who know your game exists and are willing to act when it ships: wishlist it, play the demo, reply to a post, tell one friend. Thirty of those people beat a Discord member counter reading two thousand, because the list converts on launch day and the counter does not.

This is the people half of pre-launch marketing. The system view, including how wishlists feed Steam visibility and how to time a demo, is our zero-budget indie marketing guide; this piece covers where early communities actually form, what keeps them alive at small sizes, and the one asset you should own outright.

The short answer#

Channel	What it is for	What it costs	The first step
Steam Coming Soon page	The launch-day list: wishlists and followers	$100 Steam Direct fee per game	Put the page up as early as it can honestly exist
Discord	Feedback and your first thirty players	Free	Open it when you can post weekly
itch.io page with a devlog	Small wins in public, early builds	Free; you pick the revenue split	Write the premise devlog: five screenshots, one paragraph
Reddit and genre forums	Cold discovery among strangers	Free	Read each community's rules before your first post
Waitlist or newsletter	The only audience you own	Free at small scale	One field on your site, mailed monthly

Two of these you control end to end: your Discord and your list. Two you rent: Reddit reach belongs to the subreddits, follower reach on Steam belongs to Valve's surfaces. itch.io sits in between, friendliest to total newcomers. Rented channels bring strangers in. Owned ones keep them.

The store page is a community surface#

The wishlist side of a Steam page is covered in the marketing guide. The community side is the follow button next to it. A follower gets your events in their Steam activity feed, and Steam's events and announcements tools exist precisely for the pre-launch rhythm: a small update or patch notes when you ship a build, a major update when something worth a headline lands. That is a devlog the player never had to leave Steam to follow.

Two more mechanics on the same page. The coming Next Fest on Valve's calendar is October 2026, entry needs a public demo alongside the store page, and a game can enter exactly one edition, so you time it against your launch rather than taking the nearest. And Steam Playtest lets you run closed feedback rounds with a waitlist Valve manages for you, which pairs well with a small Discord: candidates raise a hand on the store page, your core group gets the build first.

The signup mechanics of the page itself, including the fee and the review timeline, are in our Steam Direct walkthrough.

Build the Discord for twenty members#

The failure mode is universal: a developer opens a server, creates channels for announcements, general, fan-art, memes, bug-reports, off-topic, suggestions and three regional rooms, then posts twice. Every empty channel tells the next visitor this place is dead. Build for the size you have.

Four channels carry a pre-launch server: announcements where only you post, one devlog channel, one general chat, and one for playtest builds when they exist. Pin three short rules, turn on the membership screening community servers offer, and delete a channel the week it stays silent. An active server with three rooms beats a ghost town with fifteen.

Then the part nobody outsources: you post first, every week. A community server where the developer is silent is a waiting room with no doctor. The healthy pattern is a Friday note: what shipped, what broke, one question. Members reply to developers who are visibly working; they do not reply to invitations.

Skip the shortcuts. Bought members and gimmick giveaways produce a counter, never a conversation, and a fake-looking server costs you the real early fans who did show up. Put the invite link in your devlog footer instead and let it grow at the speed of your posts.

Devlogs where readers already are#

Your itch.io page is the easiest home for the devlog itself: free to set up, happy to host early and unfinished work, and each post lands on a page where the follow button and your build live one click apart. If Steam is the launch platform, write there too, as events rather than page edits, so followers see the update in their feed instead of discovering it by accident. The two stores compared for exactly this early-page role are in Steam vs itch.io vs Epic.

One discipline makes both work: a single source of truth. Write the devlog once, on your page, and echo short pointers everywhere else. Five posts that say the same thing in five places age badly the day a detail changes.

A devlog entry that gets read has a shape. What changed since last time, in at most five bullets. One gif or clip showing the change. One specific question at the end, because a question gives a stranger something to say, and "check out my game" gives them nothing.

Reddit: earn the room before you use it#

Every subreddit and forum has its own rules on self-promotion, written by people who watched their community get strip-mined by drive-by advertising. Read them before posting anything. The communities that welcome devlogs say so explicitly; the ones that ban them will remove you on the first offense and remember you on the second.

What travels there is specificity. Scan the front page of r/gamedev any given week and the threads full of comments are revenue postmortems with exact numbers, failed-launch writeups, honest "here is what I would do differently" posts. That is the currency, and it is the opposite of a marketing post. A thread titled "my first game made $46,000 and my second made under $200" will outperform a month of polished screenshots, because it gives readers something real to argue with.

So the sequence is: comment usefully on other people's threads in your genre and engine for a few weeks, then post your own numbers and failures alongside your progress. Ask first, promote second, and most communities will have your back by the time you have something to sell.

The waitlist is the only audience you own#

Everything above lives on somebody else's platform. Reddit reach belongs to subreddit rules, Discord reach belongs to a company with its own priorities, Steam reach belongs to an algorithm. A waitlist or newsletter on your own site is the one audience that carries over no matter what changes: the platform pivots, the account gets banned, the store tweaks discovery, and your list still opens in a mail client tomorrow.

Mechanically it is the smallest form on the internet: one field, no account, a promise of roughly monthly notes. What you send is the same discipline as the devlog, what changed and what broke, written for people who asked to hear it.

This is not a hypothetical for us. Egmatic is pre-alpha, and the waitlist on our landing page is how we know demand exists before the editor is finished. Every signup is one person we can tell on launch day, which is the entire point of building a community before you have a product to sell.

The weekly loop#

The whole machine is four steps, an afternoon a week:

Step	Action	Where
1	Ship one artifact: a clip, a build, a level, a 30-second cut from the trailer guide	Your machine
2	Devlog it: five bullets, one gif, one question	Your itch page or Steam events
3	Echo it into Discord with the question repeated	Your server
4	One external post or three useful comments	Reddit, forums

Track three numbers against that loop: wishlists per week, subscribers per week, and how many members replied to anything in the last seven days. Member count is not on the list. A server that grows from 30 to 40 members while five people reply every week is compounding; a server that grows to 2,000 while the message feed stays empty is rented silence.

What kills pre-launch communities#

Opening twenty channels on day one, covered above. Posting only when you need something, wishlists or testers or votes, which teaches everyone that your name means an ask. Going dark for six weeks during a hard build stretch instead of posting one honest line that you are heads-down until a date. Buying members. Measuring the Discord counter.

None of these are fatal on their own. Together they are the pattern behind every dead indie server, and every one of them is avoidable with the same habit: one artifact a week, one honest paragraph, one question.

Start this week with the two cheap ones. Put the store page up, or the waitlist form if the store page cannot honestly exist yet. The Discord can wait until Friday, when you have something to post in it.