Description
Since marbles will eventually be used by both the client and editor, and needs to be updated before rendering, we could do with a manager that keeps track of all marbles in the scene that updates/interpolates them based on input by the client (networking) or editor (physics). Lots of the final design is still subject to change.
This will also remove the marble update code from the renderer.
Minimum Acceptance Criteria
[x] A MarbleManager module that should exist in src/client/
[x] Should have functions to add/remove a single marble, remove all marbles.
[ ] Should have an interpolate marbles function for the renderer to use.
[x] Should have an entry point to update marble transform data for the networking/physics to use.
Description Since marbles will eventually be used by both the client and editor, and needs to be updated before rendering, we could do with a manager that keeps track of all marbles in the scene that updates/interpolates them based on input by the client (networking) or editor (physics). Lots of the final design is still subject to change. This will also remove the marble update code from the renderer.
Minimum Acceptance Criteria
MarbleManager
module that should exist insrc/client/
Is blocked by the following issues Blocked by #69