Starting with version 0.7.9, our game has been released simultaneously for Windows, macOS, Linux, and Android. The Android version, in particular, presented the most challenges. Rather than releasing a separate, stripped-down version for mobile devices—as is customary—we adapted all internal systems so that the game would be identical across all operating systems.
Now let’s talk about the input system. We didn’t add in-game toggles to switch between keyboard and gamepad, gamepad and touchscreen, and so on. Instead, the game automatically detects the input device in real time and switches to the appropriate one. For example, you can connect a gamepad or touchscreen to your PC, or a keyboard or gamepad to your phone—and everything will work and switch seamlessly without any configuration. We flatly refuse to include manual input settings in order to prioritize convenience for players!
Now, let’s talk about the issues we encountered. In all versions following v.0.7.9, we received a huge amount of feedback regarding control issues on touchscreens—the control buttons sometimes disappear, and you have to open the menu to fix it.
The thing is, we use Unity as the game engine, so we’re limited in what we can do. The available functionality was barely sufficient for implementing an adaptive input system, since the engine’s developers didn’t originally anticipate anyone creating such a versatile system. Up until now, we’ve been using the standard functionality—as Unity intended. But it seemed to be throwing a wrench in our plans, for example, by creating a virtual keyboard during touchscreen controls, which naturally made it difficult to identify the actual input device. So, in the end, we decided to resort to a few workarounds to get around these issues. Now the input system operates based on our own custom logic, which differs from Unity’s original design but is more efficient, stable, and bug-free.