Monday, October 08, 2012

Savage Odyssey Prime: A Coordinate System Update...

Good Afternoon, All:

It turns out that I was wrong. The core rulebook does define a Coordinate System for dimensional addresses on pg. 117. In essence, the technicians divide space and dimensional planes into imaginary trays, and then divide the trays into little boxes. Each box is designated a code for location reference. To provide a reference point, our Earth is called 0-0-0-0. The first digit represents the dimension (or quantum level, from my previous attempt to fake something). The second, third and fourth components represent the X, Y and Z components of a three-dimensional notation. The orientation of this "map" is based on a navigation beacon formed from what is believed to be a subspace communication system found in the original Sherman Ring.

With that in mind, the worlds I've mentioned previously need new coordinates, of course. Here's the basic list, re-imagined:
al-Ard (3-19-(-18)-3)
Avalon (1-(-3)-15-8)
Darwin ((-4)-(-11)-(-4)-13)
Earth (0-0-0-0)
Laurium ((-5)-(-3)-13-9)
Leninmir, lka Earth ((-3)-(-9)-17-(-13))
Morlock (9-(-7)-8-(-16))
Naacali (12-11-0-12)
Plagueworld ((-4)-16-8-15)
Rancor (8-(-11)-(-16)-(-9))
Ryuchijyo (10-3-(-5)-15)
Shaggai (5-(-11)-(-9)-17)
Thoth, lka Geb ((-3)-(-13)-(-19)-12)
Verne, lka Earth (0-18-13-12)

Part of the motivation in changing the values above is to make it easier for me to map to a two-dimensional representation of the gate map I'm creating, what the core rulebook refers to as a Guide Marker. The final map should be simple but sufficient for my gaming purposes.

More Later,


SAROE said...

If you represent the negative numbers with the alphabet, it will make coding seem easier.

-1 = A
-2 = B etc.

So intstead of ((-4)-(-11)-(-4)-13) Darwin would be DKDM. or Delta-Kilo-Delta-Mike.
[Although you might want to change some of the NATO alphabet to stuff more sci-fi-ey. So 'M' could be Mars, Molybdenum, Megatron...]

Flynn said...

The only problem with that is you are limited to 26 negative places, and I'm using at least 40 for mapping purposes.

The real solution is to separate values with commas instead of dashes, but I've kept the dashes for the sake of consistency with the core rulebook.

It it really starts getting to me, though, I'll change it.

More Later,