Quenty / Quenty/NevermoreEngine
Modules are randomly not recognised on the client in 'deferred' signal mode
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 610
- Forks
- 144
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
Description
In studio/accurate play solo some modules are randomly not registered on the client by Nevermore's loader. It seems to happen randomly, and only in deferred signal mode.
Which modules aren't recognised is totally random, and can affect Client + Shared modules. It seems like deferred mode has some impact on instance replication? Children are no longer replicated at the exact same time as _replicationFolder, so it doesn't ever get cached?
I think this can be fixed by adding .DescendantAdded in the right place?
Repro:
- Press F5 / Play in studio.
- Check for missing modules in the console.
- Repeatedly play+stop the game until an error appears. For me, it appears around 40% of the time.
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 by reproducing the issue in Roblox Studio with F5 in deferred signal mode, then inspect Nevermore's module loader and how it caches _replicationFolder children. Repeat play and stop until missing modules appear in the console; done means client and shared modules are consistently recognised during deferred-mode startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100