This is an old revision of the document!
Table of Contents
Every extension declares the version of Transcendence that it is compatible with. This allows the Transcendence engine to maintain the greatest level of compatibility while still adding new features and evolving the API.
Starting with Transcendence version 1.08e, the method for declaring the compatibility version has itself changed. An extension that is aware of all the changes in 1.08e must declare itself compatible by adding a new property in its root element:
<TranscendenceExtension ... apiVersion="12" ... > ...
This new property, apiVersion will be used in future versions to track the API that the extension wishes to use. (Note the lack of a period in the version.)
Extensions may still use the older version property to specify that they wish to be compatible with older versions.
API Version 13
Engine version: 1.2 Alpha 1 and above.
Devices
- Added hpBonus to <Device> and <DeviceSlot>
Stations
- Added maxLightRadius= parameter to stars (<StationType>)
- Added <FilterColorize> element to station <Image> tags.
- Added <AcceptDonation> tag to <Trade>
- Added <Refuel> tag to <Trade>
- Added <InstallArmor> tag to <Trade>
- Added <InstallDevice> tag to <Trade>
- Added <RemoveDevice> tag to <Trade>
- Added maxAppearing parameter to <StationType>
System Definition
- Added aOrbit variable to <Code> in system definitions.
- Added <OrbitalDistribution> as <SystemType> directive
- Added radius= and angle= to <Offset> directive in <SystemType>
- Added minDist= and maxDist= to <RandomLocation>
- Added minDist= and maxDist= to <FillLocations>
- Added count= to <FillLocations> (used if percentFull is omitted).
- <RandomStation> directive in <SystemType> takes parameters valid for <Station>
- Added “systemLevel:…” syntax to levelFrequency in <RandomItem>
- Deprecated <FillRandomLocation>; use <FillLocations> instead.
New and Changed Functions
- (msnFireEvent)
- (msnGetProperty): Added 'acceptedOn property to missions
- (msnGetProperty): Added 'description property to missions
- (msnGetProperty): Added 'name property to missions
- (msnGetStaticData)
- (objGetProperty): Added 'orbit to station properties
- (objGetProperty): Added 'repairArmorMaxLevel property to stations.
- (objGetProperty): Added 'installDeviceMaxLevel property to stations.
- (sysOrbitPos)
- (typFind): Added isEnemyOf:{unid} to typFind (for station types)
- (typTranslate)
- (unvFindObj)
Miscellanous
- Added <Type> to create generic types (for holding global data, etc.)
- <Language> elements parse and translate escape sequences (e.g., %name%).
Core Libraries
- Added stK-TypeStar to Universe library
- Added stNebulaStar to Universe library
- Non-random star systems now create extra stargates if needed.
- Only nodes with “huaramarcaGate” attribute are eligible for gate to Huaramarca.
- Added “BasicFuel” attribute to all basic fuels (all except uranium, Heliotrope fuel, and longzhu)
- Added dsPRGReful screen
- srvFindRepairArmor checks for <RepairArmor> tag, so “NPCService” data is deprecated
- Added dsRPGDeliveryMission
API Version 12
Engine version: 1.08e and above.
- apiVersion property used to specify compatibility version.
- Player ship classes must use “00200000_PlayerShip” attribute in order to appear as a player ship in Stars of the Pilgrim adventure.
- Engine validates existence of sound references. I.e., types cannot refer to non-existent sound UNIDs.
- An extension/adventure cannot define multiple types of the same UNID (an error will be reported). In previous versions one of the types was silently ignored.
API Version 1.1
Engine version: 1.04 and above.
NOTE: You must use version=“1.1” to access this API version.
API Version 1.0
Engine version: 1.0 and above.
NOTE: You must use version=“1.0” to access this API version.
- For version 1.0 and below, when defining weapons, passthrough should not equal “0” (or it will default to “50”).
- For version 1.0 and below, when defining <SmokeTrail> effects there was a bug with emitSpeed. Double the normal speed for compatibility.
- For version 1.0 and below, when defining weapons, the shield damage modified used a different calculation because we only allocated 3 bits for the damage range.e.