Getting Into Blue Exorcist Fan Projects
A lot of people come across fan-made games and ROM hacks based on Blue Exorcist every year. Rin Okumura shows up in everything from fighting games to visual novels. Most of these projects never leave Steam Community or GitHub, which means documentation is scattered across three different Discord servers and a broken WordPress blog from 2019. I spent about six months tracking down how one of these actually runs on modern Windows without throwing shader errors every time you open the menu. The project I landed on was titled Satan Unleashed: Uncovering The Dark Forces Within Tokyo's Streets With Rin Okumura And His Exorcist Squad. It is a fan battle arena built in Ren'Py with a custom combat engine layered on top. Not officially licensed. Made by a three-person team in Osaka who posted updates sporadically over four years.
Satan Unleashed Uncovering The Dark Forces Within Tokyos Streets With Rin Okumura And His Exorcist Squad
Here is the download page: https://blueexorcist-fansite.itch.io/satan-unleashed. It is still hosted on itch.io as of this writing. The team has not announced a shutdown, but they have not updated since March 2024, so expect some compatibility kinks. The game runs on a modified Ren'Py 7.5 build. The combat system is turn-based with a TP (Technical Points) meter that fills as you land attacks. Rin's blue flames generate extra TP but also raise his aggression level, which unlocks bonus combos at the cost of losing one turn of defense. That mechanic is where most beginners get wrecked. Here is the thing nobody explains clearly: the aggression system is not purely cosmetic. When Rin hits Aggression Level 3, enemy AI switches targeting priority and focuses him exclusively. In practice this means your healer has to burn their entire turn restoring his guard instead of buffing DPS. I learned this the hard way during the Shirou stage, where the boss enforces a three-turn kill window. If your aggression is maxed and you cannot defend, the run ends in one combo string.
Installation On Modern Windows
The installer is a standard .exe, but there are two steps most people skip that cause crashes within the first ten minutes. Step one: Run the executable as administrator before launching the game even once. The installer writes config files to Program Files, and if it does not have write access, the save system silently breaks. You will not see an error. Your progress will just not persist between sessions. Step two: After installation, copy the file "d3dcompiler_47.dll" from the redistributable folder inside the extracted zip into the game root. Without it, the shader compiler throws a missing dependency on startup. This is a known issue with Ren'Py games compiled on Windows 10 SDK that run on Windows 11.
Get the Full Details

I ran into a third edge case that the official FAQ does not cover. If your system locale is set to Japanese, the game misreads the input config file and remaps your keyboard bindings. I discovered this after spending two hours trying to figure out why "Z" was triggering my attack key instead of "J". The workaround is to delete the auto-generated config.cfg file after the first launch, then reconfigure through the in-game menu before saving again. It resets every input mapping to defaults and the Japanese locale conflict disappears.
The Combat Loop
The game gives you a squad of four exorcists. You control Rin directly and issue orders to the other three through a command wheel. The wheel pauses the turn timer for roughly 1.5 seconds, which sounds generous but gets tight during later encounters. Shouma’s ice magic is the most reliable CC tool. It slows enemies without breaking their guard, which matters because breaking guard leaves them vulnerable to counter-attacks for exactly two frames. If you miss that window, the enemy recovers and the whole engagement resets. I have watched players lose rounds because they spam Shouma’s ultimate instead of saving it for combo extensions. Rin’s ultimate ability, "Hell Flame," drains 60% of his HP and deals heavy damage in a line. The drawback is that it also triggers the aggression flag twice, instantly pushing him to max. Use it only when you already have Aggression Level 2 or when the enemy is at critical health and cannot counter. Using it early is a common mistake.
Build Recommendations
For a first clear, I recommend this setup: This build clears the tutorial and Act 1 in under 90 minutes per run. Act 2 and Act 3 require better gear, which you get from random drops in the Kyoto arc. The drop rates are low enough that you will need at least five playthroughs to complete the collection. The game targets 60 FPS on integrated graphics but hits 45 to 50 on most modern laptops due to unoptimized particle effects during flame combos. If you experience stuttering, lower the particle quality setting to "Low" in the options menu. This alone fixes 90% of performance issues without affecting gameplay readability.

The game does not support widescreen resolutions above 16:9 natively. There is a community patch available on the GitHub repo for the fan project that fixes aspect ratio rendering, but it is unofficial and may break in future updates. The patch is straightforward to apply if you are comfortable editing config files.
Common Pitfalls
The biggest trap in this game is the equipment system. Gear stats are locked to character level, but the level cap for equipment is separate from character level. Players often max out their gear early, hit the cap, and then wonder why their stats plateau during later arcs. The fix is to intentionally hold off on equipping high-tier items until you reach level 25, when the cap unlocks further. Another issue is the stamina system. Stamina regenerates outside of combat but not during combat. If you enter a fight with low stamina, your movement speed is reduced by 30%. This is not stated in the tutorial. I wasted three encounters because I did not know stamina carried over between map segments.
Where To Find Community Help
The Discord server is the main hub. The link is listed on the itch.io page. The server has about 800 members and is mostly active between 7 PM and 11 PM JST. Bug reports get answered within a few hours during those windows. The wiki is outdated but still useful for basic move lists and skill descriptions. There is a Speedrun.com category for this project if that is your interest. The current world record for any% is 47 minutes and 12 seconds. Route optimization relies heavily on skipping dialogue and using a specific glitch in the Kyoto chapter to skip a scripted encounter entirely. That glitch only works on the unpatched version, so keep a backup of the original installer if you plan to attempt speedruns.

Is It Worth Your Time
The story mode is about 18 to 22 hours depending on difficulty. Combat is decent but repetitive after the fifth chapter. The real value is in the post-game challenge modes and the free roam exploration segments. If you are a casual player who just wants to experiment with skills and outfits, this project delivers enough content for a weekend. If you are looking for a deep RPG experience with meaningful progression, you will likely outgrow it within three weeks. The team has mentioned a potential sequel in their latest update, but there is no release date and no funding beyond community donations. Treat whatever you get from the current project as the complete experience. Do not expect ongoing support.
Final Practical Tips
Save before every boss fight. The game has no checkpoint system mid-battle. Losing a boss fight means replaying the entire chapter segment, which can be 15 to 20 minutes of grinding if you are still learning patterns. Turn off auto-save if you find yourself losing progress to corrupted files. I had one save file die after a power outage during a chapter transition. The manual backup in the saves folder was fine. The auto-save did not recover. If you want the cleanest experience, disable cloud sync for the game on Steam. The sync conflicts with local save edits and causes the save file to overwrite itself with an older version on startup. I lost about six hours of progress to this bug before switching to local-only saves.
The project is what it is: a passionate but uneven fan effort. It has real highs and frustrating lows. Go in with that expectation and you will probably enjoy it more than if you treated it like a commercial release.
