Reddit Community Analysis: r/gamedev

1. Data Sources & Methodology

• 359 unique posts after deduplication across 4 time periods (all-time, year, month, week), 4 pages each (16 raw JSON files)
• Date collected: April 3, 2026
• Subreddit subscribers: 1,996,174
• Score range: ~1,000 to 33,563
• Median score: ~2,500 (estimated from ~180th ranked post)
• Top 10 threshold: ~5,854
• Top 25 threshold: ~3,969
• Top 50 threshold: ~3,142
• Top 100 threshold: ~2,170

This is a content strategy guide for distributing through r/gamedev. The dataset skews toward high-performing posts since it draws from "top" sorting. Low-effort promotional posts that get removed or sink are underrepresented.

Cross-subreddit calibration: r/gamedev peaks at ~33,563 vs. r/IndieDev's ~23,945, r/IndieGaming's ~15,697, r/ChatGPT's ~84,058, r/macapps's ~2,029, and r/SideProject's ~6,241. With nearly 2M subscribers, r/gamedev is the largest dedicated game development subreddit. However, its score ceiling is lower than you would expect for its size because the community is heavily moderated and text-discussion-oriented. A score of 1,000 is a solid post, 3,000+ is a genuine hit, 5,000+ is exceptional, and 10,000+ is viral territory. The median score (~2,500) is comparable to r/IndieGaming's (~2,504) despite having 4x the subscribers, reflecting a community that upvotes cautiously and prefers substance over spectacle.

2. Subreddit Character

r/gamedev is an industry watercooler for professional and aspiring game developers that explicitly bans project showcasing, making it a discussion-first, show-nothing community. Unlike r/IndieDev (which welcomes memes, gameplay clips, and emotional milestones) or r/IndieGaming (which is a visual showroom for gamers), r/gamedev is where developers come to talk ABOUT game development -- the process, the business, the politics, and the craft -- without showing their own games.

Rule 3 is the defining feature: "No Showcasing Projects." This single rule fundamentally shapes the community's content. You cannot post your game here. You cannot share screenshots, trailers, or gameplay clips for promotional purposes. You CAN share technical breakdowns, tutorials, postmortems, and industry discussion. This makes r/gamedev the anti-promotion subreddit. The sidebar explicitly says: "Do NOT ask what engine to use for your project" and redirects showcasing to r/indiegames, r/playmygame, or r/gamedevscreens.

Core cultural values, ranked by intensity:

1. Anti-corporate skepticism -- The community is fiercely critical of platform holders (Unity, Steam, Epic, Apple) and large studios (Ubisoft, Activision). Unity's install fee controversy generated 3 posts in the top 50 alone (6,998, 3,969, and 1,693 scores). Steam bugs destroying launches (5,787), Apple siding with Chinese cloners (10,550), and Epic layoffs (1,660) all resonate deeply. The community sees itself as the little guy against corporate interests.

2. Anti-generative-AI (culturally strong, moderately enforced) -- No explicit rule bans AI, but the community is deeply skeptical. "So many new devs using AI generated stuff in their games is heartbreaking" (1,163, 0.73 ratio -- the lowest ratio in the dataset, showing fierce division). "How vibe coding lead to my project's downfall" (2,799, 0.91). "Godot maintainers swamped by AI-generated code branded AI slop" (1,405). "We need to encourage people to use the term generative AI instead of just AI" (1,667). The community is NOT anti-AI-tools universally; it distinguishes between generative AI (bad) and traditional game AI (fine). False AI accusations are also a sore point (1,448).

3. Pro-worker, anti-crunch -- "Please refuse to work weekends and any unpaid overtime" (6,704), "Rant from a former Ubisoft employee" (4,888), Bethesda unionization (4,549), Diablo developers forming a union (1,474). The community strongly sides with workers over management.

4. Postmortem culture and data transparency -- The community loves hard numbers. Steam sales data, wishlist conversion rates, ad spend breakdowns, and revenue postmortems are community gold. "Over 16k wishlists, how could the release go this bad?" (3,390, 778 comments), "I emailed 100+ YouTubers" (1,497), "I Spent 3,594 on Reddit Ads" (1,138), "My game reached 100k sold copies -- here's all the data" (1,469). Transparency is rewarded; vagueness is ignored.

