
Game Overview
A satanic child stalks a hospital and small-town streets in a horror sandbox built around murder, mischief, and supernatural revenge. Lucius II continues the first game’s story after its young antihero survives the destruction of his family home and is placed in St. Benedict’s Hospital, where Biblical prophecy and suspicious new enemies complicate his rise to power. The tone is gleefully nasty rather than traditionally frightening: it plays like a B-movie horror playground where the player controls the monster. Gore, dark comedy, and references to classic horror films define an experience that is deliberately tasteless in the way old slasher cinema often is.
Players guide Lucius through a five-floor hospital and the surrounding town of Ludlow, searching for targets, useful objects, secrets, and opportunities to cause lethal accidents. The central loop revolves around observing routines, collecting tools, manipulating the environment, and combining items into traps that can be triggered in different ways. Supernatural powers return and can be selected to shape Lucius toward telekinesis, mind control, fire-based tricks, and other malicious abilities, while missions generally ask for specific victims without forcing a single solution. More than 100 potential victims populate the game, and each major area functions as an open-ended murder sandbox where timing, location, and method are largely up to the player.
Its strongest idea remains the reversal of standard horror-game roles: instead of hiding from a killer, you are the killer planning the scene. Lucius II trades the original’s more tightly guided structure for broader maps and freer experimentation, although that ambition also makes its stealth, AI behavior, and controls feel rough around the edges. Players who enjoy the improvised chaos of Hitman’s accident kills, filtered through supernatural slasher nonsense, find plenty to experiment with here. Horror fans who value polish, sympathetic characters, or genuinely tense survival gameplay may struggle, but veterans of cult-budget horror games can appreciate its nasty sandbox spirit.
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 Lucius II 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 XP
- Processor: Dual core
- Memory: 4 GB RAM
- Graphics: NVIDIA GEFORCE GTX 275 or better
- DirectX: Version 9.0
- Storage: 5 GB available space
Setup Guide & Troubleshooting
How do I fix missing DLL errors for Lucius II?
After extracting Lucius II, 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 2.60 GB — 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, including Version 9.0. 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.