hexes

For anyone wondering why you cannot tile a sphere with hexes: this is a matter of Euler characteristic.

We tried to figure out how to cut a planet into hexes, turns out you can't (no surprise).

Makes for a nice variant where exploration holds surprises, or you can expand to hexes that are already known.

Incidentally, a torus has Euler characteristic 0, and indeed it turns out that you can tile torus with hexes.

You either use small hexes with almost no room for actual graphics, or large hexes that fill up too much of the screen to give an effective view of the battlefield.

If a gps track goes through this larger parent cell, the track will have hexes with the same prefix.

Algorithms like A* work directly on a list of neighboring hexes with no coordinate conversion required.

Each hex has 6 edges, but every edge is shared by two hexes, so there are 6N/2 = 3N edges.

Some apps are built with bootstrap, some with pure, some with no styling whatsoever, different hexes for our company's primary color...

Another way too look at it, is to say the hexes would be distorted wrt.

You'd build your own map out of the hexes, set the armies and conquer.

The ui freezes when it's loading in new hexes from the server.

I say this having had a couple of fun "hex-based strategy game hobby projects" over the years (sidenote -- trying to cover a sphere in hexes is actually a non-trivial matter).

I wasn't as clever as the people mentioned in the article, so I came up with a bog-standard "offset coordinates" system, with the flat-topped hexes and a rectangular map stolen from Military Madness.

The mouseover highlighting of code as you mouse over the hexes in the 'Neighbors' section remind me of Bret Victor's work[1] Also, I was amused to see that the author used a language called "Haxe"[2] which can generate (compiles into) javascript, flash, C++, java, C# etc.