Home

First Startup

To use SimplePersist, simply add the following to your servers startup command.

-servermod=@simplepersist

When the server starts, you should see some INIT logging occur. Each module has it's own startup sequence, below is an example of the current functionality where only the Player Module is loaded.

"[SPP] | INFO | SimplePersist Player Module Loading."
"[SPP] | INFO | Adding Event handlers"
"[SPP] | INFO | SimplePersist Player Module Loaded."

General Config Options

Within Simple Persist there are a few config options that you are able to set in your Description.ext file.

Logging

Setting: SPLogLevel - Decides the log level which should be output to the RPT File for Simple Persist.

Add to initServer.sqf

missionNamespace setvariable ["SPLogLevel", 3]

See here for more options: https://github.com/Toakan-Network/SimplePersist/wiki/Settings#logging

Storage Locations.

Currently Simple Persist only supports

• ProfileNameSpace
• MissionProfileNameSpace.

Setting: SPSaveLocation - Decides how the data will be stored.

Add to initServer.sqf profileNamespace setvariable ["SPSavelocation", 1]

See here for more information: https://github.com/Toakan-Network/SimplePersist/wiki/Settings#StorageLocation

Role Based Storage

For Role based saving.

The following command will enable the server to utilise Role based saving, it needs to be added to initServer.sqf. profileNamespace setvariable ["SPSaveRoles", 1];

There is additional parameters which will then need to be added to each Playable Unit INIT in EDEN. this setvariable ["SPRoleID", "Unique ID"];

This should be a Unique Value per role, so it is possible to create 5x Sharpshooters roles which share their ID. this setvariable ["SPRoleID", "Sharpshooter"];

If the Unit does not have a SPRoleID set, Simple Persist will default to normal behaviour. This means that it is backwards compatible, and if you only have certain roles that you really need to persist separately, you can do so.