Decurion by Luminous Lore
2026-03-23
Tip: browser add-ons such as “YouTube Transcript Copy”, “Video Resumer” and “Tweaks for YouTube” add handy video features.
Playtest type: Blind (zero knowledge) – important to make players not leave/return too early. Developer-focused feedback on onboarding clarity, controls & input behavior, UI readability, combat feel, progression systems, and visual consistency.
Hi! If you are the developer and you have specific questions let me know so I can improve my gametesting!
A stylish retro-futuristic arena concept with strong mechanical potential, but currently held back by input issues and clarity gaps.
🎬 Trailer & Presentation
Intriguing style and strong first visual hook; aesthetic mix stands out immediately.
⏱ First 5 Minutes Impression
Good initial feel and music. But its a demo with a control bug so else, i think it reminds well of 90s games.
🧭 Onboarding & Clarity
Ability usage, AP system, and UI terminology take some time to get get.
🔥 Fun Factors & Peak Moments
Dash, reflect, and combat flow feel satisfying when inputs work properly.
😴 Boredom Threshold
Core loop is engaging, but confusion and lack of clarity risk early drop-off.
👍 What works well
Strong combat feel, great music, appealing 3D models, and interesting tactical layer.
⚠️ Biggest friction points
Input blocking, unclear mechanics (AP, abilities), UI readability, and inconsistent feedback.
🐞 Bugs / Crashes
Major input issues, menu lock, and inconsistent behavior with core/shield interactions.
💡 Ideas
More dynamic objectives (moving core), clearer UI/feedback, stronger visual cohesion.
⏳ Timestamps
00:04:33
I switch to controller but there is no proper support or transition → controller integration feels incomplete.
00:05:35
Movement input gets blocked after holding a direction → critical gameplay bug affecting control reliability.
00:07:24
Input blocking persists after restart → issue is consistent and not session-specific.
00:09:36
Pixel art enemies clash with 3D environment → visual inconsistency reduces immersion.
00:11:19
Post-run stats screen uses unclear terms (AP, save costs, evolve) → lacks readability and onboarding explanation.
00:14:59
Start button prompt is not obvious → small UX friction before gameplay resumes.
00:19:17
Enemy damage feels unclear/unfair (sudden death without clear feedback) → needs stronger hit feedback.
00:20:45
Core damage rules are unclear (shared damage vs separate?) → system understanding gap.
00:21:46
Cannot retry or interact with UI → temporary softlock.
00:23:20
Retry only works after multiple clicks → unreliable UI interaction.
00:25:37
Mech ability (dash/melee) unclear at first → onboarding does not communicate abilities effectively.
00:28:52
AP system unclear (no understanding of how to regenerate) → missing core system explanation.
00:30:33
“Save” mechanic appears without context → unclear purpose or impact.
00:33:05
Core suddenly moves/jumps without explanation → surprising but interesting mechanic, needs clarity or intentional design.
00:35:35
Respawn feedback is visually weak → lacks urgency or clarity to prompt action.
00:36:27
I can damage my own core → unclear if intentional, feels punishing without feedback.
00:37:52
Shield does not damage enemies → feels unintuitive given its visual/physical presence.
00:38:52
AP pickup finally explains system indirectly → feedback should be introduced earlier.
00:39:16
Inconsistent interaction with shooting through shield/core → rules feel unreliable.
00:40:48
Upgrade system discovered too late → progression mechanics not surfaced early enough.
00:46:03
Map/mode variety visible only at end → strong feature hidden too late in experience.
#indiedev #gamedev #playtest #feedback #uxdesign #indiegames #gameplayfeedback
My reports are free! In case you feel like you want to support me helping indie games by playtesting you can: ☕ https://ko-fi.com/akton1
In case you like my reports and want me to playtest your game: https://ko-fi.com/akton1/commissions
