LÖVE saves and paths
Stores progress in the game’s writable save area rather than inside packaged files. It validates versioned data without executing saved Lua and preserves the last valid state if replacement or migration fails.
love-save-filesystem
See how it helpsWhen is it useful?
Use when packaged builds cannot find saves or content updates change the format.
What does it help you do?
- Distinguishes packaged source reads from writable save storage.
- Preserves game identity and stable identifiers in saved data.
- Keeps the last valid save during failed replacement or migration.
Try asking this
Save unlocked levels and control settings for our puzzle game. Launch from a read-only installation, load a damaged save and test an older format. Use the intended game identity directory, keep data separate from executable Lua and offer recovery without overwriting the last valid progress.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
LÖVE — save filesystem
Use when persisting LÖVE settings, saves, user content or packaged asset paths.
Version and project gate
Inspect conf.lua and main.lua, LÖVE and Lua/LuaJIT versions, callback definitions, modules, filesystem identity, graphics/audio APIs, .love packaging and native extension dependencies. Distinguish color/API conventions across major releases. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Set and preserve the game identity and distinguish archive/source reads from writable save storage. Serialize validated data with schema versions and stable IDs. Do not evaluate a save as arbitrary Lua code. Preserve the previous valid save when replacement or migration fails.
Deliver
A save/path contract and safe load/recovery implementation. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Packaged game content is not the normal writable save directory; changing identity can appear to lose progress.
Acceptance scenario
Load an older or malformed copied save, run from a .love archive and confirm saves use the intended identity path. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Lilt. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md