World War II G.I. is another unfortunate member of the Build Engine family

destructoid.com:

Let’s take a moment to show some appreciation for the publishers who have the guts to keep kusoge available for purchase. Ziggurat. Nightdive. Thank you for giving me a megaphone to cry for help. Hopefully, someone will hear my pleas.

I’ve been fighting a losing battle to try and get Extreme Paintbrawl working on a modern PC. That game has the reputation of being the absolute worst game ever built in Ken Silverman’s wonderful Build Engine. While the engine was home to games like Duke Nukem 3D, Shadow Warrior, and Blood, it also had a lot more questionable games. Last week, I covered 1998’s Nam. This week, we’re looking at another game by the same developer, World War II G.I.. Maybe next week, we’ll look at William Shatner’s TekWar if I can get it working. Let’s hope not!

Released in 1999 – one year after Nam – World War II G.I. is pretty easy to discern just based on the name on the tin. Once again, we’re taking Duke Nukem 3D’s Build Engine and transplanting it to another place. This time, it’s France during World War II rather than Vietnam.

At least with this setting, it’s one of the rare wars where intervention seemed necessary, unlike the Vietnam War. I still don’t really want to talk about it, though. That’s how exhausted I am from keeping up with the ongoing real-world wars. To sum up the backstory to World War II G.I., it’s 1944. The Axis still have control over most of Europe, and the Allies are launching a seaborne invasion of Normandy, France.

More importantly, the game was developed in 1999, a year after Saving Private Ryan hit theatres. It was a few months before Medal of Honor would start the avalanche of WW2 games that would become a hallmark of the era. The time was right, but there are plenty of reasons