| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is seems like it creats even more chaotic binding between the
components but it is a very nice and testable intermediate step
before moving everything to standalone systems and shoving state into
the... well, State.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This whole ongoing refactoring process is meant to better understand
relationships between Battle, Simulation and Systems.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This should have been added earlier. The test itself is questionable
and overall very optimistic about the edge cases. The intent of this
commit is purely set up of the testing framework.
|
|
|
|
|
|
|
|
|
|
We do not control this code so the warnings may only potentially hide
our own problems in logs.
|
|
|
|
|
|
This might be a bit too generic of a name, but the intent is to get the
main shared abstracts for gameplay loop and/or simulation outside of
the game executable implementation to redirect dependencies.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
