cfgeconomycore.xml (in mpmissions/<map>/) tells the central economy (CE) which root classes it manages, which logs it writes and which extra folders of CE files it must load. It is mostly edited to plug in the files of a mod or a map.
How to use the tool
Import your current cfgeconomycore.xml (recommended) or start from the proposed root class list.
Add, edit or delete root classes (name, act and reportMemoryLOD columns).
Set the log variables (one per line, name=value) and, for a mod, the CE folders (folder|file|type).
Fix the warnings in the “Checks” panel, then download the file.
Replace mpmissions/<your_map>/cfgeconomycore.xml and restart the server.
Adding a mod's files
Put the mod's files in a subfolder of the mission (e.g. mpmissions/<map>/custom/), then declare them here. Each line of the “ce” field becomes one <file> tag; the expected type is types, spawnabletypes or events.
custom|my_mod_types.xml|types
custom|my_mod_spawnabletypes.xml|spawnabletypes
custom|my_mod_events.xml|eventsFrequently asked questions
- What does “rootclass” do?
- It declares the classes whose objects (and derived ones) are tracked by the central economy. Only remove vanilla classes if you know what you are doing: items might stop spawning or being cleaned up.
- Is my data sent to a server?
- No. The file is read and generated in your browser; only your settings are kept in localStorage.
