Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

faxeneda rated Abdomen Expansion

faxeneda rated a game 4 days ago
A browser game made in HTML5.

Because of the fact that the version here is outdated, this review is based on my experience with the Steam version of the game.

Anyways, I'm not really into inflation or clicker games and I'll be honest, this game is pretty rough but I'll give it a bit of a pass for having some tentacle hentai and the art style is good. The main problem I have with this game is just that there's no real balance to the game. I'm okay with the later "scenarios" (the game doesn't have a name for them so that's what I'm calling them) taking longer to complete but, even with an auto clicker, they take way too long to complete and nothing happens throughout most of that time.

I know that there is the reset mechanic for getting passive bonuses but they're not permanent, meaning that you have to regain them every time you start a new scenario. I also didn't know how many of them would be optimal and I always felt like I had way too little of them even though I felt like I spend way too long getting them. Because of this, I didn't actually finish the game and I just decided to play until I got all the achievements.

The last thing I want to mention, is that I was able to play the game on both Linux and android. The game worked fine in the version of Proton Steam defaulted to for Linux but android gave me some problems. I normally use Winlator for running PC games in android but I've never used Steam in Winlator, so I tried GameNative instead because it has built-in Steam support.

GameNative, despite being based on Winlator, almost never works even for games that work perfectly fine in Winlator. Luckily, I was able to get this game working in GameNative but I had to use different settings from what the "use known config" set the container to and the game had to be ran manually from within the container itself. While I know that my settings might not work for everyone, I set container variant glibc and graphics driver to VirGL, then I was able to launch it manually from the A: drive inside the container.