5. NSFW content freedom (2025-2026 hot topic) -- At least 8 posts in the top 100 of the year period relate to Collective Shout, itch.io NSFW removals, and payment processor censorship. This is currently the community's most active battleground, with posts scoring 1,300-3,900 and generating 200-850+ comments each.

Enforcement mechanisms: Rule 3 (No Showcasing) and Rule 4 (No Blatant Self Promotion) are the primary content filters. Posts with "only a link to social media, game pages, or similar will result in a ban." However, links are allowed if they "serve a valid purpose, such as seeking feedback, sharing a postmortem, sparking discussion, or offering a learning opportunity." The community also self-polices through downvotes -- posts perceived as thinly-veiled self-promotion get friction even if they technically follow the rules.

How this sub differs from similar subs: On r/IndieDev, you show gameplay and share memes. On r/IndieGaming, you show gameplay to gamers. On r/gamedev, you discuss process, share knowledge, and debate industry issues. It is the only major game development subreddit that explicitly prohibits showcasing. This makes it unusable for direct product launches but invaluable for building credibility through knowledge-sharing.

3. The All-Time Leaderboard

Dataset median: ~2,500. Top 25 threshold: 3,969. The top 25 averages 0.961 ratio. TEXT format dominates (10 of 25), followed by LINK (4), VIDEO (5), and IMAGE (6). 10 of 25 posts have no flair, reflecting the community's casual flair usage. The most controversial top-25 post is "Palworld is not a good game" (0.81 ratio) -- opinion posts with strong takes generate both massive engagement and significant pushback.

4. Content Type Dominance at Scale

Key finding: Tutorial and Source Code flairs have the highest average ratios (0.98-0.99), indicating near-universal approval. Discussion flair has the lowest average ratio (0.92) because it encompasses the most controversial opinion posts. Posts with no flair at all average higher scores than most flaired categories, suggesting that many viral posts are spontaneous rather than carefully categorized.

The surprise: Industry News flair, despite being the year period's dominant category, has the lowest average score (~1,550). This suggests the community is drawn to industry drama in the moment but doesn't upvote it as aggressively as technical content.

5. Content Archetypes That Work

Archetype 1: The Technical Breakdown / Tutorial

Score range: 2,900-8,217 Examples:

• "Stylized explosion shader breakdown" (8,217)
• "Procedural animation in 10 steps" (6,432)
• "Edge lighting for pixel art" (5,794)
• "LERP 101 (source code in comment)" (4,606)
• "Fire animation tutorial: Shading and Animation basics" (4,276)

The pattern: Short, visual, educational content that teaches a specific technique. VIDEO and IMAGE/GIF formats dominate. These posts achieve near-perfect ratios (0.98-0.99) because there is no opinion to disagree with -- it is pure knowledge transfer. The titles name the exact technique, keeping the promise clear.

Why it matters for distribution: This is r/gamedev's one legitimate channel for showing your work without breaking Rule 3. If your product involves game development tools, engines, or techniques, creating tutorials that demonstrate your tool's capabilities is the most natural and highest-approval content type on the subreddit.

Archetype 2: The Platform Outrage Post

Score range: 3,063-10,550 Examples:

• "Apple removed my game from the app store because of a Chinese clone" (10,550)
• "Unity silently removed their Github repo to track license changes" (6,998)
• "This is how Steam can ruin more than 10 years of your work" (5,787)
• "The game I've spent 3.5 years and my savings on has been rejected by Steam" (3,063)
• "Wow! Facebook (Meta) just unpublished our game studio page" (3,035)

The pattern: A developer is wronged by a platform (Steam, Apple, Unity, Meta) and shares the story with evidence. The community rallies in solidarity. These posts generate enormous comment counts (500-1,300+) because every developer fears becoming the next victim. Most include detailed evidence, timelines, and legal specifics.

Why it matters for distribution: If you have been genuinely wronged by a platform, sharing the story here generates massive visibility and community goodwill. The post about Steam's wishlist email bug (5,787) is a textbook example -- the developer shared data, the community amplified it, and the story spread to press outlets.

