Girls’ civilization

Table of Contents

Girls’ civilization is an open-world, real-time strategy game about a robot that is destined to fulfill a mission. . . problem being, she hasn’t a clue what that mission is!


(Adult) Content?

Not applicable.

Hours of Gameplay?
Twenty or thirty hours.

Modding Support?

Patch Available?
Not applicable.


Assemble and train troops and lay siege to your enemies. By destroying enemies, you’ll gain a variety of equipment and raw resources. Battles are fought in real time, much like an real time strategy game; you may route your army using an overhead view (or sit back, and enjoy the show!) Alternatively, you may fight side-by-side with your comrades. Soldiers cost money — not only do you need to train and replace your (wo)men, but you’ll have to insure that you’re earning enough to pay them every day. Thankfully, earning money and replacing bodies can both be automated when you conquer cities. However, taking (and keeping) a city is no easy task; when a city’s at stake, hundreds, if not thousands of lives are on the line!

As fun as Girls’ civilization is, it’s also grossly unrefined.

Most of the game isn’t well explained. Beyond a few meager tutorials (which can’t be revisited), you’re on your own. It’s easy to get RNG-screwed from the beginning the game, practically warranting a restart. Traveling between cities is extremely tedious, due to the fact you have to walk. Girls’ civilization should take a page from Skyrim, and implement “fast travel” between discovered locations. You can save at any time, and set the game to auto save before each battle. Considering how often this application crashes, you’re gonna need it. Only a handful of units are worth manufacturing. Once you’ve managed to produce an army of leveled-up cavalry, you’ll dominate the world — that is, until tanks enter the picture.

By advancing the “age” of civilization, you’re able to produce new and improved units.

However, doing so will put you at an enormous disadvantage; when you tech-up, so does everyone else. . . instantly. Considering the AI gets infinite resources, it’s in your best interest to never tech-up, and maintain cavalry as the strongest unit in the game. Advanced tech is expensive, and (in some cases) succumbs to friendly fire. If you mix melee and ranged troopers, you may end up hurting yourself more than the enemy. I suggest investing into the “Gunpowder” age, which introduces primitive cannons and firearms. I won’t lie — riding on horseback with flintlock pistols is awesome, and doing so with an army of over-powered cavalry is super awesome.

I’ll end this section with advice — if you find any “Aquilegias Stones”, save them for the story!


Iwinya has been remanufactured by Krosa, her own captain to fulfill a “top-priority” mission. They are “Ancients”, or military robots — they last saw the light of day seven hundred years ago, during the Anti AI War. When Krosa was remanufactured, she could only gather three words regarding the mission; all she knows are “destroy”, “hemisphere”, and “support forces”. Iwinya has no choice but to mingle with humans to unravel her mission. The world she knew was no more; apparently, all that’s left of the Anti AI War are scattered Ancients, which have been remanufactured across four nations. Iwinya and Krosa will have to make friends with the four nations, as they collect their mechanical comrades and discover why they have been called upon.


The titlescreen is an ugly mess. Though I enjoy interactive titles, the way the camera shifts (based on your cursor) doesn’t work; chances are, you’ll wind up with a fancy picture of the floor. The tutorial regarding the “error box” on the bottom-right of the screen not only looks atrocious (and wildly unprofessional), but it says something about the functionality of the game (and not a good something.) From “Options”, you may adjust audio, display, gameplay, graphical, and language preferences. The “Options” menu need to be streamlined, and more user-friendly for players that aren’t familiar with computer hardware. The English translation is terrible, and there’s lots of dialogue.

I hope your PC is packing power — this game will test your computer!

Girls’ civilization is a demanding game. The world map is quite large, and the landscape is populated with a number of NPCs. All NPCs are physics-enabled; their hair and clothes will flail as they run about. Battles (particularly sieges) can have upwards to a thousand NPCs (again, with physics). Having hundreds upon hundreds of characters fight each other with dynamic lighting, explosions, projectiles and jiggly attire is sure to work your PC to the bone. I played this game using an RTX 2060, and large scale battles seemed to crawl with single-digit frame rates. However, if you’re really careful, it’s definitely possible to avoid large scale conflicts (though you’ll miss out on tons of valuable loot).

In other words, check yourself before you wreck yourself.

The Goods

I wasn’t expecting any adult content, but I was pretty bummed out not to see any nakie-tiddies!


Wait for updates and a strong sale. Provided (A) this game is not crashing, and (B) you don’t get RNG screwed and (C) you actually know what to do, Girls’ civilization is actually a lot of fun. This game is a buggy mess, and it looks like an asset-flip fest — but, it has its merits. Say what you will about the stock waifus, but the visuals work (as long as you don’t “tech up”). It’s fun raising armies, and I loved watching bodies ragdoll as they were trampled (or exploded!) You’re free to do with the camera as you please, allowing you to really soak in each battle. Girls’ civilization is, to be frank, not great — but if you’re willing to look past its blemishes, I think you’d understand why I struggled to put the game down.

Wombat Woah! — “Rag ‘n ‘bag!” [Jan 12th 2021]

When you rapidly crouch/un-crouch over fallen bodies, they’ll totally spaz-out! Just make sure they’re dead first — don’t forget to double tap. . . heh.

Wombat Woe! — “Where my Siege at?” [Jan 12th 2021]

For reasons I could not pinpoint, sometimes my Siege Armies would disappear upon arriving to their destination. I sent an army from Chateaubriand to Portiere (under Juengal control) — they disappeared. I also sent an army from Gate Gigot to Pattatas and Stolen (under Imperial control) — they too, disappeared. It’s worth mentioning that at the time, Pattatas and Stolen had Siege Armies “replenishing” during my attacks. Until this issue is addressed, I suggest saving before “marching” a Siege Army, just in case the game screws you over.

Questions, requests or comments?