Real-time scheduler and event engine with string message handling. #969
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skittles1
force-pushed
the
eventscheduler
branch
from
e489455
to
6009f46
Compare
skittles1
force-pushed
the
eventscheduler
branch
from
6009f46
to
73a467d
Compare
skittles1
force-pushed
the
eventscheduler
branch
from
73a467d
to
9166c01
Compare
The workflow is now event ends -> calls @EventEnd in GameEvent -> lets GameEventEngine know the event is finishing -> calls @EndEvent on the GameEvent in addition to any cleanup that needs to be done.
Also moved a couple messages to GameEvent so they can be used by any event.
skittles1
force-pushed
the
eventscheduler
branch
from
04f48dd
to
a4add9a
Compare
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is Keen's real-time scheduler and game event engine with modifications to support calling messages by string. Instead of sending a constant which is interpreted by RealTimeCallback, the actual message (@EventStart, @EventEnd, etc) is sent which means the real-time scheduler can call ANY message in any class (e.g. can schedule @StartQormas, and eventually we can schedule a frenzy this way).
The limitation in this system is that the callback messages are called with generic parameter names (these have to be written in kod in advance) so the called message has to handle parameters as parm1, parm2, ... parm15.
The Register messages in the real-time scheduler object can convert non-string input into strings which are saved to call the message back, so sending temp string, the message itself, or a debug string/quote will all result in a valid string being saved.