Fox Studios logo Fox StudiosGame projects, devlogs and Scratch builds
Community

Giving Useful Feedback on Other People's Games

Scroll the comments under almost any shared Scratch game and you will see the same three replies over and over: "cool", "too hard", and "add more levels". None of them are mean. None of them help either.

Two young game makers looking at a laptop screen and writing notes about a shared game

Scroll the comments under almost any shared Scratch game and you will see the same three replies over and over: "cool", "too hard", and "add more levels". None of them are mean. None of them help either. The person who made the game reads them and still has no idea what to change.

Giving feedback on other people's games is a skill, and it is one of the fastest ways to get better at making your own. When you have to explain why a jump feels wrong, you start noticing it in your own projects too. This is how our studio gives feedback to each other and to the community, with the exact phrases we use.

Why Most Game Feedback Gets Ignored

Feedback gets ignored for two reasons: it is too vague to act on, or it tells the maker what to build instead of what happened. "Make it better" is vague. "Add a shotgun" is a design order. Neither one tells the maker what you actually experienced while playing.

The useful part of any feedback is the experience. The maker knows their code, their plans and their intentions. The one thing they cannot know is what it felt like to play the game fresh, without knowing where the secret door is. That is the only thing you have that they do not, so that is what your comment should be about.

Play It Properly Before You Comment

This sounds obvious, but a lot of comments are written after 30 seconds. Before you give feedback on a game, give it a fair go.

  • Play for at least five minutes or until you finish or quit for real.
  • Read the instructions and notes, because the answer to "how do I jump" is often there.
  • Play twice if it is short. The second run shows whether it is fun once you know the rules.
  • Note the moment you first felt confused, bored or annoyed. Write down the level or the second it happened.

That last point is the most valuable thing you will collect. "I got stuck on level 3 at the moving platform" is gold for the maker.

A Simple Format for Feedback on Other People's Games

We use a three part format inside our studio. It keeps comments short and makes them easy to act on.

One thing that worked

Start with something specific you liked. Not "nice game" but "the sound when you collect a coin is really satisfying". It tells the maker what to keep, which is just as useful as what to change.

One moment that did not work

Describe what happened, not what they should do. "I died four times on the second jump because I could not tell where the edge of the platform was" gives them a real problem to solve. They might fix it with a brighter edge, a bigger platform or a shadow. That choice is theirs.

One question

Ask something you were curious about. "Is the blue key supposed to open the first door?" Questions often reveal bugs or confusing design without sounding like a complaint.

The whole comment can be three sentences. Short and specific beats long and general every time.

Phrases That Help and Phrases That Hurt

Instead ofTry
This is too hardI could not get past the third enemy after eight tries
BoringI stopped playing around level 2 because it felt like level 1 again
Controls are badI kept pressing space to jump, but it was the up arrow
Add more levelsI finished in two minutes and wanted to keep going
Your art is badI could not tell the enemies apart from the background

Notice that every phrase on the right describes something that happened to you. The maker cannot argue with it, because it is simply true.

Why "Just Be Nice" Is Not Enough

A lot of community guidelines say the most important rule is to be positive. Kindness matters, and we never post anything cruel. But only positive feedback does a maker no favors.

When every comment says "awesome game", the maker learns nothing and keeps the same problems in their next project. We have seen games with 40 friendly comments where nobody mentioned that the final level could not be completed. The kind thing would have been to say so.

Honest feedback can be friendly. Lead with what worked, describe the problem calmly, and never make it about the person. "This level confused me" is honest and kind. "You clearly did not test this" is neither.

Giving Feedback to Beginners Versus Experienced Makers

Adjust how much you say to how far along the person is.

For someone sharing their first game, pick one thing to praise and at most one thing to change. A first project with a list of eight problems under it can make a new maker quit, and the community loses someone who might have made something brilliant on their third try.

For an experienced maker who asks for feedback directly, you can go deeper. Mention game feel, difficulty curve, pacing between levels and how the menu works. They asked because they want the detail.

If someone posts "please give feedback", that is your sign they are ready to hear more than "cool". Found a bug? Give the steps to make it happen again: which level, what you pressed, and what you expected. "On level 4, if you jump while touching the wall, you get stuck inside it" lets the maker fix it in minutes instead of guessing.

What We Learned From Receiving Feedback

We get feedback on our own games too, and being on that side changed how we give it. When we sorted every comment on one project, the ones we could actually use all described a specific moment. The rest we could not do anything with. We wrote about that process in sorting 63 player comments into fixes.

If you want to practise giving feedback in a safer setting first, try it with friends sitting next to you. Our guide to playtesting a game with friends shows how to watch someone play and take notes without steering them.

Game Feedback FAQ

What if I did not like the game at all?

Find the one part that worked best and mention it, then describe where you lost interest. You do not have to pretend you loved it, and you do not have to list everything you disliked.

Should I suggest features or ideas?

Only if the maker asks for ideas. Otherwise describe what you experienced and let them decide how to solve it. Their game is their design.

How long should a feedback comment be?

Three to five sentences is plenty for most shared games. Longer is fine if the maker asked for detailed feedback or if you found a bug they need to reproduce.

Try It on the Next Game You Play

Next time you play something shared by another maker, write one thing that worked, one moment that did not, and one question. Post it, then watch how the maker replies compared with the "cool" comments around it. You can find more ways to support other makers in our community posts.

MK
Mira Kovac

Mira teaches coding to beginners and writes the step-by-step guides, always testing each one on someone who has never coded before.

More posts by Mira

More in Community

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto