Developer Help
This page introduces developer features available in SSP, along with a few tips for developing ghosts and other content.
For those of you who have been enjoying ghosts and now want to try making one yourself.
Or those of you who installed SSP with the intention of creating a mascot application from scratch.
There should also be useful information for those interested in creating content such as balloons and shells, rather than ghosts.
Unfortunately, SSP's help alone explains very little about how to make anything.
This page is intended only to explain SSP's features.
However, as a starting point, we've also prepared a few extras: a collection of links and frequently asked questions. We hope you'll use them as a starting point and explore the sites linked there.
What to Do First
In Preferences, open General and turn ON "Enable developer features".
The first time you turn this ON, a dialog may appear. If so, just proceed through it.
This will make the settings in Development / Miscellaneous available and add several items to the "Features" section of the right-click menu.
It will also add settings to Ghost preferences and its default settings.
Adjusting Settings
We recommend the following settings during development.
Preferences - Ghost (1)
- Update check method
Strict (SSP default setting).
Preferences - Development / Miscellaneous
- Create update files and NARs when a folder is dropped
ON.
This makes it easy to create update files and NARs. - Do not include files with the read-only attribute in updates
ON.
This is a precaution to keep unnecessary files out of updates. - Hide when a surface does not exist
ON.
Normally, if a script specifies an undefined surface, the ghost displays its default expression (for example, surface0 for the\0side).
However, this can make it difficult to notice a mistake in a surface specification. Turning this setting ON to hide the surface completely can make such mistakes easier to spot. - Suppress Vanish (uninstall) execution
ON.
This helps prevent accidents such as accidentally deleting a ghost during development.
You may want to turn it OFF only when testing what happens during uninstallation. - Notify when errors at or above level ○○ occur
NOTICE.
NOTICE-level notifications can also help you spot possible errors in your code. - Use a version control tool for updates when available
ON.
Using a version control tool can help you recover from serious problems. - Use the exception handler
OFF.
This setting prevents SSP from stopping and the ghost from ending unexpectedly when a serious error occurs, such as an access violation while accessing memory.
This is useful for users, but for developers it can cause signs of errors to go unnoticed.
Preferences - Folders
It is useful to create a folder specifically for ghosts under development, and keep your in-progress ghosts and ghosts with development support features together in it.
For that folder, we recommend turning on all the checkboxes in its folder-specific settings.
This prevents various events that could cause problems during testing.
You can also configure the same settings for individual ghosts using the development palette described below, but setting them here helps prevent accidental mishaps.
Of course, this also makes it easier to find ghosts when you have many installed.
Developer Features
1,Script log
Displays a history of the scripts SSP has received and executed. You can perform actions such as having a script spoken again or copying it.
You can also switch to the error log, which contains a history of error notifications.
⇒Details
2,Force Exit from Restricted Modes
Forcibly exits modes that restrict certain actions, such as passive mode and induction mode (these modes are normally started and ended by the ghost using Sakura Script controls).
If these modes are not turned off at the right time, they may effectively prevent you from using SSP. This feature can help in such situations.
On the other hand, if a mode is turned off when it should still be active, unexpected actions or behavior may occur and cause further problems.
Therefore, this feature is intended not as a regular emergency measure for users, but as a tool for developers to use while investigating and fixing problems that prevent a mode from ending normally.
3,Development Palette
Opens a window for controlling settings and tools that are very useful during development.
⇒Details
Development Links
A collection of useful sites and tools for creating and developing content.
⇒Development Links
Development FAQ
Answers to common beginner questions about development and how to handle problems.
⇒Development FAQ