Archetype 3: The Data-Rich Postmortem

Score range: 1,138-5,787 Examples:

• "Over 16k Wishlists, how could the release go this bad?" (3,390, 778 comments)
• "My game reached 100k sold copies -- here's all the data" (1,469)
• "I emailed 100+ YouTubers to play my game and here are the results" (1,497)
• "I made 5k wishlists in my first month on Steam" (1,497)
• "I Spent 3,594 on Reddit Ads for my indie game" (1,138)
• "I Analyzed Every Steam Game Released in a day" (1,536)

The pattern: Hard numbers, transparent methodology, honest reflection on what worked and what failed. The community rewards vulnerability over vanity. Failed launches with honest data outperform successful launches with vague claims. Posts that include specific dollar amounts, wishlist conversion rates, and traffic source breakdowns generate the most engagement.

Why it matters for distribution: This is the single best archetype for product awareness on r/gamedev without violating rules. Frame your launch as a data-sharing exercise. "Here's exactly how my launch went, with every number I have." The community will upvote the transparency, and your game gets named in every reply.

Archetype 4: The Industry Hot Take / Opinion Post

Score range: 1,200-7,647 Examples:

• "Palworld is not a good game. It sold millions" (7,647, 0.81 ratio)
• "Pro tip: never go public" (3,697)
• "Sorry, your marketing isn't bad, your game is bad" (1,434, 0.85 ratio)
• "Gamedev is not a golden ticket, curb your enthusiasm" (1,213, 0.79 ratio)
• "Why don't people understand that this is an art form?" (1,656)

The pattern: Strong, declarative opinions about game development philosophy. These posts have the highest comment-to-upvote ratios in the dataset because they trigger debate. They also have the lowest approval ratios (0.79-0.93), indicating significant pushback. The formula is: [Contrarian claim] + [Supporting argument with specific examples].

Why it matters for distribution: These posts are high-risk, high-reward. They generate massive engagement but also significant downvotes. If your product relates to the opinion you hold (e.g., an anti-AI-slop position from a hand-crafted-art tool maker), the debate itself becomes a distribution channel.

Archetype 5: The Wholesome Developer Story

Score range: 1,509-18,579 Examples:

• "Just overheard my son and his friends start their own game development studio" (18,579)
• "Started coding this January, today I release my first game!" (13,168)
• "Give a man a game and he'll have fun for a day. Teach a man to make games..." (5,593)
• "By pure luck, the first person to play my game was a huge twitch streamer" (2,401)
• "My nephew accidentally became my best marketer" (1,509)

The pattern: Personal, heartwarming stories about the human side of game development. Kids discovering coding, first releases, unexpected moments of joy. These achieve high ratios (0.93-0.99) because they are hard to dislike. The best ones are specific, funny, and self-deprecating.

Why it matters for distribution: If you have a genuine personal story connected to your product, this is a high-ceiling archetype. The "son starting a game studio" post (18,579) is the second highest-scoring post in the dataset. But it must be authentic -- fabricated wholesomeness is instantly detected.

Archetype 6: The Free Resource Drop

Score range: 1,918-5,593 Examples:

• "I've made 60+ textured nature models you can use for free!" (5,593)
• "Epic Games Releases $12M Worth of Paragon Assets for Free" (5,337)
• "I've made 200 crosshairs so you don't have to!" (3,312)
• "[6000+ free models] Google Poly is shutting down, so I spent 5 months recreating it" (3,836)
• "I've made over 1,280 input icons for your games! (CC0)" (1,918)

The pattern: Free, immediately usable assets or tools with clear licensing (CC0 or public domain). The community loves generosity and rewards it with near-perfect ratios (0.97-0.99). The best posts include preview images, clear download links, and explicit license statements.

Why it matters for distribution: If you have a freemium product or want to build credibility, giving away genuinely useful free resources is the safest and most consistently rewarded strategy on r/gamedev. KenNL (Kenney) has multiple posts in the dataset and is treated as a community hero.

6. Format Analysis

