Projects and Resources

A project keeps your Scenes, reusable resources, settings, and declarations together. Save the authoring project to keep the work you build.

Player progress uses separate saves. File > Save stores your .mythproj authoring project. The Save Game Action records runtime progress in a player-storage slot. Saving and Loading Progress explains those slots.

Keep Project Files and Media Together

In desktop Myth, a new project gets its own folder. After saving media as separate files, a project named Forest can look like this:

Forest/
  Forest.mythproj
  Forest.assets/

The .mythproj document stores your project structure and resource references. The companion .assets folder holds external image files and other media that the document references. Keep the two beside each other. Their names match: Forest.mythproj looks for its external media inside the companion Forest.assets folder.

A project with no external media may have no companion folder. Check the saved folder after importing the intended media and saving, before moving your work. Copy every referenced media file.

Use File > Save as… to save under another name or location. For external media, Myth writes the document and matching .assets folder. The project name follows the selected filename. For example, Forest Copy.mythproj uses Forest Copy.assets for its external media.

Keep exported art somewhere you can choose it again when a later edit needs reimport. Source exports support that authoring step. Saved media supplies the existing imports in the copied project, even when you have not reimported them. Choose original source exports through their relevant editors.

Follow a Resource Into the Game

A resource is a reusable Thing, such as a Sprite, Sound, Object, Scene, or Logic Component. For a moving character, the connections are:

Resource or Setting	What It Supplies
Sprite	The imported image and its frame data.
Object’s Sprite component	The selected Sprite and that component’s display settings.
Attached Logic Component	The Events and Actions controlling the character, with inputs bound on the Object.
Scene placement	An occurrence of the Object at a particular location.
Game Settings	The Scene where the game begins.

The same Sprite can serve several Objects. You can also place the same Object in several Scenes. Each placement is an instance. Objects and Components explains resource ownership; Scenes and Instances covers placement state.

Give each resource a name that describes its role, such as Door State or Forest Entrance. Many references pair a stable resource identity with a readable name. Rename through the editor to preserve those relationships. After deleting a shared resource, inspect diagnostics and repair its dependent references.

For all categories, see Resource Types. Weighted Maze’s first chapter shows project creation and how its resources work together.

Check a Missing Connection

Start with the Sprite resource that owns the imported image you expect to see in play. The Sprite Editor guide shows its import and frame controls. Check the image first.

Next, inspect the Object’s Sprite component and its selected resource. A correct image does not assign itself to an existing Object. Select the intended Sprite there.

Check the exact Scene occurrence in Scene Explorer, then its active and starting visibility settings. Before changing imports, check the game’s start Scene and run it to inspect the exact placement. Repair the first broken connection. A Sprite reimport supplies image data; a missing Scene placement needs a placed Object.

Move or Archive a Saved Project

1. Stop the playtest and choose File > Save. Wait for the save to finish.
2. Copy the complete project folder, including its document and associated media. Keep the original intact.
3. Open the copied .mythproj with File > Open Project…, then inspect its imported image and Object assignment.
4. Start a fresh run from the intended Scene. Confirm the expected art appears and the affected interaction works.
5. Keep the original folder until the copied project passes every check you needed for this change.

The reopened copy should contain the intended resources and their saved media. Test from the copied path. An image cached by an already open original project can hide a missing file.

For file and recovery problems, see Project Files and Missing Assets.