Arcane Energy is a personal game and tool development space. The projects on this website are mostly made with Godot, and small custom tools built around game development workflows. The archive contains finished games, prototypes, shaders, editor addons, tutorials, and technical experiments.
Focus
Most projects start from a small mechanic or workflow problem. A sandbox game may begin with fire propagation, a tool may begin with a single export format, and a shader may begin as a small visual test before becoming something reusable.
The projects are usually built in small steps. First the core interaction has to feel clear, then the surrounding systems can grow around it. For games, this often means testing movement, physics, destruction, UI, or progression before committing to a larger structure. For tools, it means keeping the workflow direct enough that the tool stays faster than doing the same task by hand.
Games and Experiments
Many of the games here are compact ideas that were finished, expanded, or archived after they served their purpose. Some are mobile games, and some are jam projects that later became larger releases. The common thread is that each project tries to focus on one recognizable idea instead of spreading itself across too many systems at once.
Sandbox projects are a recurring theme because they leave room for systems to interact. Fire, weather, physics, elements, and player-created content can produce results that were not authored directly. That kind of behavior is useful for games, but it is also useful for learning how separate systems affect each other.
Smaller prototypes are kept for the same reason. Even when a prototype does not become a full game, it can still contain a useful camera controller, inventory model, shader, save system, or editor workflow. Those pieces often become reference material for later projects.
Tools
The tool projects are usually built around a practical production need. A level editor exists because placing tiles manually is slow. A scatter tool exists because placing hundreds of meshes one by one is not a good use of time. A whiteboard app exists because notes, sketches, images, and presentation points can belong in the same workspace.
The goal with these tools is not to cover every possible use case. It is to make one workflow understandable and repeatable. A tool can stay small and still be useful if its data format is clear, its controls are predictable, and its limitations are visible.