What Format to Use For What

• Industry discussion / hot takes / postmortems -> TEXT. This is the dominant format and the most natural fit for r/gamedev's discussion-first culture. Long-form selftext posts with data, arguments, and personal experiences perform best.
• Technical tutorials / shader breakdowns -> VIDEO or IMAGE (GIF). Short visual demonstrations with code in comments achieve the highest ratios in the dataset.
• Industry news / platform announcements -> LINK. External links to PCGamer, The Verge, and other outlets perform well when the topic is inherently newsworthy.
• Free asset releases -> VIDEO (showing the assets in use) or TEXT (with download links). Preview the quality visually, then link to the download.
• Game showcases -> Not welcome here. Use r/IndieDev, r/IndieGaming, or r/playmygame instead.

What Makes a Good Technical Video

Top-performing video posts share these traits:

1. Under 90 seconds: "3 years of gamedev in 90 seconds" (6,636), "Procedural animation in 10 steps" (6,432). Brevity signals confidence and respect for the viewer's time.
2. Show the technique, not the marketing: The breakdown IS the content. No logos, no call-to-action, no "wishlist on Steam."
3. Before/after or step-by-step structure: "Stylized explosion shader breakdown" (8,217) literally breaks the effect into components.
4. Screen recording with minimal or no narration: The community prefers silent GIFs or screen recordings over talking-head tutorials.
5. Code or node graphs visible: Posts that include the actual implementation (even briefly) outperform those that only show the visual result.

7. Flair/Category Strategy

Best flairs for raw performance:

• Tutorial (avg ratio 0.98, avg score ~3,700): Near-universal approval. Use this when sharing educational content.
• Source Code (avg ratio 0.99, avg score ~3,700): Highest approval, but very niche. Requires actually sharing code.
• Assets (avg ratio 0.98, avg score ~3,400): Free resources always perform well.

Best flairs for distribution utility:

• Discussion (avg ratio 0.92, avg score ~2,800): Lower approval but generates the most comments and debate. This is where postmortems, industry opinions, and data-sharing posts live. If your goal is to be part of the conversation (and mention your product in context), Discussion is the vehicle.
• Postmortem (avg ratio 0.94, avg score ~2,600): Specifically designed for post-launch analysis. The community expects hard data and honest reflection.
• (none) (avg score ~3,500): Many viral posts have no flair. Don't overthink flair selection -- the content matters more.

Flairs to approach with caution:

• Game and Show & Tell: These exist but flirt with Rule 3. Only use if your post genuinely contributes knowledge beyond "look at my game."
• Question: Lower average score and often generates generic advice. Not a strong distribution vehicle.
• Meta: Reserved for community governance discussions. Don't use for product-related content.

Pricing model is irrelevant here: Unlike r/macapps (which has strong anti-subscription sentiment), r/gamedev does not have a pricing hierarchy. The community discusses pricing strategically (as in postmortems) but does not penalize any specific model.

8. Title Engineering

Top 10 Title Deconstruction

1. "An important reminder" (33,563) -- Vague but intriguing. Works because the image (which the community already knew) does the heavy lifting. This is an exception, not a formula.
2. "Just overheard my son and his friends start their own 'game development studio'..." (18,579) -- Storytelling hook with an ellipsis that promises a punchline. Uses quotes for ironic distance.
3. "Started coding this January, today I release my first game!" (13,168) -- Time-compressed journey. "This January" to "today" creates a satisfying arc in one sentence.
4. "Apple removed my game from the app store because some company in China made a clone..." (10,550) -- Injustice narrative with a specific villain (Apple, Chinese clone). The specificity signals credibility.
5. "Despite having just 5.8% sales, over 38% of bug reports come from the Linux community" (10,518) -- Counter-intuitive data headline. The specific percentages (5.8%, 38%) demand attention.
6. "Palworld is not a 'good' game. It sold millions" (7,647) -- Contrarian thesis in two sentences. The quotes around "good" signal intentional provocation.
7. "Steam is removing NFT games from the platform" (7,535) -- Pure news headline. No editorializing needed -- the fact itself is the hook.
8. "Unity silently removed their Github repo to track license changes..." (6,998) -- Accusatory tone ("silently") with specific evidence (Github repo). The ellipsis promises more damning details.
9. "Please refuse to work weekends and any unpaid overtime" (6,704) -- Direct imperative address to the community. Feels like a rallying cry, not a rant.
10. "3 years of gamedev in 90 seconds" (6,636) -- Time compression formula. The contrast between "3 years" and "90 seconds" is irresistible.

