Date: Thu, 28 Mar 2024 16:00:46 +0000 (UTC) Message-ID: <514682752.21.1711641646205@b606f581ddb0> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_20_1745887905.1711641646203" ------=_Part_20_1745887905.1711641646203 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can define custom data for Shadowrun 6 in Genesis. This is d= one by writing XML data files with the corresponding translation files.
Locate your data directory
Go to the Genesis settings. First thing on the screen is an information abo=
ut your current data directory.
Create a custom/shadowrun6 subdirectory in your data directory=
strong>
In the =E2=80=9Ccustom=E2=80=9D subdirectory, create a =E2=80=9Cshadowrun6=
=E2=80=9D directory.
Create an XML-file and a corresponding .properties-file=
Genesis detects the kind of data by the prefix of the filename. E.g. if you=
want to define custom spells, create a file =E2=80=9Cspells_mine.xml=E2=80=
=9D and the corresponding =E2=80=9Cspells_mine.properties=E2=80=9D
As an optional step, you can add a corresponding -help.properties-file (e.g=
. =E2=80=9Cspells_mine-help.properties=E2=80=9D) to add full text descripti=
ons.
The currently supported prefixes are:
=E2=80=9Cgear=E2=80=9D, =E2=80=9Citem=E2=80=9D, =E2=80=9Cequipment=E2=80= =9D for any kind of gear
=E2=80=9Cmodification=E2=80=9D for item enhancements
=E2=80=9Cspells=E2=80=9D for - Surprise! - spells
=E2=80=9Ccomplex=E2=80=9D for complex forms
=E2=80=9Cpower=E2=80=9D for adept powers
=E2=80=9Cqualities=E2=80=9D for positve or negative qualities
=E2=80=9Cskills=E2=80=9D for new skills
=E2=80=9Ctradition=E2=80=9D for magic traditions
=E2=80=9Cmentor=E2=80=9D for mentor spirits
=E2=80=9Cmetatype=E2=80=9D for =E2=80=A6 well .. metatypes
=E2=80=9Cechoes=E2=80=9D for Echoes
=E2=80=9Cmetamagic=E2=80=9D for Metamagics (handled identical to echoes)=
The list above is not necessarily all we can do. You can issue a request= for further types in our ticket sysstem.
Unfortunately there is no documentation on how to write data files yet. = So your only option is to copy from the data from other products. We advise= you to study the XML files = here and the property file here.
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=3D"sg-100" avail=3D"2" cost=3D"2000" issue=3D"2020-11">
<useas type=3D"DRONES" subtype=3D"MINIDRONES"/>
<vehicle han=3D"3" acc=3D"8" spdi=3D"8" tspd=3D"20" bod=3D"1" arm=3D"0"=
pil=3D"2" sen=3D"2" type=3D"WATER"/>
</item>
Note that you have to use some existing =E2=80=9Ctype=E2=80=9D and =E2=80=
=9Csubtype=E2=80=9D, otherwise the item will not show up in the selection m=
enus. 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=3DHOME
plugin.Custom.productname=3DHomeBrew
plugin.Custom.productname.full=3DHomeBrew Rules
In addition it should contain name and page per item. For above drone th=
is could look like this:
item.sg-100=3DSG-100 Submarine Drone
item.sg-100.page=3D1
Note that you should assign a page number to the item, even if it is pag= e 1 for everything, otherwise there may be display errors.
C ) The help file can contain the description of the item. To do this, u=
se a simple line with .desc, like below:
item.sg-100.desc=3DThe SG-100 =E2=80=9CSpreewald Gurke=E2=80=9D is a small,=
gherkin sized, underwater drone build by a local manufacturer in Berlin.=
p>
Note that there is no limit to the length of text you can add, however i=
t needs to be in one line. If you want a line break in the output text, add=
=E2=80=9C\n=E2=80=9D into the text line and end the line with =E2=80=9C\=
=E2=80=9D (both without the =E2=80=9C=E2=80=9Cs). Bold or Italic are not su=
pported, but you can of course CAPITALIZE words.
For questions contact us.