Error codes

This page is intended only for developers. If you’re a user of SplameiPlay, please read our troubleshooting page.

0_DESERIALIZE_FAILURE (0x001)

Cause

This error occurs when SplameiPlay fails to deserialise it’s save file. This could be for the app itself or recap

Fixes

This error is usually due to a corrupted save file. If this is the case, the only fix would be by deleting the save file found in %appdata%/Splamei/SplameiPlay/Saves.

0_SERIALIZE_FAILURE (0x002)

Cause

This error occurs when SplameiPlay fails to serialise it’s save file or save it. This can be trigged by any of SplameiPlay’s save files

Fixes

This error is usually due to a corrupted save file. If this is the case, the only fix would be by deleting the save file found in %appdata%/Splamei/SplameiPlay/Saves.

0_SAVE_FILE_404 (0x003)

Cause

This error occurs when SplameiPlay fails to check if it’s save files exists. It usually isn’t a SplameiPlay issue.

Fixes

Since this is usually an API issue, make sure the version of the .NET Framework installed on your system is updated and that the installation isn’t damaged.

0_INDEX_DESYNC_ERROR (0x004)

As of SplameiPlay 5.0 Particle, this error has been made obsolete and will not occur in normal installs

Cause

SplameiPlay has lists knows as the index. These combination of lists store data needed for SplameiPlay. When these list get different counts, SplameiPlay has to stop running as one or more of the lists has become corrupted and if SplameiPlay kept running, issues would occur with SplameiPlay attempting to retrieve a value outside the range of the list or data would be ignored.

Fixes

When this exception occurs, SplameiPlay automatically clears the offending index lists and will show the error screen. Because of this, usually, no extra action is required but you may need to delete the save file if this issue continues to occur

3_EXTRACTION_EXCEPTION (0x005)

Cause

During the installation process when adding a project in SplameiPlay, an exception may occur while extracting the zip file. This may occur due to a corrupt zip file or an error saving the uncompressed files.

Fixes

If you still receive this error when trying again, try reinstalling SplameiPlay or changing where SplameiPlay will store projects. If you still receive this issue, the zip file is corrupt so you’ll need to contact the publisher to fix the file.

4_SPINSTALLER_PARSE_EXCEPTION (0x006)

As of SplameiPlay 5.0 Particle, this error has been superseded by 5_FILE_PARSE_EXCEPTION (0x00F)

Cause

This exception occurs when SplameiPlay failed to parse the data given within an .spinstaller file. This error typically occurs when the data provided within the file is invalid and so, SplameiPlay cannot understand it

Fixes

Make sure the syntax of the file is correct and that SplameiPlay has the permission to access the file. If this exception still occurs, try reinstalling SplameiPlay

0_PAGE_SETUP_EXCEPTION (0x007)

Cause

This exception occurs when SplameiPlay is loading the saved data in the index that contains the data for custom projects. If SplameiPlay failed to decode this data, it will trigger this exception and stop running. This is commonly caused due to SplameiPlay trying to load corrupt data within the index.

Fixes

Try reopening the project page but if this exception continues to occur, the index has become corrupted. You’ll needed to delete the main save file and try again.

1_PROJECT_UNINSTALL_EXCEPTION (0x008)

Cause

This exception will occur when SplameiPlay attempts to uninstall a project. SplameiPlay will remove all references (except from recap) of the project from the index and delete all the files for the project that SplameiPlay manages. Sometimes this may fail when the files no longer exists because of their removal during runtime or a corrupt save file.

Fixes

Firstly, restart SplameiPlay to see it it realises the absence of the project. If the exception continues to occur, the save file’s index may have become corrupted. In this case, you’ll have to delete the save file.

4_FILE_LAUNCH_EXCEPTION (0x009)

Cause

When SplameiPlay attempts to launch a project, it will launch the file that it is told to run. This exception will occur when the process of running the file failed. Typically due to the file not existing.

Fixes

Make sure the executable file SplameiPlay runs does exist and that your user and SplameiPlay has the permissions to launch the file. SplameiPlay may also need to be updated or re-installed. If the exception continues, try deleting the save file or re-installing the project.

4_FILE_LAUNCH_EMPTY (0x00A)

Cause