Title Formulas That Work

The Counter-Intuitive Data Point: "[Surprising statistic] + [implication]"

• "Despite having just 5.8% sales, 38% of bug reports come from Linux" (10,518)
• "Over 5,000 games released on Steam this year didn't make enough money to recover the $100 fee" (1,226)
• "Schedule I estimated steam revenue: $25 million" (1,521)

The Platform Injustice Story: "[Platform] did [bad thing] to [my game/work]"

• "Apple removed my game from the app store because..." (10,550)
• "Unity silently removed their Github repo..." (6,998)
• "This is how Steam can ruin more than 10 years of your work" (5,787)

The Time-Compressed Journey: "[Long time] of work in [short time] of content"

• "3 years of gamedev in 90 seconds" (6,636)
• "Started coding this January, today I release my first game" (13,168)

The Imperative Lesson: "[Do/Don't] [specific action]"

• "Please refuse to work weekends and any unpaid overtime" (6,704)
• "Do not, I repeat DO NOT use Arial in your projects" (4,378)
• "No. You're not going to add multiplayer later." (2,397)

Title Anti-Patterns

• No "check out my game" titles: Rule 3 makes these instant removals. In the top 100, zero posts have titles that read as product pitches.
• No vanity metrics without context: "My game got 5k wishlists" only works when followed by detailed data. Bare bragging without substance gets friction (see "My first game made $30k" at 0.83 ratio).
• No generic questions: "What engine should I use?" is explicitly banned in the submit text. Low-effort questions get buried.
• No AI-positive framing: Posts that frame AI usage positively receive the lowest ratios in the dataset. "If I use tab-autocomplete in my code editor, do I need to tell Steam my game is AI made?" (1,134, 0.80 ratio) was perceived as bad-faith.

9. Engagement Patterns

If your goal is VISIBILITY (maximum upvotes, broad reach): Use IMAGE or VIDEO format with a technical tutorial or wholesome story. These achieve the highest average scores with minimal controversy.

If your goal is RELATIONSHIPS and DISCUSSION (deep engagement, community credibility): Use TEXT format with a data-rich postmortem, industry opinion, or platform critique. These generate 3-4x more comments per upvote than visual content.

Highest-Discussion Topics (most comments regardless of score)

1. AI in game development: "So many new devs using AI" (1,163 score, 1,123 comments -- the highest C/U ratio in the dataset at 0.96). AI posts generate more debate per upvote than any other topic.
2. Pricing and marketing philosophy: "Sorry, your marketing isn't bad, your game is bad" (1,434, 691 comments). These opinion posts are comment magnets.
3. Industry injustice stories: "Op-Ed: The Same Fucks Who Fucked Steam Just Fucked Itch.io" (3,898, 873 comments). Righteous anger generates discussion.
4. Platform policy changes: "Unity announces new business model" (3,969, 1,328 comments). Policy posts consistently generate 500+ comments.
5. Career and life advice: "16yo watched 6 hrs of C++ on YouTube; knows C++ now" (1,671, 812 comments). Relatable frustration about unrealistic expectations.

10. What Gets Downvoted

Ratio Tiers

• Above 0.94: Universally well-received. Technical tutorials, free resources, and wholesome stories live here. 65% of the dataset.
• 0.85-0.94: Net positive but with friction. Opinion posts, industry hot takes, and AI-related content. 30% of the dataset.
• Below 0.85: Controversial or community-hostile. Only ~5% of the dataset, but these generate the most heated debate.

Notable Low-Ratio Posts

Anti-Patterns (Community-Specific)

1. The Tone-Deaf Success Brag ("My first game made $30k" at 0.83): Framing $30k as a failure while many developers would celebrate it. The community resents perceived humblebragging, especially when the post is heavily formatted with bold text and reads like marketing copy.

