Scripts opened by a scenario remain locked after scenario error exit
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 869
- Forks
- 222
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 1
Description
Reported by @hemmond in Discord: If a scenario fails to load due to an error, and that scenario opens other script files via require(), the required files aren't closed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing scenario loading and Lua require() handling, focusing on the error-exit path after a scenario opens other script files. Reproduce a scenario load failure that requires another script, then verify that all opened scripts are closed when loading aborts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100