Xelerus Rules and Standards

These standards were created by the community and should be considered before creating a mod! Following these rules should ensure good mods that enhance the gamplay.

The xelerus Admin (Bimbel) and all xelerus moderators (Digdug, Taben) have the right to edit, relocate and remove any mod at any time without any further notices. If you have the feeling that any of your mods was edited/relocated/removed by accident or you want further informations on why your mod was edited/relocated/removed please join the IRC and discuss it with any of us!

These standards apply to most non-utility, non-source, non-tutorial and non-development mods.

• If your mod over-writes vanilla content, it should clearly say that it does this. If it is NOT a TC (total conversion), it should say what it over-writes. This will help cut down on conflicting mods, and help people determine if a mod is causing a bug or if it is Transcendence itself.
• Please use proper english, grammar and punctuation. If english is not your first language, feel free to add a text in your language to the english one.
• Dnn't take ships/items/stations/… out of the game with only changing some values and making it your mod.
• Don't spam godmods! Taking a weapon and adding 100k damage or the like not only breaks the game, it is also doable by every modder and shouldn't be uploaded.
• Don't take single ships/items/stations/… out of the game and make them playable, instead try making a balanced mod pack of them or make your own ships/items/stations/….
• Don't spam similiar mods! If you have mods that are very similar think of releasing them as a modpack.
• Don't hold on old versions of your mods. You should always have only the newest release uploaded to avoid confusion!
• If your mod is not finished put it into the work in progress (WIP) category so that anyone notices it!

These directory standards should be followed strictly to avoid conflicts with other mods and to keep the mods organized.

• Stand-alone mods should be packaged in their own directory such as: …\trans10\extensions\[modname]\[modname].xml
• Subordinate mods should be packaged in a subdirectory of the mod that they modify. An example would be: …\trans10\extensions\[primarymodname]\[subordinatemodname]\[subordinatemodname].xml
• Resources (these include image and sound files the mod uses) should be packaged as: …\trans10\extensions\[modname]\resources\…
• For linux compatibility, it is best to use ”/” instead of “\” and make sure all directories are case-sensitive.

XML standards are strongly suggested. Non-compliance usually results in required fixing of the mod in question (or deletion if mod is not fixed). These standards apply to most non-source, and non-development mods.

• You should have a registered UNID for your mod. If nobody complains of a conflict, it will not be removed. However, if there are complaints of a conflict, it will have to either be fixed or removed. Any mod that uses someone else's UNID will be removed, as it causes conflicts that prevent Transcendence from starting. To register your UNID, please go to OTF UNID registration thread and request your UNID.
• The XML must work. All mods that prevent transcendence from launching will be immediately and promptly removed from xelerus. The only exception is for WIP/bugtesting mods to illustrate bugs or to get help for fixing them.
• No illegal UNIDS! These are UNIDS that contain non-hexidecimal characters AND/OR are not within the prescribed range (User UNIDS may range from 0xD000 to 0xEFFF).

XML standards strongly suggested. Non-compliance usually results in required fixing of the mod in question (or deletion if mod is not fixed). These standards apply to most non-source, and non-development mods.

• No illegal Hex. This means you cannot use characters in a hexidecimal field that are non-hexidecimal characters. Ex: 0xgg (correct use is 0xff)

Graphics standards are strongly suggested. Mods of such a low quality they burn out peoples' eyes will however usually be deleted (unless they fall under the “DO NOT apply” section. (see below). Also mods that over-recycle “free to use” ships in an inappropriate manner (see below) are also liable to be removed.

*NOTE: these rules DO NOT apply to mods that: a) do NOT focus on the graphics themselves (such as demonstrations, proofs of concepts, tutorials, mods focussing on other elements) b) mods using them the graphics as placeholders

*NOTE: these rules apply ONLY to mods that: a) advertise themselves as having “custom graphics” b) are in the “playerships” AND/OR “enemies” AND/OR “friendly” AND/OR “station” sections and DO NOT fall into sections “a” or “b” of thee exceptions section c) and do not fall under any of the “DO NOT apply” categories

• 2D ships are allowed fine, given that they are of good quality.
• 3D ships should generally avoid being grey-scale.
• No 3D ships made out of only a few primitives. (Unless it actually looks good, which is really a hard feat to accomplish)
• Please avoid making ships with graphics that wobble.
• Inappropriate use of “free-to-use” ship graphics includes: re-releasing a single dvelnk6 ship as a player ship
• appropriate use of “free-to-use” ship graphics includes: re-releasing all the dvelnk6 ships are playerships in a mod pack

These are the most strictly enforced of all standards. Any violations result in removal of the mod. Recurring violations MAY result in account removal at the discretion of Bimbel.

• No “stolen” mods. “stolen mods” are mods that have been blatantly copied and re-uploaded AND/OR mods that have been incorporated into another mod without the original author's permission.
• No mods that violate the laws of your country of residence.