UNID Database

[Hades]

My last one was invalid.
0x3a2b - Hades

[Fatboy]

Um... is that your invalid one?


it has to start in D or E and have A-F and numbers 0-9 3 digits afterward, like this 0xE3A2.

[Hades]

My last one was invalid.
0x3a2b - Hades

Okay then make it - 0xD1A3

[Psycholis]

DEED - psycholis

reposted for format

[H Iris]

Can I have 0xD7770000 - H Iris?

Couldn't find in the posts so i'll guess its not taken.

[wnmnkh]

0xD010 -wnmnkh

[Aury]

0xD010 -wnmnkh

wait... >.> are you wnmnkh of the battleship threads on the gpg forums?

Anyways, I'd like to register BOTH xD314 and xE314 as mine since I have two large mods and I didn't want to risk conflicting ID's (both mods could very easily reach into the thousands of UID's (E314 is already mine)

[F50]

Can I have 0xD7770000 - H Iris?

Couldn't find in the posts so i'll guess its not taken.

If it is not in here it is not taken, but you actually want

0xD777****

as only the first four digits are registered and the rest belong to you for free.

[Periculi]

Another thing about the UNID- you can get a LOT of them from a single registered unid prefix. tens of thousands, I do believe. If you follow the numbering standards for item/ship/station (0xDDDD# where # is defined by the type- 4 for items, for example) you have at least 16^3 (4096) per design type, but if you need more you can ignore the conventions and get 16^4. (65536 uniques)

More importantly- when are we going to update the top post, move the table of registrants to xelerus or otherwise get back on track tracking these?

[Aury]

Another thing about the UNID- you can get a LOT of them from a single registered unid prefix. tens of thousands, I do believe. If you follow the numbering standards for item/ship/station (0xDDDD# where # is defined by the type- 4 for items, for example) you have at least 16^3 (4096) per design type, but if you need more you can ignore the conventions and get 16^4. (65536 uniques)

I like to organize my UNID's: ie, 0*** are resources, 1***-5*** are items 6***-A*** are ships/stations etc...

Thus not all of them will always get used, but enough of a potential to warrant using two... anyhow, backup is nice...

[evilbob]

my UNIDs then to be a mess, organised only by A###, B### etc for each mod file I make, to avoid conflicts

[Periculi]

I followed George's methods. He has the design types separated according to this schedule: (from transcendence.xml)

Code: Select all

	UNID Namespace

	0x D MMM T III

	T		Type ID. Within a module, the division of the namespace is
			undefined. Transcendence uses this value to represent the
			type of object assigned an UNID:

			0	star system description
			1	sovereigns
			2	station types
			3	ship classes
			4	item types
			5	special item types (virtuals)

			8	random tables (items, encounters)
			9	effects, energy fields, space env, etc
			A	dock screens
			B	powers

			F	images and sound resources

MMM is what we register here. 0xD is for all player mods.

[Aury]

I followed George's methods. He has the design types separated according to this schedule: (from transcendence.xml)

Code: Select all

	UNID Namespace

	0x D MMM T III

	T		Type ID. Within a module, the division of the namespace is
			undefined. Transcendence uses this value to represent the
			type of object assigned an UNID:

			0	star system description
			1	sovereigns
			2	station types
			3	ship classes
			4	item types
			5	special item types (virtuals)

			8	random tables (items, encounters)
			9	effects, energy fields, space env, etc
			A	dock screens
			B	powers

			F	images and sound resources

MMM is what we register here. 0xD is for all player mods.

that's what i based it off of. though I rationalized it out a bit.

[Periculi]

yeah, I see that. Good thing we don't actually have to follow the naming standards, eh?

[Aury]

yeah, I see that. Good thing we don't actually have to follow the naming standards, eh?

yeah then we'd have extraordinary amounts of wasted UNID's