Quenty / Quenty/NevermoreEngine
No error is thrown when the loader finds 2+ packages named the same
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 610
- Forks
- 144
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
Description
When two packages are named the same, one will inevitably be replicated in before the other. The loader will choose the first. This means that seemingly at random, a conflicting package and its modules will fail to load in-game, giving you the typical xxxx not a child of folder error.
While this isn't undesired behaviour, a more descriptive error should be thrown. You normally see this error when you've mistyped a module name, it's easy to misattribute the cause.
This only occurs with .bootstrapGame, affecting both the client and server.
Contributor guide
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 at the .bootstrapGame entry point and reproduce the duplicate-package scenario in both client and server contexts. The work is done when duplicate package names produce a descriptive error that distinguishes the conflict from a mistyped module name.
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