Settings

Logging

SimplePersist uses built in logging to track information. There are three levels

• 1 = Error
• 2 = Information
• 3 = Debug

To enable Debug logging, use the following command in your Debug menu.

• missionNamespace setvariable ["SPLogLevel", 3]

Or you can add your preferred LogLevel to the missions initServer.sqf using the same command.

StorageLocation

SimplePersist by default uses the MissionNameSpace in order to store information.

• 0 = Default MissionNameSpace
• 1 = ProfileMissionNameSpace

It is possible to switch this to use the ProfileMissionNameSpace, however doing so means that additional steps are required when building missons. Using the ProfileMissionNamespace is preferred when you want to store data per MAP/Mission because you are then able to change the missionGroup for each new map and your old save data will be retained. Think of this as specify which save slot you want to use :)

In Description.EXT, you will need to set the following options.

missionGroup="YourCampaignNameHere";

In initServer.sqf, you then need to set the following.

profileNamespace setvariable ["SPSavelocation", 1];

The missionGroup will tie your mission data to a specific file, which is required if you plan on using EDEN to modify the file after an operation or game session, but you want to keep your player data available.

Doing this also splits off the storage from the main vars storage that ProfileNameSpace uses, so it is possible to set a different storage group for every mission, and not have them all interfere with each other.

See the Wiki for more information on this.

Deleting Data

If you want to delete SP data, you will need to delete the Vars file which contains it.

• If you are not using SPSaveLocation = 1 this file will be the default Server Profile.Vars file.
• If you are using SPSaveLocation = 1 then the data is stored into the <MissionGroup>.vars file (The name is the same as your setting for MissionGroup).

You can find more information here: profileName.