This repository has been archived by the owner on Mar 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Type
Alex "Archcannon" Chen edited this page May 13, 2020
·
1 revision
There is some ambiguous terminology regarding "Types" in Transcendence extensions. Here, we define the terms that Transgenesis uses.
- DesignType: In Transcendence, a DesignType is an XML structure that defines the content of a game type. It has an attribute
UNIDspecifying the UNID of its type. - UNID: In Transcendence, a UNID is a hex integer unique to a Type.
- Entity: A string of the form
&{codename};that represents some data; in Transcendence, this data is a UNID. During processing, the Entity gets replaced by the UNID. Transgenesis allows you to define an Entity without an associated UNID, in which case the UNID will be auto-generated on file save. - Type: In Transcendence, a Type is a DesignType bound to a UNID. No two Types can have the same UNID. Here, we consider a Type to be a DesignType bound to an Entity, so we don't have to worry about the UNID conflicts.
In TranscendenceRL, we simply bind DesignTypes to codenames