Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Ready to add to the bottom of the server's "types.xml".
<!-- Solar-Panel-Power-System -->
<type name="RFSolarPanel">
<lifetime>3888000</lifetime>
<flags count_in_cargo="0" count_in_hoarder="0" count_in_map="1" count_in_player="0" crafted="1" deloot="0"/>
</type>
<type name="RFSolarPanelKit">
<nominal>18</nominal>
<lifetime>172800</lifetime>
<restock>1800</restock>
<min>12</min>
<quantmin>-1</quantmin>
<quantmax>-1</quantmax>
<cost>100</cost>
<flags count_in_cargo="0" count_in_hoarder="0" count_in_map="1" count_in_player="0" crafted="0" deloot="0"/>
<category name="tools"/>
<usage name="Industrial"/>
<usage name="Town"/>
</type>
...
QUESTION:
what is the syntax for using the modular approach?
thanks in advance.
The syntax would be this.
In ^cfgeconomycore^, at the bottom, add these strings:
<economycore>
<classes>
.
.
.
.
.
<ce folder="Mods">
<file name="typesXXX.xml" type="types" />
<file name="typesSolarPanelPowerSystem.xml" type="types" />
<file name="typesYYY.xml" type="types" />
<file name="typesZZZ.xml" type="types" />
<file name="cfgspawnabletypesXXX.xml" type="spawnabletypes" />
</ce>
</economycore>
The "types" files if you only have a "unitary" spawn (single pieces), you can add the "cfgspawnabletypes" files if you have "complex" spawns (objects with attachments inside to select, like accessories on weapons).
In the mission folder "...\mpmissions\dayzOffline.chernarusplus" add a "Mods" folder (but you can call it whatever you want, as long as the name is the same in all its references).
Inside that "Mods" folder you add the various files "typesXXX.xml", "typesYYY.xml", "typesZZZ.xml" and "cfgspawnabletypesXXX.xml" formatted from start to finish as unique files, and each one for its own mod .
Upon reboot everything should work as intended. In the case of an update, of course, you have to review all the files, but having separated them, each one will have its own story. That is, with a new patch, you will have a new "types", but it won't change the mods one. If the "cfgeconomycore" also changes in the new patch, until you re edit it, you will lose all mods.
In short, advantages and disadvantages also for this solution, there is no "The Solution" right for everything.
In my opinion, for 2/3 "simple" mods it's not worth it. Add the typi to the end of the "types.xml" file and it's much faster.
If you have a server with many mods and some even complex and articulated ones, then this additional work certainly has its advantage, but immediately take into account that the more complex the system you use, the more complex the maintenance will be and the more risk you will have of "errors and omissions".
Good job, that DayZ is already a "madhouse" of her ... ;-)
And, sorry for my bad English but I must use Google.