[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR aims to lay a foundation for for implementing physics engines as plugin providers by laying the groundwork for API's that should universally be available to allow for an implementation agnostic interaction with physics.
Is there an open issue that this resolves? If so, please link it here.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR aims to lay a foundation for for implementing physics engines as plugin providers by laying the groundwork for API's that should universally be available to allow for an implementation agnostic interaction with physics.
Is there an open issue that this resolves? If so, please link it here.
https://github.com/novelrt/NovelRT/issues/559
What is the current behavior? (You can also link to an open issue here)
https://github.com/novelrt/NovelRT/issues/559
What is the new behavior (if this is a feature change)?
There will be a plugin interface that can be implemented by physics engine plugins.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
There should be no breaking changes introduced in this PR
Other information: