-
-
Notifications
You must be signed in to change notification settings - Fork 6
Legacy Split Format
NOTE: This information pertains to .split files made using Splitter < 4.0. For the current version, see .Split-format.md. Newer versions of Splitter (≥ 4.0) can still open files saved in the legacy format, but modifying the and saving the file will render it incompatible with older versions of Splitter.
The root folder of the .split
bundle can contain the following:
-
runInfo.json
- Contains the metadata and segments of the run. -
appearance.json
- Configures the appearance for Splitter. -
gameIcon.png
- The game’s icon, if it has been set. -
runIcons/x.png
- the icons for individual segments, if they have been set (see below)
-
title
- The title of the Game/Run (i.e. "Super Mario Odyssey") -
category
- The Category of the run (i.e. "Any %") -
attempts
- An integer value of the number of time the user has attempted this run. -
platform
- A string representing the platform the game is being played on (i.e. "Switch") -
gameVersion
- Version of the game that is being run (i.e. 1.3.0) -
version
- Version of Splitter that created the file -
build
- Build number of Splitter that created the file
NOTE: "Time" with regards to a segment refers to the total time since the beginning of the run, not the time from the beginning of the segment.
-
name
- Name of the split -
personalBestTime
- The user's current personal best time for that segment. -
previousPersonalBestTime
- PB time, prior to the current time. This is used for comparison (i.e. when you have made a new PB in a run, the old time must be kept to compare the new and the old time) -
currentTime
- the time the user most recently completed the segment at -
previousTime
- the time the user completed the segment prior to their most recent attempt. This is used for comparing the current time to the previous attempt. -
startTime
- date/time the user started the run at, in RFC 3339 format. -
endTime
- date/time the user ended the run at, in RFC 3339 format.
Within the runIcons
directory are .png
files for each segment with a corresponding icon. If a segment doesn't have an icon, that index is skipped.
For example: A run has icons set on segments 0, 1, and 3. Segment 2 does not have an icon set. The runIcons
folder will be as follows:
0.png
1.png
3.png