-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathmodDesc.xml
More file actions
42 lines (34 loc) · 1.71 KB
/
modDesc.xml
File metadata and controls
42 lines (34 loc) · 1.71 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
<?xml version="1.0" encoding="utf-8" standalone="no" ?>
<modDesc descVersion="67">
<!--
As you can see only the parts which addSpecialization require are shown here.
-->
<extraSourceFiles>
<sourceFile filename="scripts/AddSpecialization.lua"/>
</extraSourceFiles>
<l10n>
<text name="GLOBAL_TEXT_1">
<en>This is my global text!</en>
</text>
</l10n>
<!--
l10nNameTag - Optional - Make text global so we can use it on the mod. Name it like following in modDesc GLOBAL_TEXT_1, GLOBAL_TEXT_2...
debug - True / False - Log the work flow
- The following tags can be used multiply times -
vehicleTypeLimit - Optional - True / False - Limit to what vehicle type to add specialization into, True = Add to this type, False = Don't add to this type. Remove tag if not used.
restrictions - Optional - 0 / 2 - Specialization which we must/can't have.
searchWords - Optional - 0 / 2 - This will search for an match for this word in the specialization name
States
0 = Required specialization, all of these must be found to pass
1 = Unallowed specialization, fail if any of these are found
2 = Allowed specialization, if any of these are found then it will pass the checks
-->
<addSpecialization>
<specialization name="SampleSpecialization" className="SampleSpecialization" filename="scripts/SampleSpecialization.lua" l10nNameTag="GLOBAL_TEXT" debug="false">
<vehicleTypeLimit state="false" name="combineDrivable" />
<restrictions state="0" name="drivable" />
<restrictions state="2" name="motorized" />
<searchWords state="1" name="fillVolume" />
</specialization>
</addSpecialization>
</modDesc>