Video summary
Your game idea (probably) sucks
Main summary
Key takeaways
Storyline
This video is a non-story “rant”/advice guide rather than a game narrative. It argues that many proposed game ideas fail because the core idea is flawed, not because of lack of effort.
Core Message: The 5 Most Common Issues With Game Pitches
-
The scope is too big for the developer
- Examples: solo dev pitching massive open-world MMO-style projects.
- Why it hurts: unrealistic timelines and long gaps before feedback.
- Consequence: you can’t finish/iterate fast enough; marketing is also harder because much content won’t be ready.
- Fix: “stone down”/reduce scope to something you can build and get playable feedback on within ~6–12 months (it may balloon, but should remain realistic).
-
The concept is too vague (especially “artsy” ideas)
- Example: “Return to [X] but with meaningful choices.”
- Why it hurts:
- You can’t explain mechanics, perspective/viewpoint, player actions, and the end goal.
- Marketing fails because you can’t write a clear Steam description.
- Development can stall into constant pivots and leftover unfinished mechanics (“Lovecraftian mess”).
- Fix:
- Write a clear elevator pitch.
- Use a simple Steam short description exercise early to validate clarity.
-
The game is too derivative (clone/reskin with little novelty)
- Examples: “Like Among Us, but with pirates/space” style pitches.
- The video also references a trend analogy: outreach gets harder once novelty fades and others have already covered similar games.
- Why it hurts: players/content creators prefer originality or meaningful improvements; otherwise you’re competing with “better versions.”
- Fix: add a real differentiator, not just a theme swap.
-
You’re not being honest about market viability (making a niche game only for yourself)
- Problem: some devs make games only ~4 people care about (the creator plus a few friends).
- Why it hurts:
- Steam visibility, content creator interest, and marketing conversations break down.
- You may end up “spinning up a company” and paying Steam costs without realistic financial goals.
- Fix: decide whether you’re building for Steam market/finances or simply learning/dev craft—and avoid flooding Steam with ultra-niche releases.
-
The genre/timing is “too late” or overcrowded
- Examples: generic 2D platformer/Metroidvania pitches trying to compete with established “kings” (Silksong and Hollow Knight referenced as context).
- Desktop idlers: the video claims the boom wave has passed; there are many idlers and limited attention (you can generally only run one at a time).
- Also warns that long development cycles can miss hype waves.
- Fix: find the overlap where the game you want to make, the game you can make, and the game people want to play intersect—and be realistic about differentiation and timing.
Practical Validation Exercise / Key Tips
- Write a Steam short description in ≤ 300 characters as early as “day one” of the idea.
- Include:
- Perspective/viewpoint
- Verbs (what the player actually does)
- Main goal
- Environment/genre
- Include:
- Rule of thumb: if you can’t do this, the idea may be too vague to market and possibly too uncertain to develop.
Gameplay / Strategy Highlights
No specific mechanics from particular games are discussed. Instead, the video emphasizes process strategies:
- Build a small scoped core gameplay loop quickly (even within ~2 weeks) to get feedback.
- Don’t wait years to show anything when big-scope games delay feedback cycles.
- Use Steam page/short pitch clarity as a development and marketing gate.
- Ensure novelty so content creators and players have a reason to care.
Mentioned Gamers / Sources (End)
- Eric Barone
- Bite Me Games (channel/host referenced)
Referenced Games/Brands (Sources/Examples)
- Among Us
- Overcooked
- Vampire Survivors
- Factorio
- Timberborn
- Hades / “Heretics Fork” (mentioned comparatively alongside Vampire Survivors in the derivative discussion)
- Viking/RTS examples (general discussion)
- Dungeons & Dragons (D&D)
- Silksong
- Hollow Knight
- Desktop idlers
- Unicycle Pizza Time (trend example)
- Unity (development environment mentioned)
- Steam (distribution/marketing reference)