2. The Reductive Hot Take ("Sorry, your marketing isn't bad, your game is bad" at 0.85): Oversimplifying a complex issue (marketing vs. product quality) triggers defensive responses from developers who have experienced the randomness of success firsthand.

3. The AI Provocation (multiple posts, 0.73-0.80): Any post that appears to defend or normalize generative AI in game art receives the harshest pushback. Even nuanced takes get caught in the crossfire. The "tab-autocomplete" post (0.80) was perceived as a bad-faith slippery slope argument.

4. The Gatekeeping Lecture ("Gamedev is not a golden ticket" at 0.79, "Some of you seriously need to get that delusion out of your heads" at 0.88): Posts that lecture the community about unrealistic expectations, while often factually correct, are perceived as condescending. The community knows gamedev is hard -- they do not need to be told.

5. The Indie Purity Test ("Expedition 33 devs attempts to join the indie scene are harmful" at 0.76): Policing who gets to call themselves "indie" is deeply divisive. The community splits between those who want to protect the indie label and those who see the gatekeeping as destructive.

6. The Locked/Political Thread (multiple): Posts about Tarkov/Russia, NSFW censorship, and corporate politics that get locked by mods tend to have lower ratios, partly because the locking prevents late positive engagement.

11. The Distribution Playbook

Phase 1: Pre-Launch (4-8 weeks before)

1. Become a knowledge contributor first: Post 2-3 genuine technical tutorials or free resources related to your domain. A shader technique, an open-source tool, a detailed writeup on a problem you solved. This builds post history and community recognition.
2. Engage in Discussion threads: Leave thoughtful, data-backed comments on postmortems and industry discussions. The community remembers usernames that contribute substance.
3. Study the rule boundaries: r/gamedev's Rule 3 and Rule 4 are specific. You can share links if they "serve a valid purpose, such as seeking feedback, sharing a postmortem, sparking discussion, or offering a learning opportunity." Frame everything through this lens.

Phase 2: Launch Day

You cannot launch a product on r/gamedev. This is the single most important thing to understand. Instead:

1. Post a data-rich postmortem 1-2 weeks after launch: "Here's how my launch went -- every number I have." Include wishlist counts, conversion rates, traffic sources, revenue (if comfortable), and honest reflections on what worked and failed. Name your game naturally in context.
2. If you have a tool or engine: Post a tutorial that happens to use your tool. "How I solved [common problem] using [your tool]" is acceptable if the tutorial has standalone value.
3. If you have a game: Post to r/IndieDev, r/IndieGaming, or r/playmygame for the showcase. Use r/gamedev for the STORY of development, not the game itself.

Phase 3: First 24-48 Hours

1. Reply to every comment within 4 hours: r/gamedev's text-heavy discussion culture means the comment section IS the engagement. A postmortem with 50 thoughtful author replies outperforms one with 500 upvotes and silence.
2. Handle criticism with data, not defensiveness: If someone questions your numbers, methodology, or decisions, respond with more data. "You're right, here's what I would do differently" is the highest-credibility response on this subreddit.
3. Do not edit the post to add self-promotion: If your post gains traction, resist the urge to add "Edit: Check out my game at [link]!" The community will notice and the ratio will drop.

Phase 4: Ongoing Presence

1. Post follow-up data: "3 months later -- here's what happened after my postmortem post" is a proven format. The community loves longitudinal data.
2. Contribute to recurring threads: r/gamedev has regular feedback, question, and discussion threads. Being a consistent, helpful presence is worth more than any single viral post.
3. Cross-post strategically: Your r/gamedev postmortem can be cross-posted (or reframed) for r/IndieDev (more emotional, visual), r/IndieGaming (gameplay-focused), and r/SideProject (builder narrative).

Comment Strategy: Pre-Written Replies

"Is this vibe-coded / AI-generated?": "No. Here's the git history / development timelapse / process documentation showing [X months] of manual work. Happy to share more if you want specifics."

