
Game Overview
A self-engineered warrior fights to survive in a volatile far-future wasteland where the rules of each run are never quite the same. Metamancer combines action-RPG combat, roguelite unpredictability, and a world simulation that keeps changing around the player instead of serving up a fixed campaign. Neon ruins, poisoned marshes, scrapyards, data centers, and orbital wreckage give its procedural planet a harsh, synthetic atmosphere. The tone is aggressive and experimental: every expedition is about making the best of strange equipment, shifting territory, and enemies that may be better armed than expected.
Combat mixes quick melee encounters with a build system based on computer hardware. CPUs, GPUs, RAM, and rarer motherboard components determine active skills and modifiers, turning character progression into a grid-based equipment puzzle with room for unusual synergies. Generated weapons, armor, and shields support different approaches, while regenerating shields reward players who know when to disengage, reposition, and push back in. Enemies visibly carry the gear they can drop, so a difficult opponent is also a potential upgrade, and the loop revolves around fighting, looting, tuning a build, and venturing into more dangerous territory.
Its strongest idea is the degree of procedural variation: maps, sprites, loot, dialogue, quests, and even market conditions are designed to avoid familiar repetition. Four rival factions struggle across the overworld in two competing alliances, claiming tiles, erecting strongholds, and altering available routes as their borders move; choosing a side affects reputation and opportunities. Trading matters because the economy responds to the wider simulation rather than acting as a simple vendor menu, while the many biome types prevent runs from feeling visually uniform. Players who enjoy Diablo-style loot chasing, Hades-like run adaptation, or the item-grid theorycrafting of games such as Backpack Hero should find plenty to experiment with, though its dense systems suit patient tinkerers more than anyone seeking a purely straightforward hack-and-slash.
Screenshots
Installation
- Select the Download button at the top of this page to open UploadHaven.
- On UploadHaven, wait for any countdown, then select Free Download. Optional: UploadHaven Pro for faster downloads.
- When complete, extract the archive to a Metamancer folder using 7-Zip.
- Open the extracted folder and start the game normally.
- For errors, check Setup Guide & Troubleshooting below. Keep your security software enabled.
System Requirements
- OS: Windows 10
- Processor: i5 7700k
- Memory: 2 GB RAM
- Graphics: AMD R9 290
- Storage: 80 MB available space
- Additional Notes: Works best on 16:9 monitors.
Setup Guide & Troubleshooting
How do I fix missing DLL errors for Metamancer (v1.10)?
After extracting Metamancer (v1.10), navigate to the _Redist or _CommonRedist folder inside the game directory and install DirectX, Vcredist, and any other dependencies included.
What should I do if the downloaded file is corrupted?
The full archive is 154.77 MB — make sure your download completed fully before extracting. Use 7-Zip to extract the files. If you still see a "file corrupted" error, re-download and try again.
Do I need to run the game as administrator?
Usually, no. Start the game normally from the extracted folder. If you see a permissions or save error, check that the folder is writable and follow the game's documented fix. Only grant administrator access when a trusted game's specific setup requires it.
How do I update my GPU drivers for this game?
The game won't launch — what should I try?
Check that extraction completed and your PC meets the system requirements. Note any error message before choosing a fix. If it identifies a missing runtime, install the required DirectX components or Microsoft Visual C++ Redistributable from Microsoft.
My antivirus is blocking the game — is it safe?
A warning needs to be investigated; the download source alone cannot confirm that a file is safe. Keep your security software enabled and review the detection details. Do not run or restore a flagged file unless you have verified that it is a false positive. If you are unsure, leave it quarantined.