If the location provided within the save file index is incorrect, when SplameiPlay attempts to launch the faulty project, it will be unable to file the file to be opened. SplameiPlay performs checks when starting to ensure that the index locations are correct so this error is likely due to the files being deleted at runtime.

Fixes

Restart SplameiPlay to allow it to perform the location check for the project to be automatically removed if still faulty. Also verify that no other process is deleted the files that SplameiPlay is using.

4_SPTHEME_PARSE_EXCEPTION (0x00B)

As of SplameiPlay 5.0 Particle, this error has been superseded by 5_FILE_PARSE_EXCEPTION (0x00F)

Cause

This exception is typically due to an incorrectly created theme file where the syntax within at least one of the lines is incorrect

Fixes

Verify the syntax of the lines within the .sptheme file and hex code to make sure they are correct. Sometimes, SplameiPlay may be too new or too old so it’s best to update the theme file and SplameiPlay to the latest versions.

0_POLICY_FILE_EXCEPTION (0x00C)

Cause

When SplameiPlay is doing it’s initial read of a .splameiplay policy file, if it is unable to get it’s file version, type or if it’s a ‘hopping’ policy file.

Fixes

This is likely due to an incorrectly set up policy file so check to make syntax of the policy file is correct and that SplameiPlay can read from it.

0_POLICY_HOP_LOOP (0x00D)

Cause

Once SplameiPlay has requested for 50 files for a policy and all files request SplameiPlay to ‘hop’ to a new file, SplameiPlay will detect that a ‘Policy Hop Loop’ is occurring so will terminate the policy.

On SplameiPlay 5.0 Particle and later, this error can also occur when SplameiPlay detects it’s hopping to a policy file it already hopped too.

Fixes

Make sure that SplameiPlay can access the policy with as little ‘Policy Hops’ as possible and verify that all policy files SplameiPlay will access do not lead to SplameiPlay returning to a previous policy file.

0_INCORRECT_POLICY (0x00E)

Cause

If SplameiPlay fails to read the policy file due to an invalid syntax or unknown policy term, SplameiPlay will be unable to decode and parse the policy file. The policy file may also be rejected by SplameiPlay if it uses an incompatible version.

Fixes

Verify the syntax of the policy file and make sure any text that should be ignored starts with - to make it a comment. Also make sure that the policy file and SplameiPlay are at their latest version to make sure they are compatible.

The following errors were added in SplameiPlay 5.0 Particle and will not occur in older version

5_FILE_PARSE_EXCEPTION (0x00F)

Cause

If an exception is thrown when SplameiPlay attempts to read the File Syntax, this error will trigger. Is it a recoverable error however, further errors may occur.

Fixes

This usually occurs due to a syntax error however, it can also occur when SplameiPlay fails to read the file it’s targeting. For information about the file syntax, please read here.

6_FLOW_CLIENT_INIT_EXCEPTION (0x010)

Cause

If an exception is thrown when the SplameiPlay Flow client attempts to initialise itself, this error will also occur. This is a non recoverable critical error.

Fixes

Normally, this error occurs when the save code provided by the SplameiPlay Flow client is not valid meaning a restart will fix the error as SplameiPlay will initialise with a new code. Otherwise, it could signify a critical issue with the SplameiPlay Flow client. Making sure SplameiPlay is updated and it’s not being blocked by your network provider may also fix the error.

0_FILE_DIRECTORY_ACCESS_VIOLATION (0x011)

Cause

This error occurs when an exception occurs when SplameiPlay attempts to get a full, safe path from a unsanitised one. Typically, the exception is an AccessViolation meaning SplameiPlay attempted to access a path containing invalid characters. ‘Back-out’ characters (\..\) will often cause this exception. This is a non recoverable critical error that can be triggered anywhere in SplameiPlay.

Fixes

Verify the install location is a valid directory and that projects are also installed in the correct directory. Otherwise this is a critical issue you most likely can’t fix so please report it on GitHub or via email.

1_INVALID_REQUIRED_SPLAMEIPLAY_SYNTAX (0x012)

Cause

This error occurs when SplameiPlay failed to read the play data or release data files for a project. This may be due to missing keys, invalid values or an entire invalid file. This error is recoverable but will prevent the download of the project.

Fixes

Verify the data follows the SplameiPlay File Syntax and is accessible by SplameiPlay. The logs should indicate the exact place where SplameiPlay failed.