"Why not just use [existing tool/engine]?": "Great question. I evaluated [tool] and it didn't handle [specific use case] well because [technical reason]. I documented the comparison here: [link]."

"What's your revenue?": "Here are the exact numbers: [wishlists, conversion rate, units sold, revenue]. I'm happy to share more detail on any of these."

"This is just self-promotion": "I understand the concern. My goal was to share the data for other developers going through the same process. The game is named because it's the subject of the postmortem, not the pitch."

"Your sample size is too small / methodology is flawed": "Fair point. Here's the limitation: [acknowledge it]. I've shared all my raw data so others can draw their own conclusions."

Score-Tier Calibration

• Technical tutorials: Realistic ceiling of 4,000-6,000. Exceptional ceiling of 8,000+.
• Data-rich postmortems: Realistic ceiling of 1,000-2,000. Exceptional ceiling of 3,000-5,000.
• Industry opinion posts: Realistic ceiling of 1,000-2,000. Can go viral (7,000+) but at the cost of ratio.
• Free resource drops: Realistic ceiling of 2,000-4,000. Consistent but rarely viral.
• Direct product promotion: Zero. The post will be removed.

Post-Publication Measurement

• Ratio above 0.95 after 6 hours: You've hit the right tone. The post will likely continue to grow.
• Ratio 0.88-0.95 after 6 hours: Your post has friction. Check the comments for the point of contention and address it directly.
• Ratio below 0.88 after 6 hours: Your post is controversial. This is not necessarily bad for engagement (high C/U ratio) but it will cap your score ceiling. Do not delete -- controversy drives discussion.
• Under 50 upvotes after 4 hours: The post likely will not gain traction. Consider whether the title was clear enough or whether the content format was wrong for this community.

12. Applying This to Any Project

Quick-Reference Checklist

1. Have I contributed 2+ non-promotional posts to r/gamedev before posting about my project?
2. Does my post comply with Rule 3 (no showcasing) and Rule 4 (no blatant self-promotion)?
3. Is my post framed as a knowledge-sharing exercise with genuine standalone value?
4. Does my title use a proven formula (data headline, time compression, imperative lesson)?
5. Have I included hard numbers, not vague claims?
6. Is my post in TEXT format if discussion-oriented, or VIDEO/IMAGE if tutorial-oriented?
7. Am I prepared to reply to every comment within 4 hours?
8. Have I avoided any AI-positive framing that could trigger community backlash?
9. Does my post acknowledge failures and limitations honestly?
10. Have I saved the actual product showcase for r/IndieDev, r/IndieGaming, or r/playmygame?

Scenario-Based Launch Guides

If your product is free/open-source:

• Optimal formula: "I made [free resource] for the community" + VIDEO/IMAGE preview + clear license + download link.
• Key risk: Being perceived as building a mailing list or user base under the guise of generosity. Keep the post genuinely free with no strings attached.

If your product uses one-time/lifetime pricing:

• Optimal formula: Data-rich postmortem 1-2 weeks after launch. Include wishlist-to-purchase conversion, revenue, and marketing spend.
• Key risk: The community expects honesty about what went wrong. A pure success story gets less engagement than a balanced retrospective.

If your product uses subscription pricing:

• Optimal formula: Focus on the tool's educational/technical value rather than the business model. Post tutorials using your tool.
• Key risk: r/gamedev does not have strong anti-subscription sentiment like r/macapps, but subscription fatigue is real. Do not make pricing the focus.

If your product was built with AI:

• Optimal formula: Be transparent about AI usage, frame it as "AI-assisted" with human oversight, and show the human craft that went into the project.
• Key risk: This is the highest-risk scenario on r/gamedev. The community ratio for AI-positive posts is 0.73-0.85. If AI is central to your product, consider whether r/gamedev is the right subreddit at all. You may get more traction on r/ChatGPT or r/LocalLLaMA.

If your product is a game development tool or engine:

• Optimal formula: "I solved [common pain point] and here's the tool I built" + technical tutorial showing it in action + free tier or demo.
• Key risk: Being perceived as an ad. The tutorial must have standalone value even if the viewer never uses your tool.

Cross-Posting Guidance

The same project should be reframed for each subreddit: