Looks great! I took a look at the build when it was producing an error and I was tired, and had no idea how to fix it. But now when I download the Windows build, I just download, decompress, and run. No need to unblock it. Not sure what the difference is. I'm on Windows 8.1, don't have UAC enabled, and have obviously run things named C7.exe before (but you probably have too?). I do occasionally get the "this application comes from an untrusted source on the Internet" notice when downloading other programs, but for whatever reason my computer seems to think you are trustworthy.
I'll fire up by Bionic Beaver and see how it runs there.
Beaver update:
Got it downloaded and extracted. It's great that Ubuntu had a good GUI program for decompressing now. Ran it. Got an error:
"Could not display C7.x86_64"
"There is no application installed for 'executable' files. Do you want to search for an application to open this file?"
I guessed that chmod +x would fix that, and sure enough it did. At that point, the splash screen would appear, but then it would disappear and crash. Running it from the console confirmed that the error was not being able to find the main menu mp3 file, which must mean I don't have Civ3 files copied over to this Beaver.
Which means two things:
1. It basically worked, we just have the chmod problem that I also had when running the Linux build on Windows. I wonder if this is as easy as adding the chmod step at the end, since GitHub Actions is probably running on Linux? Although GitHub is owned by Microsoft now, so maybe it's on Windows or a legacy Xenix box that they were looking to repurpose.
2. It might not be a bad thing that I have a VM without the Civ3 install files set up; that makes it a good test bed for avoiding crashes if files are missing. IIRC, I did set up a try/catch around the main menu background, but didn't think of that when adding the music.
Update: Pushed a small fix for the mp3 crash, verified by renaming my Civ3 folder on Windows.
Oh and (3) I couldn't download without being signed in. Tried on Firefox on Bionic Beaver, and verified on SeaMonkey on Windows. Took a look in the Settings, but didn't see anything obvious, although I did see that it keeps the builds for 90 days. Which is fine for automated builds, but if we plan to use GitHub Releases to host releases, we'll have to figure out how to yank a build for a release and make it stick around a bit longer.