The difference between a working handler and a working experience.
Imagine clicking on a furnace, starting a combat encounter or trying to reach a dungeon entrance. Each action crosses multiple systems: movement, interaction distance, collision, animation, inventory, requirements and the final result. When only some of those pieces are present, the activity may look implemented in a checklist but still feel broken in-game.
Our development approach considers those connected steps. We are interested in whether a player can find an activity, begin it, understand the response and complete it without an unexpected dead end.
Combat needs readable feedback.
Timing, reach and presentation make combat understandable. A boss or monster needs appropriate attacks, while the player needs to see when an action starts and how it lands. An incorrect projectile or animation can make even valid damage confusing. Getting that right requires both system testing and actual game sessions.
Loot and defeat matter too. Items awarded or recovered after an encounter have to follow consistent rules. A narrow test result might verify one part of the process, but the full player experience includes the journey back to the bank, reconnecting and returning for another attempt.
Skills need a complete loop.
Take a typical gathering or production activity. Clicking the object is the beginning, not the end. A convincing implementation considers the player's tool, resources, animation, reward, XP, inventory space and access to the next step. A skill method that drops an item but cannot lead to meaningful progression does not yet meet the same quality bar.
That same thinking applies across the world. Shops, banks, NPC positions and travel routes must make sense together. World population should serve gameplay rather than simply increase the number of spawned characters.
How these observations shape our roadmap.
The exact feature set available to testers will change as repairs and checks proceed. We avoid labelling everything as fully ready just because a few tests pass. Instead, our goal is to communicate what is being worked on, where feedback is useful and what an active test build actually supports.
See the current development stage and upcoming RSPS overview for context. If you notice a similar issue while testing, our testing page explains how to report it helpfully.