Game Overview
Running a crooked casino is hard enough before the mob demands payment in planetary-scale debt. JOHN GLEEP turns that absurd setup into a frantic sci-fi roguelike where a desperate alien proprietor kidnaps gamblers from hostile worlds, stuffs them into his bouncing pachinko casino, and tries to keep both his business and personal life from collapsing. The tone is gleefully ridiculous, but the pressure is real: gangster dentist Joey Norp is waiting for his money, while John’s ex-wife, child, and increasingly strange acquaintances add complications between raids. It plays like a cartoon crime drama filtered through an arcade cabinet that has far too many buttons.
Each run splits attention between two simultaneous activities. On one screen, John pilots his UFO around a planet, scooping up citizens, collecting junk, dodging Captain Missile’s attacks, and dealing with hazards; on the other, abductees tumble through a peg-filled casino board that generates the profits needed to survive. Random crises such as bomb disposal, bugs, and unwanted virtual meetings force rapid decisions, while found Gadgets and Junk improve the ship or grant disruptive abilities. Fueling the Hyperdrive lets you leave for new star systems and better opportunities, but failure to clear the debt ends a run and sends John back to start with another randomized chance.
The clever draw is the collision of active UFO action and hands-off pachinko management: neither side can be safely ignored for long. More than 40 pegs allow for wildly different casino layouts, while over 100 gadgets create builds that can turn a clean abduction route into chaotic, profitable nonsense. Permanent upgrades, companion storylines, and side activities including Binko Racing, Human Poker, and visits with John’s family give repeat runs extra texture beyond chasing a high score. Fans of roguelike build-crafting and hectic multitasking games will get the most from it, especially anyone who enjoys the bizarre humor of games like Luck be a Landlord paired with arcade-style action.
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 JOHN GLEEP 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 64-bit
- Processor: Intel Core i5-8400 / AMD Ryzen 5 2600
- Memory: 8 GB RAM
- Graphics: NVIDIA GTX 1060 6GB / AMD Radeon RX 580 8GB
- DirectX: Version 11
- Storage: 2 GB available space
Setup Guide & Troubleshooting
How do I fix missing DLL errors for JOHN GLEEP (v1.0.2)?
After extracting JOHN GLEEP (v1.0.2), 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 538.54 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, including Version 11. 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.