Script Debugger saves the following information into a compiled script file:

• The compiled script bytecode.
• The script’s description, if any.
• Persistent information such as the current values of script properties.
• Script window state (such as its size and position) and view settings, plus:
  • What panes (such as the result pane) are showing and how they are configured.
  • Event log pane and window configuration.
• Libraries.
• Expressions.
• Breakpoints, if the script is saved in debug mode.

For a plain compiled script file, Script Debugger stores some secondary information in the file’s resource fork. In a bundle format file, however, no resource forks are used; secondary information is saved in separate files. (The description is saved in an .rtfd file, the recovery text is saved in an .rtf file, and the other secondary information is saved in a .plist file.) For this reason, a bundle format file is the most compatible with version control systems, non-Mac filesystems, and so on.