The Wintel Retro Landscape

I started this project before the massive boom in Claude-enabled decomps started rushing the scene, so this may now be mostly of historical rather than practical interest. I planned on comparing more applications but see little point now; I’m publishing more or less as it was last time I touched it. It should also be noted that when I wrote this, the Pi 5 was a lot more affordable!

Windows On Intel dominated the late PC era, and there’s a wealth of software available for the platform, especially from the 90s and 2000s, right in the sweet spot when desktop games had matured but not bet become totally entangled in Steam and DRM. Microsoft has done an impressive job keeping legacy applications running on the platform. It’s a platform I hoped you could keep stable indefinitely, even if WINE was required.

However, Wintel and desktop in general have been slowly falling out of favor. Apple, ever the trend setter, has switched away from Intel for its desktop machines. Microsoft has been shipping ARM tablets for a while. The Raspberry Pi is the common denominator hobbyist platform. People are hopping mad about Windows 11. And overall, computing has switched from something you do on a desktop with a keyboard and mouse running an Intel processor to being something you do with a mobile device with an ARM processor.

What do we do when platforms are retired and try to make us give up our software? We persist!

Meet the Test Applications:

I’ve tried to assemble a grab bag of applications you should be able to find if you look hard enough but nonetheless are personally nostalgic.

EV Nova (Windows Port) (2003)

The definitive 2D space trader. One of my favorite games and one of those “I want to be able to play this forever” emulation targets. Previous attempts to run in WINE have been difficult due to font weirdness, but with the advent of the CE binary patch have gotten within reach.

Space Invaders (Windows, 1999)

2.5d Shmup based on the ur-shmup. If you speed run it, it plays like a puzzle game.

Lego Loco (1998)

2d sandbox/toy. Charming pixel art graphics. Like a Lego Sim City but without any Sim elements; the only real ‘game’ is to hunt for all of the whimsical easter eggs they programmed in, including some that only appear on certain dates (for example, on Halloween all characters spawn as skeletons.)

Star Craft: Broodwar (1998)

The classic sprite RTS and once the most popular esport.

Command & Conquer Tiberian Sun

https://cnc-comm.com/tiberian-sun/downloads/the-game/installer

An eclectic mix of technologies and killer atmosphere create a memorable RTS experience.

Test Environments:

Raspberry Pi 4/5: Wine + Box64

PI 5 only: change kernel page size:

The PI 5 has a larger kernel page size than legacy programs expect. You need to downgrade your kernel to make it work. This is only a problem on the PI5. Be pretty cool if this could be emulated too though.

https://github.com/ptitSeb/box86/issues/993

Edit your config.txt:

sudo vi /boot/firmware/config.txt

(or sudo nano if you don’t like vi)

add the following to that file:

kernel=kernel8.img

Reboot.

Compile Box64

https://github.com/ptitSeb/box64/blob/main/docs/COMPILE.md

git clone https://github.com/ptitSeb/box64
cd box64
mkdir build; cd build; cmake .. -D ARM_DYNAREC=ON -D CMAKE_BUILD_TYPE=RelWithDebInfo -D BOX32=ON -D BOX32_BINFMT=ON -D RPI4ARM64=1 #Change the last line according to your PI version
# This takes a while
make -j4
sudo make install
sudo systemctl restart systemd-binfmt

Install bundle libraries

https://github.com/ptitSeb/box64/blob/main/docs/BUNDLE-X86-LIBS.md

sudo apt-get install binutils coreutils curl rpm2cpio tar zstd

/box64-bundle-x86-libs.sh

Install x86 WINE

download wine here: https://github.com/Kron4ek/Wine-Builds/releases (wow64)

Run the program

bin/wine <program.exe>

Remarks

This setup isn’t too bad, but it required some knowledge of Linux, googling, and assembling multiple parts. Nothing I expect the average Raspberry Pi user to be intimidated by, not not something I can recommend to the general public in the way you can with Steam.

For CD ROM games

You’ll need to mount the ISO of the CD ROM:

