Clarify scheduling by tag
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 72
- Forks
- 2
- Avg merge
- 6m
- Merged PRs (30d)
- 4
Description
I had been using this example as how to do a quick game loop with the usual stages:
And then to complicate things I add an update camera system that gets the default tag and a new camera tag. I explicitly schedule it before render but the expectation was that I don't have to. Since moveBody is scheduler before render and it also has the default tag I expect the tag to inherit this requirement
Is that correct?
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 with the scheduler behavior involving the moveBody, render, and update-camera systems, and compare how their default and camera tags are interpreted. Confirm whether scheduling moveBody before render should imply the same ordering for another system with the default tag; document the expected behavior and add a focused example or test if the project provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100