How Lokko's Feedback System Works

📊 Feedback that disappears into a form nobody reads isn't feedback — it's a suggestion box in a closet. Lokko's feedback system is built specifically so that doesn't happen. What you submit in-game is visible on a public dashboard almost immediately, and it's the same raw data the team actually reviews. Here's exactly how it works, end to end.

Step 1: You Submit Feedback In-Game

A feedback pipeline is the full path a piece of feedback travels — from the moment someone submits it to the moment it either shows up publicly, gets acted on, or both. Lokko's starts with the in-game feedback option, where you write what you want to say and give it a rating. Behind the scenes, your submission also carries basic system info — platform, operating system version, and system language — automatically, so the team can see patterns like "this only happens on PS5" without you having to describe your setup yourself. You can also attach a screenshot if it helps make the point.

Step 2: It Goes Live on the Public Dashboard

Once submitted, feedback shows up on the public feedback dashboard — not after a review cycle, not curated for positivity, just the real submissions as they come in. Anyone can visit it and filter by platform, date range, rating, or search for specific text. This is deliberate: the same data the team looks at internally is the data you can look at too.

See Live Feedback

Step 3: The Team Sorts It Into Something Workable

Raw feedback at volume is noisy — one-word entries, duplicate submissions, test data, and genuinely substantive reports are all mixed together. Sorting that into something a developer can actually act on is its own step, done with an internal review tool built specifically for this. Feedback gets sorted by length (substantive entries first), filtered by platform, and anything irrelevant or duplicated gets hidden from the working view without being deleted from the record. What's left is a shortlist that's actually worth a developer's time.

Not every piece of feedback needs a response — but every piece needs to be looked at once before that decision gets made. The sorting step exists so that judgment call happens deliberately, not by accident.

Step 4: Patterns Get Tracked Over Time

Individual pieces of feedback matter, but patterns matter more. Alongside sorting, the team tracks feedback trends — average rating by platform, how ratings move over time, and submission volume — to catch shifts that a single piece of feedback wouldn't reveal on its own. A rating that's quietly dropping on one platform over a few weeks is a very different signal than one player having a bad session, and trend tracking is what surfaces the difference.

Step 5: It Actually Changes Something

Sorting and tracking only matter if they lead somewhere. They do. See our companion post on what Early Access feedback changed about our game for concrete examples pulled directly from this exact pipeline — real quotes about friends, multiplayer, combat feel, and achievements, and what came out of taking them seriously.

Why Sorting and Trend-Tracking Are Two Separate Steps

It would be simpler to fold sorting and trend-tracking into one step, but they're solving different problems and would interfere with each other if combined. Sorting is about a single moment — is this one piece of feedback substantive enough to act on right now — and it necessarily throws away context to move fast, which is exactly right for that job. Trend-tracking is the opposite: it only works by keeping everything, including the short, low-substance entries that sorting would deprioritize, because a pattern across a thousand two-word ratings is invisible if you've already filtered most of them out. Running both off the same filtered view would blind one of them to exactly the signal it needs.

Why the Dashboard Is Public

Most games treat player feedback as an internal-only asset. Lokko's dashboard being public is a deliberate choice: it means nobody has to take our word for what players are actually saying, positive or critical. If you want to check whether a complaint you have is already known, or just see what other players think, the same real data is one click away.

Browse the Feedback Dashboard

Key Takeaways

• Feedback submitted in-game carries your rating, written comment, platform, and system info automatically — no need to describe your setup yourself.
• It appears on the public dashboard at /viewFeedbacks.html immediately, unfiltered and uncurated.
• The team sorts raw feedback by substance and platform using a dedicated review tool, hiding noise without deleting the record.
• Feedback trends (rating by platform, rating over time, volume) get tracked separately from individual submissions, to catch slow shifts a single comment wouldn't reveal.
• The pipeline leads somewhere — see what Early Access feedback changed about our game for real, specific results.