Getting Slaying The Dragon Running on Your Machine
Slaying The Dragon is a free, open-source roguelike game built with the Godot engine. It's available on GitHub under the MIT license, and it runs on Windows, Linux, and macOS. The game features procedurally generated dungeons, real-time combat, permadeath, and a voxel-based art style that was the result of a year-long community effort. I installed it on an Ubuntu 22.04 system last year and ran into an issue right away — the default build process expects Vulkan support, and my hardware was limited to OpenGL 4.5. The game refused to launch with the standard Godot export. I ended up recompiling with the GLES3 renderer flag enabled, which added a build step but got it running. If you're on older hardware or using certain integrated graphics, this is the same path you'll need to take.
Slaying The Dragon Download and Installation
The source code lives at github.com/AlexNiles/SlayingTheDragon under the "releases" section where prebuilt binaries are posted for Windows and Linux. If you grab a prebuilt Linux version, you should be able to extract it and run the binary directly after making it executable. For the Windows build, just unzip and launch the .exe. If you want to compile from source, you need Godot 4.x installed. Clone the repository, open the project in the Godot editor, and export. The build typically takes about three to five minutes on a decent machine, maybe longer if you're doing a full debug export. Production builds strip unnecessary debug symbols and compress the exported files. The Linux package is distributed as a tarball. Extract it to wherever you keep your games, open a terminal in that directory, and run the executable. There is no installer. On Windows it is a single folder with a launcher and some DLLs. On macOS you may need to disable Gatekeeper for the first launch, which means right-clicking the app and selecting Open to bypass the restriction warning.
One thing people usually miss when installing is that the game creates a save directory in ~/.local/share/slayingthedragon on Linux. That is where your character data, settings, and logs live. If you move the game folder around or reinstall, the saves persist. I spent about ten minutes confused the first time because I thought I had lost my character — the game folder moved, but the data folder stayed behind, which meant the game saw a new empty profile instead.
Get the Full Details
How the Game Actually Works
The core loop is straightforward: enter a dungeon floor, fight enemies, collect loot, reach the boss room, survive, and descend. Death is permanent for that character. The game tracks multiple characters, so each one you create is a separate run. Stats are randomized at creation based on a class selection — warrior, ranger, mage, and cleric — and each class scales differently. The procedural generation uses a BSP (binary space partitioning) algorithm to create rooms and corridors. The layout changes every floor, but there is a deterministic seed system built in. If you enter a specific seed code, the dungeon will be identical across runs. This is useful for sharing interesting layouts or practicing specific routes. The seed display appears in the top-left corner once you start a floor. Combat is real-time. You swing your weapon or cast a spell on cooldown. Enemies have simple AI states — patrol, chase, attack — and they cluster in ways that can ambush you if you advance too quickly into unexplored areas. The minimap reveals tiles as you walk past them, which is helpful but also a crutch if you rely on it too heavily.
The loot system drops gear with random stat rolls. Item rarity is color-coded: white, green, blue, purple, and gold. Gold-tier items have the widest stat variance and sometimes include special modifiers that change how a weapon or armor piece functions. The value of gold items depends heavily on build synergy. A high-damage sword with poor scaling for your class is worse than a mid-tier item that matches your stat distribution.
Things That Are Not Obvious
Most players figure out the controls within a few minutes. The things that trip people up are the less visible systems. Stamina management is the first bottleneck. Every sprint and heavy attack drains the stamina bar. If you sprint into a group of enemies and have no stamina left, you cannot dodge or attack effectively until it regenerates, which takes roughly two seconds of not moving. I learned this the hard way on a night run when I sprinted straight into a pack of four enemies, burned through my stamina, and died before the bar refilled. The fix is simple — pause between pushes and let stamina recover before engaging another cluster. The inventory has a weight limit. Beyond a certain threshold, your movement speed decreases and your stamina regeneration slows. I initially ignored this and carried every item that dropped because the UI does not show a weight percentage — it only displays a numeric value. Once I started tracking the limit relative to my class's base capacity, I found that dropping low-rarity white items early in a run kept my mobility significantly better. The tradeoff is that you might need an item you discarded later, but most runs end before that becomes a real problem.
Cleric healing spells have a hidden cooldown. The UI does not indicate this. When you cast a heal, there is a brief window where casting another spell interrupts the recovery animation and wastes the second cast. This caught me off guard during a boss fight when I tried to chain a heal and a light attack together, and the heal failed silently. Waiting for the animation to complete before casting anything else resolved it.
Known Limitations and Where It Falls Apart
The game is still in active development. Some builds have memory leaks that cause performance to degrade the longer a run goes on. I noticed frame rate drops after about forty minutes of continuous play on Linux, which suggested garbage collection pressure in the Godot runtime. Restarting the game clears the issue. Windows builds tend to handle this better based on community reports, but it is not guaranteed. Certain enemy types spawn with behavior flags that can soft-lock a run. I encountered a situation on floor twelve where an enemy's attack pattern entered a state where it could not lose aggro and would chase the player through walls at maximum speed. The only workaround was to restart the run. This is not common, but it has happened enough times in community threads that it is worth noting. The game does not have a robust difficulty slider. The closest thing is a "challenge mode" toggle that increases enemy health and damage across the board, but it also changes loot drop rates in a way that is not clearly documented. If you want a gentler introduction, start on the default setting and level a character up before trying harder content. The XP curve is forgiving enough that a few runs will get you to a comfortable power level.
If you prefer turn-based roguelikes with deeper build complexity, games like DCSS or Caves of Qud offer more mechanical depth. Slaying The Dragon is faster-paced and more accessible, but it sacrifices some of that complexity for simplicity. That is not a flaw, it is just a design choice.
Controls and Key Bindings
Movement uses WASD or arrow keys. Left click attacks. Right click casts the selected spell. The number keys 1 through 5 select spells or abilities. The E key interacts with objects. I opens the inventory. M toggles the minimap. F toggles fullscreen on supported systems. These defaults can be changed in the settings menu, which is accessible from the main menu or by pressing Escape during gameplay. One practical tip: bind your healing spell to a number key that is easy to reach without moving your hand from the movement cluster. Fumbling for the cast key during a fight costs more time than you might think, especially when stamina regeneration is ticking down.
Performance Tweaks for Older Hardware
If you are running the GLES3 build on weaker hardware, lowering the render scale to 0.75 in the video settings usually improves frame rates without making the game unplayable. Disabling post-processing effects helps too. The game is not demanding by modern standards, but the voxel rendering pipeline can stress older GPUs if all effects are enabled. I also recommend closing background applications before launching. The game does not prioritize GPU resources aggressively, so any competing process will make the difference between a smooth 60 frames and a stuttery 40. The developer posts update notes on the GitHub repository. Each release usually includes bug fixes, balance adjustments, and occasionally new content. Checking the release history before downloading a fresh copy will tell you what has changed and whether a known issue has been resolved in the latest build.
