Federation Commander

The idea for the nested-hex grid was to allow for actions to take place on a different time scale depending on which size of hex was being used at the time. Movement would be one large hex per month, or one week per medium hex, or two days per small hex. However, the grid gets very "busy" when I went down to the next level:



If you want less complicated, I tried two other grids, one with ten hexes across and one with seven:





The ten-hex version makes more sense if you want to keep things simple as each sub-hex is 50 parsecs vs. 71.4 parsecs on the seven-hex version.

I know this is a bit old, but I'm finding this very useful.

The first hex shown in the previous post above that has subhexes with subsubhexes, is a great pattern. With 13 subhexes and 6 half hexes, if you take three half hexes and consider those full subhexes as part of the larger hex, then you can use a linear base-16 addressing scheme that can address the infinite plane of hexes with a single number, no need for x+y coordinates of any sort. Each base-16 digit relates to a particular scale. Of course the center subhex should always be 0, but depending on how the other subhexes are measured, custom addition and multiplication tables can be used for advanced stuff, though isn't required for simple mapping and reference.

This also lets you have write ups in a binder for each hex or otherwise based on location and yet easy to know where everything maps to.

I'm glad to see at least one person out there found it useful.

Indeed. It's not as mathematically elegant as Spiral Honeycomb Mosaic, but the lack of spiraling and working in base 16 makes it easier to deal with conceptually and on the computer. I can convert coordinates so much easier without that spiral.

In fact, in one of my fictional universes they actually use hexes for mapping and referencing areas, especially militarily.