“`mkdir ~/cdrom0

sudo mount -o loop -t iso9660 <my_iso>.ISO ~/cdrom0

EV Nova

PI 4: Runs albeit at a framerate slightly below the original OS9 play speed (and well below the default Windows play speed.) ~25 FPS.

PI 5: Acceptable performance. Fonts still slightly jank.

Space Invaders

PI 4: Runs stable, with some graphical glitches. You need to install it from the CD then run from Wine’s C drive (easy to find with winefile.) Couldn’t figure out how to make the window bigger.

Tiberian Sun

PI 5: Runs great. Initial startup was wonky and need multiple tries. Make sure you change the screen resolution asap because any space outside the resolution gets an awful flashing pattern (Photosensitive warning!)

Android: Winlator

Winlator is distributed as an APK here: https://github.com/brunodev85/winlator/releases/

Installing APKs on android requires clicking through several security warnings because it’s opening up your device to possible compromise in a way that most activity on an Android device does not. But, if you’re pretty sure you know what you’re doing, Winlator packages WINE, Box86/64, and several other tools together into an android app that lets you run some wintel programs on an android ARM device.

For best results you’re going to want an external Bluetooth keyboard and at least a stylus.

EV Nova

Can’t keep a consistent frame rate. Some text missing. Semi-Playable, but only if you’re a diehard fan.

C&C: Tiberian Sun

Way too slow to be playable. Radar didn’t work. Froze on campaign start, but was able to start a skirmish. LMB controls meant you could still sort of play slowly.

CD Games

Winlator is unable to run games that require a CD in the tray to run because it lacks CD emulation.

Remark

It’s simply not ready. Maybe never will be.

Linux on x86 (Virtual Box)

I consider WINE on Lin86 a mature enough technology that I don’t feel the need to discuss it here, instead I wanted to compare it to Virtual Box.

I used Lubuntu on an old ThinkCentre. Similar instructions are out there for other Linux distros. There are some well known Windows XP installs you can use. Make sure you enable virtualization in your BIOS.

https://www.virtualbox.org/wiki/Linux_Downloads

sudo apt install gcc make perl
sudo /sbin/vboxconfig

sudo rmmod kvm_intel

# You may need to configure these to run at startup
sudo modprobe -r kvm
sudo modprobe -r kvm_intel

But there are issues:

https://forums.virtualbox.org/viewtopic.php?t=106674

After 6.x, Virtual box dropped support for 3d acceleration in WinXP guests.

Installing 6.x on Ubuntu 24.x turned out to be difficult as well, but your mileage may vary.

CD support is very nice; you just load each CD as a virtual dive. I’ve found this the most straightforward way to run non-game applications if you need them.

CnC Remastered (2020)

I forgot to post this review at the time. Oops. Posting it now to get it out of my drafts bin.

You can play either Red Alert or Tiberian Dawn multiplayer in CnC Remastered and one of the most interesting parts is just how much better Red Alert’s multiplayer is. The most obvious difference is that the maps are much larger, so you’re not micro-managing your base layout to avoid running out of room or blocking your harvesters. The Harvester AI also benefits from more room to move around. Gems mixed in gold fields add an extra micro element for people who want to mine more efficiently. And boy are those harvesters dumb. One of Starcraft’s best innovations was the hack of just letting harvesters ignore collisions.

Silly harvesters aside, it’s shocking how well Red Alert holds up, especially to a group of players now seasoned by 8 Bit Armies, Red Alert 2, Grey Goo, and Starcraft II. It helps that with huge screen resolutions available now, you can have just absurd numbers of units on screen without lag. You can blanket the map in tanks. The grittyness of Westwood’s RTS is on full display; a good tank micro will turn a column of infantry into a large puddle. Infantry will go to ground when fired upon. Moving units appear to be able to dodge some shots. Tesla coils appear to have glorious procedural lightning. While you can probably win with math (like any RTS) it at least feels like there’s an element of micro and an element of chance in there. Luck combines well with Light tanks, as it happens.

The music though, what about the music? As someone who’s been listening to the CnC and RA tracks since the mid 00s I can say confidently that the music is absolutely amazing. The cover versions, the remastered versions, they’re both awesome. I have this vivid memory of sharing music back in ’10 or ’11 and showing someone Bigfoot. The bitcrushed quality didn’t bother me, but others couldn’t see past it. That problem is a thing of the past. I forsee blasting these versions for far longer than I will be playing the game. Klepacki has done it again.

DnD Papercraft Buildings (2004)

Someone was asking for papercraft RPG/tabletop terrain, and I of course flashed back to a publication called the “Map Folio 3D” from the DnD 3.5 era. Papercraft DnD-scaled buildings on cardstock. I’ve unfortunately long since ditched the structures, but Wizards uploaded them as PDFs back in ’04 (and why shouldn’t they have; they were selling books after all, not papercraft hobby supplies.)

I was able to dredge a few out of the archive before it started going down (again, apparently) today (see edit below), and I’ll present them here. You may have better luck, I’ll update this if the archive ever comes back up (and, more than likely, move the whole collection there or to some other more appropriate hosting.)

Seeing them again is quite nostalgic. They have the same hard to describe texture feel that other DnD 3/3.5 era maps had. Early digital photorealistic illustration… core?

Edit: The Wayback Machine was running again, I got the rest

(no PDF was in the archive for this one, so it’s presented as two JPEGs.)

SnapShips and ZBuilders

A long time ago, I got my hands on Zoids Z Builders (aka Blox) and thought they were pretty cool, but didn’t really chase it further. As I sometimes do, I wondered if there was a modern equivalent, so I looked for ‘scifi robot cube building toys’ and found SnapShips. Over a decade after the debut of Z builders, it’s worth comparing these cube-and-greeble 1/72 scifi building toys of past and present.

Z Builders

Sprues!

The first thing you notice about the Zoids model is just how much of a capital ‘M’ Model Kit it is. Previous Zoids figures where less toy like-they where a little more like something you’d see from Tamaya or Airfix, though they contained motorized play elements. Z builders adds freely moving joints/possibility and a building system instead of a windup mechanism, but you are still looking at sprues when you first open the box, and decals when you finish the build. Like some Gunpla kits, the sprues are made of different colored plastic so no paint is required for a half decent paintjob.

Feel human, use tools

One interesting similarity between ZBuilders and SnapShips is that they both include a small tool for disassembly. SnapShips include a spudger, and Zoids ships with an ‘extractor tool.’

Zoids ‘blox’ elements are 14.7mm, and no rounder in inches.

The stickers are a pain. There is no guide so you have to sort of look at the box and figure out where they go, (again) more like a traditional scale model. They are in a grid and the squares are much larger than the places you need to put them, so you have to cut them to size. After all that, they don’t go on super clear. Wet transfer decals would have been better if they’re not going to die cut them anyway. They do add a nice sense of scale though.

The model is somewhat poseable. It won’t really hold a pose that involves much weight because the rubber joints are rather weak. It’s possible that the decades since it was manufactured have taken a toll on the rubber. Still, robotic dinosaur: very cool. Timeless even.

Wonder how it’s supposed to reload that arm gun without opposable thumbs? Perhaps its teeth…

SnapShips

SnapShips cube elements are 20mm

The SnapShips have much more detailed, Lego style instructions but they aren’t really as needed if you want to build it like a puzzle. The blocks lock together so that rather than flexing, they hold a specific shape. The parts are all in bags – no sprues which is honestly kinda chaotic.

The SnapShips contain three alt-builds each, similar to what Lego does with its Creator theme. I built the forward-swept wing design rather than the front-of-box design.

SnapShips give you tons of rectangular greeble panels, but a cube is relatively large compared to the scale so all of the vehicles you make will turn out very blocky. There are relatively few specialized pieces besides the aforementioned panels. Between sets there’s a strong compatibility at least – there’s only two color schemes. You get prints instead of stickers too. I think the appeal may be limited for SnapShips though. Trying to make something sleek out of something so boxy is going to be a challenge with the part set available, and the boxes are so big compared to the features people will want to capture is going to make that rectilinear form stand out.

Something else to consider about SnapShips is that it’s got a full blown tabletop war game of all things associated with it. Apparently it’s quite similar to X Wing. 1/72 is sort of a huge scale for dogfighting, but some reviewers seem to love it.

Glue Guide

So here is a strange question. I underestimated just how sharp exacto knives are while cleaning up the seams on my minis. Can i just use the plastic glue to seal it rather then keep changing bandaids each time it comes back open and bleeds again?

u/themonkeyone, who I assume isn’t a plastic model

When I saw this, I realized I really did need to write this up. I cannot allow the public to remain uninformed any longer regarding glue!

Plastic Cement

Also known as: Plastic Glue

This stuff smells like nail polish remover, and it’s no coincidence: they both use Acetone. The Acetone in plastic glue liquefies the plastic surfaces and when they re-harden, they’re very well stuck together. Cement is right; this stuff creates very strong bonds. The drawback is that it’s only good for specific plastics; the sort of polystyrene that you see in typical model kits, but it won’t work if you’re attaching a rock to a base or working with resin parts. It also won’t bind up your skin (otherwise nail polish remover would be far more dangerous. If you take nothing else from this article, take this:

You cannot close wounds with plastic cement!

If something is stuck on with plastic cement, your best bet for cutting it off.

SuperGlue

Now, I’m not a doctor, but I’m assured you can close a wound with superglue. It certainly sticks robustly to skin. Cyanoacrylate, the technical term for this type of glue will readily bond skin, so avoid using it without gloves. If you do, I recommend GoJo. CA glue will work with a variety of materials and form very strong bonds, but it has a few drawbacks: it’s finicky about setting. You get a few seconds to hold your bond steady (pressure is good) and then the glue is no good, you’ll need to try again after removing the now-spent glue. If you glue painted parts you need to make sure you don’t get glue anywhere visible, because it dries opaque. Its quick setting can be an asset though; you can pull off poses that would be slightly trickier for a longer setting glue. I hear you can freeze it off, but I haven’t had success with this myself.

PVA Glue

PVA glue, also known as School Glue, is also used in wood glues. It’s the least consequential of glues; you’re not going to poison yourself with it (unless, I imagine, you drink it) and if it sticks to your fingers you can can just wash it off, or rub your fingers together for a few seconds. It’s popular for basing because it’s thick, goopy, and easy to fix if you make a mistake; just add sand! You can even get it premixed with sand in the form of nice basing paste. It can be dissolved by soaking in water for a day or so and then scraping off with a toothpick.

(Re) Introducing Galactic Night

My vow to stop making EV-likes has had mixed results. Here, I’ll discuss some of the more interesting aspects of a recent EV-Like, Galactic Night.

Perspective on perspectives

While I did make a serious run at doing a vehicle game in Godot, it was hard to get around just how excellent the affordances of what I’d already built were, and what was lacking in Godot 3. But it didn’t start there. It started with an observation:

First Let’s Play google gives you for “EV Nova.” I haven’t listened to the whole thing, so I can’t vouch for it. But it’s got footage of the game.

Ships in EV Nova (and MPEVMVP, for that matter) are sprites rendered from 3d models. They are rendered with perspective so that when the front of a ship faces the screen, it appears larger than the back. It’s subtle on some ships, obvious on others.

Perspective camera isn’t the norm for sprite games. Most games with pre-rendered sprites use an isometric camera; here’s Starcraft as an example:

First result for broodwar gameplay. The Terran Siege Tanks are the best example of isometry.

For games where the units are in a rich world with lots of points of reference, rendering them in perspective might look wonky. Too much perspective might look wonky under any circumstances! However, the decision to use perspective in the sparse world of Nova lends the ships a sense of scale.

2.5d games that use a full 3d world instead of sprites tend to either use a perspective or isometric camera. It’s easy to implement either in Godot (and other engines) by changing the camera’s mode. But I was curious: could I implement something with a vertex shader that would deform a mesh such that it appeared to have perspective, even while rendered in an isometric view? Perspective, I should note, not truly relative to the camera, but relative to an imaginary camera ‘rendering’ the imaginary ‘sprite’?

This is difficult to convey with words, so I built a demo:

What’s interesting about this, at least to me, is how difficult it is to notice what’s going on. Your brain seems to happily accept the very unnatural perspective. At least mine does. But if you look closely, you can see that no matter where the spaceship (and thus actual iso camera) move, the spinning cubes maintain their fixed perspective, just like sprites in an old school video game.

Flying around was fun, I wanted to do more stuff. It got out of hand. It’s a whole game now.

More Ship Shader Fun

Using a 3d pipeline offered the possibility of using some nice 3d features, exploiting the fact that the textures and effects were in-engine rather than an external pipeline. Nova has engine glows and weapon glows; I implemented those too.

Nova also has an (unused) feature where you can stain your ship a different color. I wanted to try something similar, but nicer:

You can check out the full ship shader here. Note that in GD4 you can split shaders into multiple files, so the important parts are the perspective transform here, and the color swap logic here.

Union Bytes Painter allows for multiple texture layers, so it’s easy-ish to make separate textures for lights, engines, weapons, paint, and a base. It’s a little clunky for exporting though – I need to show/hide layers and export a few times. Still miles better than the Blender workflow I used while working on Flythrough.Space.

Flat Space

I wanted to create a nice set of planets and nail the EV Nova look, so I followed tradition and picked up the venerable LunarCell, which was also used to render the planets for EV Nova. This creates (gorgeous) 2d planet sprites:

Only problem? Lunar Cell doesn’t create masks, just planets on a black background. Solution? This remarkably simple shader:

https://github.com/EamonnMR/galactic-night/blob/main/entities/spobs/Spob.gdshader

You’ll notice though that that’s a 2d shader, and the game is 3d. That’s the neat part – the background is a 2d canvas! We use this class to make sure the sprite in 2d space tracks the correct position in 2.5d space:

https://github.com/EamonnMR/galactic-night/blob/main/component/FollowerSprite.gd

The background itself is basically the same shader I used in Survive Space but with additional special effects you can cue up to make hyperspace more exciting:

I wanted to visually represent folding space, and the looped background made for a unique opportunity to do it. The shader is of course just dropping specific images (Screaming Brain’s awesome Nebula backgrounds) on a couple of layers, but it would look better looped if I did something with Perlin noise.

Procedural Generation

Flythrough.Space used a handmade universe I originally drew on graph paper. While charming, that took a whole lot of work for very little gain at the end of the day. For MPEVMVP I used universe maps generated by Mag Steel Glass’s spreadsheet. Which is fine by all accounts, but I wanted the player to be able to generate new universes on the fly. That’s where I ran into my new best friend: Delauny Triangulation.

Compare:

(source: https://preterhuman.net/software/escape-velocity-macintosh/)

(wikipedia)

Ok, you need to look a bit closely, but in both cases, you’ve got a point cloud that is stitched up by non-overlapping lines. So to generate an EV map, because there’s a library function for that all you need to do is feed it a set of points and get your EV map’s hyperlanes!

https://github.com/EamonnMR/SurviveSpace/blob/main/procgen/Procgen.gd#L87

That same strategy carried over to Galactic Night, with some modifications, namely the division of space into quadrants to provide a difficulty curve, and the separation of growing biomes from growing faction influence. In Valheim, the game I imitated most on Survive Space, all three are effectively the same; a biome is a difficulty level is a spawn location for various monsters. In Galactic Night, spawns can depend on biome (for asteroid types) faction (for where to spawn enemies or allies) and quadrant (more difficult NPCs.)

Codex

The codex window loads up a folder tree of bbcode (weirdly, Godot’s rich text boxes support this) files and displays them. Item fluff that would usually be embedded in the interface in an EV goes here, a much more conventional placement for a modern game. I never did get around to writing a system for unlocking entries.

Retrospective

I’m proud of the technology and writing that went into Galactic Night, and some of it will certainly be recycled for future projects. I’d be happy if people get any use out of the code or design concepts tested out. I’ll close out with some final thoughts on how the project went.

I think the perspective looked really good, but some people definitely found it jarring. In future projects, it should definitely be an optional feature.

Doing the textures in Union Bytes painter became a slog. Small UI issues compounded over the course of several objects, and it stopped being fun.

Upgrading from GD3 to GD4 mid project was a big hiccup, but ultimately worth it because the syntax of GDscript is far nicer.

Though the procedural universe was really fun to tweak and play with, I don’t think it provided enough stuff for an exploration focused game. Games like Minecraft and Valheim exploit the inherent human desire to play around in a virtual space, and an EV map doesn’t really provide that; in a game like this the contours of the explored world are unique spaceships you find, well written place descriptions, missions, graphics, and the like. I never found a way to work in that level of diversity. Also, I never found an effective way to hint to players that, for example, getting lostech will allow them to increase their tech level and make more options available. Sure, it’s there in the manual, but who’s gonna read that! The upshot was that it felt like a big empty map with nothing particularly interesting going on in it, and no motivation to strike out and try to do stuff. Oh well.

Lead Testing wargaming minis

First, an apology. If I’d known I was going to write this up, I would have taken pictures of the minis and the lead test results. Lacking that, you’ll just have to trust that I read the test strips correctly. I encourage anyone to test any minis they’re concerned about, and don’t file or sand metal minis around kids.

Random weird knock off space marines of questionable origin: Lead

I tossed them, but they weren’t anything I’ve seen before or since. They resembled space marines but had vertical slats for face plates and resembled robots. May have been garage minis. Really kicking myself for not taking a picture.

Microworld Games: no lead

Agents Of Gaming: No lead

Brigade Models Starmada ships: No Lead

Scotia Grendel: Positive

Privateer Press (warmahordes): Positive (this is surprising because they’re a pretty big outfit.)

Old Questionable Fasa hex walkers: Positive

Cloud Nine’s Heavy Gear mechs: clean

Fading Suns A Call to Arms: Clean

I have a bunch of IWM things, so I tested a few

the Forestry mech labeled ‘Lead free pewter’ was indeed lead free

The Long Tom seemed clean, maybe the slightest positive?

But another seemingly new tank (probably a Shrek PPC carrier) had one of the strongest positive results I saw.

Lab Notes

I accidentally flicked a bit of vinegar/reagent mix into me eye. Owch. Washed it out pretty exhaustively… I hope.

Road Not Taken: Godot’s VehicleBody in Hovertank22

It’s no secret that I’ve been captivated by trying to make vehicle driving feel good for as long as I’ve been programming. Initially Hovertank 22 (formerly OWTD) used Kinematic movement as described here. But it wasn’t quite right. I have a strong memory of how much more fun World Of Tanks was after they introduced proper physics. I decided that if a third person perspective (as oppose to top down) was going to be used, I should probably use some sort of physics.

In Godot you have at least two options: the ‘easy’ one, using VehicleBody and the hard one, using a bunch of 6DOF joints. I elected to use the former, in this barn-burner of a PR. And it… well it sort of works, I guess.

As you can see, though wonky, the Tilter is able to navigate the terrain. It’s using a single visible steering wheel in front and the tracks are represented by two invisible wheels in the back. This movement model is, of course, built for car driving games, so the trike configuration cuts into the stability badly. The requirements of “Eamonn’s Ideal Vehicle Game” and thus Hovertank 22, however, call for tanks. Unfortunately, this has major disagreements with the movement model.

The basic idea, I figured, for implementing tank movement has been to treat each track as a series of wheels. To turn right, you drive the wheels on the left side and brake or reverse the wheels on the right side. In a real tracked vehicle, this causes it to turn. In Godot’s model, however, wheel slip seems to be very all-or-nothing: the vehicle stays in motion nicely but as soon as you cut the wheel and one track slips, the whole vehicle starts to drift uncontrollably. While some amount of drifting was desired, this turns out to be unplayable. And, worse, messing with wheel slip values didn’t really help.

Editor screenshot showing how the Cobra’s wheels are configured

Another problem with this movement style was that when the vehicle was in motion, differential steering worked far more effectively than from a dead stop (I assume that this has something to do with how overcoming friction is coded.) In order to turn from a stop you need to overcome the friction of all of the wheels, so turning while stopped was impractically slow. I implemented a fix which increased power when you weren’t moving but it was unsatisfactory and resulted in a vehicle that jerked around suddenly and violently.

I suspect that customizing the 6dof version might be able to overcome these limitations, but I don’t have the bandwidth to try it. Similarly, it might be very possible to implement this sort of thing as a custom integrator and bunch of rays, but again, that was more of a lift than I had time for.

Faced with basically a negative result from this experiment, I’ve decided that I’m going to roll back (ha) from the VehicleBody approach. I may switch back to a top-down perspective, and also may try switching out heighmapped terrain for tile terrain.

So what did I learn from this little excursion? You really need to validate your assumptions about how something is going to behave before you stake a project on it. I’m glad I didn’t fully do that (I still have a path forward for Hovertank ’22), though pulling it out is definitely going to be a setback.

Name Collisions in EV Nova

EV Nova was a formative game for me. One thing I noticed about it, and wanted to document, was that there are a lot of what I’ll call name collisions: names that are almost the same but refer to different things. Did I miss any? Leave a comment, I’ll add it.

Temmin Shard / Shard (faction)

LPAD station, where Temmin Shard takes you

Temmin Shard is a character in a side quest. However, “Shard” is also used to describe a faction formed when you win the Fed campaign and everyone else comes after you.

Krane / Kane (incl. Port Kane, Kania, and the Kane band)

Port Kane
Earth, with Kane band, but also a place where you might encounter Krane

Omata Kane invented galaxy-spanning hypergates and a bunch of things are named Kane in her honor, including earth’s artificial ring, the Kane Band. There’s also a Port Kane in the Kania system. Krane is the sociopath leader of the secret fed faction that you work for in some campaigns. Very different people.

Glimmer / Gli-Tech / Gli-Tech-Nia

Home of the GLi-Tech corporation (formerly known as GLiMMER until the discovery of the Glimmer system)…

Both are companies that make missiles. Huh? Gli Tech also owns an entire planet, called Gli-Tech-Nia. But wait, Glimmer is also the name of a star system. Surely this piece of fluff for Gli-Tech-Nia clears it up:

Associated Guild Of Free Traders / Free Traders

Pirate carrier used by both

Two opposing pirate factions that fly the same ships. One is hostile by default, the other isn’t. No idea which one though; and feds don’t care which one you blow up either. According to Word Of Atmos this is intentional.

Polaris / Polaron Cannon / Polaron Torpedo

Polaris are one of the game’s major factions. Polaron refers to a Federation weapon. But the weapon is pink… the color of Polaris technology. And the Polaris have a Polaron Torpedo which is pink but apparently unrelated. Maybe Polaron refers to some specific scifi gubbin, but then that’s still colliding with the Polaris.

Vella / Vell-os

Vell-os are a race of psychic transhumans and mostly extinct, Vella are a neighboring Arouran subfaction.

Wraiths / Wraith Cannon / Wrathii

A wraith
Wrathii fired from a Wraith cannon (no relation)

Wraiths are a race of sentient space-monsters, Wrathii are pink projectiles that the Polaris fire out of a Wraith Cannon. Also the Wraiths are right next to the Polaris.

TOWCB / TCTLIDS

The Ones Who Came Before are your standard ancient race of aliens trope, TCTLIDS are The Creature That Lives In Deep Space harvested for drugs, an abandoned plot hook that somehow remained in the timeline preamble.

Making a Hovertank level: Godot map editing

(Updated to reflect that this has been released! https://github.com/EamonnMR/hovertank-22/)

Hovertank is an honest attempt to bet big open 3d environments with AI agents running around working in Godot, using HTerrain and Godot Detour. I hope this is helpful for anyone who wants to make something similar in the future.

See also: https://hterrain-plugin.readthedocs.io/en/latest/

Set up terrain nodes

Create a new inherited scene from the “world” scene.

Add an HTerrain element to your level. Make sure it’s collision layers are 1 and 8.

Create a data directory in the levels folder

Apply a tileset to your HTerrain by dragging tileset.tres into the texture set slot, or making a new one from scratch.

Edit the terrain to your heart’s content using the generator and the tools.

Bake navmesh

You’ll need to repeat the next steps each time you edit the terrain mesh

From the “Terrain” menu up top, select “Generate mesh (heavy)” and select an LOD of 4. At least that’s what I’ve been using.

It will create a node called “HTerrain_fullmesh.” This is the node that the pathfinding library uses to actually determine where AIs can go. Hide this mesh; if you need to see the navmesh turn on “visible collision shapes” and you’ll see it (and it may lag real bad!)

Note that the flattened areas have nice clean navigation, but the more sloped areas don’t. You can use the flatten tool to cut paths across the map. Make sure you enable “pick” on it, it’s much nicer that way.

Place Entities

The prefabs folder has enemies with preconfigured weapons you can just drop right into the scene. You’ll want to drag them a bit closer to the ground though.

You can also place buildings this way. Careful not to accidentally parent stuff to random entities you’ve already placed – entities in Hovertank expect to be parented to the world.

You can set up objectives by adding the “ObjectiveMarker” component to an entity.

When all of the entities with objective markers are destroyed, the player has won the level. You can add the objective marker to any enemy or building.

The incursion spawner will spawn the entity you provide in “spawn” whenever there’s an incursion with the selected severity. Put one of the monsters in there by dragging its tscn file in to the spawn field (only monster at time of writing is our friend Kochab) (Incursions were removed, but you can see how it worked in older commits — Ed)

Add your level to the list

Add an entry to the big literal with all of the levels pointing to your level’s TSCN file, give it a name and a description, and it should show up in the dropdown in the main menu.