High Hexadecimal...

[GoblynByte]

I've come across some (very) rare formulas in random world generation where the tech level is 16 or greater. I have no real issue with this existing, but how does one notate this for the UWP?

My understanding of Hexadecimal is amateur at best. But after "F" it reverts to numbers starting at 10, right? Being the tech level, this appears after the hyphen in the UWP. So confusing a two digit number with the other single digit numbers won't really be an issue, but it just looks... funny.

I guess what I'm asking is: how do you guys handle numbers higher than 15 in hexadecimal for things like the UPP and UWP? Do you just use 10+ or just throw convention to the wind and continue the alphabet from G?

By the way, I know this is a completely fiddly and useless fuss over a miniscule detail that will never affect anyone's enjoyment of the game. I'm simply asking out of idle curiosity.

 

[aramis]

You're correct that true hexidecimal goes 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F, 10, 11, 12, ... 1E, 1F, 20...

Travellerecimal is 0...9, A...H, J...N, P...Z

For UWP's and UPP's, f=15, H=17, J=18, N=22, P=23 etc to Z=33.

World Sizes don't linearly increase after F=15 (as at that size, the mass should be sufficient to generate a subjovian).

Likewise, a number of specific failure to match cases exist.

Computers 0=none, 1-9 = models 1-9, A-J = 1fib to 9fib, R-S are 1bis/2bis, but could be R-Z if one applies HG-79 logic to HG-80 sequences.

HG sizes are a non-linear scale.

Lots of exceptions but in general...

Value	Code
0	0
1	1
2	2
3	3
4	4
5	5
6	6
7	7
8	8
9	9
10	A
11	B
12	C
13	D
14	E
15	F
16	G
17	H
18	J
19	K
20	L
21	M
22	N
23	P
24	Q
25	R
26	S
27	T
28	U
29	V
30	W
31	X
32	Y
33	Z

 

[whulorigan]

I've come across some (very) rare formulas in random world generation where the tech level is 16 or greater. I have no real issue with this existing, but how does one notate this for the UWP?

My understanding of Hexadecimal is amateur at best. But after "F" it reverts to numbers starting at 10, right? Being the tech level, this appears after the hyphen in the UWP. So confusing a two digit number with the other single digit numbers won't really be an issue, but it just looks... funny.

I guess what I'm asking is: how do you guys handle numbers higher than 15 in hexadecimal for things like the UPP and UWP? Do you just use 10+ or just throw convention to the wind and continue the alphabet from G?

By the way, I know this is a completely fiddly and useless fuss over a miniscule detail that will never affect anyone's enjoyment of the game. I'm simply asking out of idle curiosity.

The rule going all the way back to Classic Traveller is to continue the alphabetic progression, omitting "I" and "O" to avoid confusion with "1" and "0".

This results in a scale going all the way up to level 33 ("Z"), though in some applications, "X", "Y", and "Z" are considered "reserved" for redesignation by the GM as necessary.

The accepted term for this alphanumeric progression in Traveller today (under T5 rules at least) is "eHex" (extended Hex).

 

[Easterner9504]

Look up Darrian, it is TL16 and shown as G.

 

[Shonner]

I've come across some (very) rare formulas in random world generation where the tech level is 16 or greater. I have no real issue with this existing, but how does one notate this for the UWP?

My computer programs use "G" for 16, and continue on through.

Then I got confused, like the rules state at times, when reading "I" and "O" using certain fonts. So I just recently omitted those two letters. "P" or "Q" is the highest letter I see in my outputs.

 

[inexorabletash]

T5 labels this eHex, which is as good a term as any.

(EDIT: Sorry, already mentioned above, sorry for the noise.)

 

[GoblynByte]

I discovered this while doing an excel spreadsheet for calculating UWPs. It involves the command DEC2HEX. Obviously this converts it to standard hexadecimal. I don't see much of a workaround for that other than keeping an eye out for it and changing it manually. Must I do *everything* myself? :rofl:

 

[inexorabletash]

eHex to Decimal:
FIND(n, "0123456789ABCDEFGHJKLMNPQRSTUVWXYZ") - 1

Decimal to eHex:
MID("0123456789ABCDEFGHJKLMNPQRSTUVWXYZ", n + 1, 1)

 

[hdan]

eHex to Decimal:
FIND(n, "0123456789ABCDEFGHJKLMNPQRSTUVWXYZ") - 1

Decimal to eHex:
MID("0123456789ABCDEFGHJKLMNPQRSTUVWXYZ", n + 1, 1)

Yes, this is the best way I've come up with doing this too, though translated into whatever my language of choice is for the project.

 

[aramis]

Yes, this is the best way I've come up with doing this too, though translated into whatever my language of choice is for the project.

in c/c++ or java, use an enumerated type

 

[GoblynByte]

eHex to Decimal:
FIND(n, "0123456789ABCDEFGHJKLMNPQRSTUVWXYZ") - 1

Decimal to eHex:
MID("0123456789ABCDEFGHJKLMNPQRSTUVWXYZ", n + 1, 1)

Hmmm... I'll see if I can figure that out. Thank you! Very useful.

 

[hdan]

in c/c++ or java, use an enumerated type

That doesn't print well in c/c++. I find it easier to just use integers internally and convert to "traveller digits" on output or input.