...
A ) The data XML files need to start and end with the category, e.g. <items> some text </items>.
Within those boundaries, a new drone could look like this:
<item id="sg-100" avail="2" cost="2000" issue="2020-11">
<useas type="DRONES" subtype="MINIDRONES"/>
<vehicle han="3" acc="8" spdi="8" tspd="20" bod="1" arm="0" pil="2" sen="2" type="WATER"/>
</item>
Note that you have to use some existing “type” and “subtype”, otherwise the item will not show up in the selection menus. See the examples linked above for types and subtypes.
B ) The properties file needs to identify the content. For this it needs to include three lines like this:
plugin.Custom.productname.short=HOME
plugin.Custom.productname=HomeBrew
plugin.Custom.productname.full=HomeBrew Rules
In addition it should contain name and page per item. For above drone this could look like this:
item.sg-100=SG-100 Submarine Drone
item.sg-100.page=1
Note that you should assign a page number to the item, even if it is page 1 for everything, otherwise there may be display errors.
C ) The help file can contain the description of the item. To do this, use a simple line with .desc, like below:
item.item.sg-100.desc=SG-100 “Spreewald Gurke” is a small, gherkin sized, underwater drone.
Note that there is no limit to the length of text you can add, however it needs to be in one line. If you want a line break in the output text, add “\n” into the text line and end the line with “\” (both without the ““s). Bold or Italic are not supported, but you can of course CAPITALIZE words.
For questions contact us.
Related articles
...