2 lines
5.9 KiB
JavaScript
2 lines
5.9 KiB
JavaScript
|
import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.Mb1uu3dm.js";const p=JSON.parse('{"title":"Guide to Incrementals/Navigating Criticism","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/navigating-criticism","title":"Guide to Incrementals/Navigating Criticism","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/navigating-criticism/index.md","filePath":"garden/guide-to-incrementals/navigating-criticism/index.md"}'),n={name:"garden/guide-to-incrementals/navigating-criticism/index.md"},o=i('<h1 id="guide-to-incrementals-navigating-criticism" tabindex="-1">Guide to Incrementals/Navigating Criticism <a class="header-anchor" href="#guide-to-incrementals-navigating-criticism" aria-label="Permalink to "Guide to Incrementals/Navigating Criticism""></a></h1><p>Developing games is fun and exciting and teaches a lot of wonderful skills - I enthusiastically encourage anyone with an interest in game development to try it out - and incremental games are a wonderful way to get started. However, there are many challenges young and inexperienced developers have to face, and I think the hardest one - harder than coding, debugging, balancing, etc. - is handling criticism. When you put your heart and soul into a game it is natural to feel very vulnerable. While I think there's a lot communities can do to ensure they're welcoming, positive and constructive with their criticisms, inevitably you will eventually read some, and potentially a lot, of comments that can deeply affect you. No one is immune to this, from young incremental game developers to the largest content creators you can think of. That's why it's important to be able to process and navigate criticism, because ultimately collecting feedback is essential to the journey to becoming a better developer. On this page, we'll explore how to embrace criticism, grow from it, and continue to post your games publicly with confidence.</p><h2 id="reading-feedback" tabindex="-1">Reading Feedback <a class="header-anchor" href="#reading-feedback" aria-label="Permalink to "Reading Feedback""></a></h2><p>Game development is a skill that takes time and practice to get truly great at. Criticism and other constructive feedback are vital to continually improving. It's useful to look at the criticism as solely a tool for improving this game and future games - that is to say, it should never be used against you as a person. Insults towards the developer(s) themselves are never okay and should not be allowed within whatever community you're sharing your works in. If you do come across a comment you interpret as an attack upon your person, you should report it. For other negative comments, try not to internalize them; instead, focus on improving the game. By distancing your own identity from your work emotionally, you can better analyze the game and use the feedback to your advantage.</p><p>Not all feedback is made equal, and you don't need to feel compelled to read and obey every piece of feedback you receive. Learn to distinguish between constructive feedback and unhelpful comments. Constructive feedback typically offers specific suggestions for improvement, while unhelpful comments are often vague or hurtful. Prioritize the former and disregard the latter. That said, most feedback you get will not be from game developers, so take specific suggestions with a grain of salt. Determine the actual problem they're experiencing, and design what you believe the best solution to that problem would be, regardless if that's the specific solution the player asked for. And keep in mind, due to different player preferences you'll never satisfy everyone, and you don't need to. Ultimately if even just you find the game fun, then that's a success.</p><h2 id="seeking-feedback" tabindex="-1">Seeking Feedback <a class="header-anchor" href="#seeking-feedback" aria-label="Permalink to "Seeking Feedback""></a></h2><p>When deciding where to share your game, consid
|