You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
different timing options (tick, when player presses, etc)
player movement
ACTION
AGAIN
redo a level
support OR tiles on the left (condition) percolating to the right (action) even when in different brackets
play a level and move to the next when win conditions are met
record a level playthrough so it can be replayed as a unit test
support flickscreen setting
support zoomscreen setting (lots of redraws)
detect win conditions
support WINCONDITIONS section
support WIN command in the rules
CANCEL
ellipses [ | ... | ] -> [ | ... | ]
SFX commands
undo
CHECKPOINT
render messages and message levels (screen 34x13 characters)
sprites add on the right side of a Rule should be NO on the left side (be smart though) might only work if 1 sprite is being added. Speeds up evaluation since there will be fewer matches
tsc
errorssemantics.addOperation('parse', {...}
or by assembling the Object arg before passing it in.getMatchedMutatorsOrNull
onto the non-pair class and passing in an additionalcorrespondingActionNode
fieldThen, we can start implementing:
[ > Cat | ^ Dog ] -> ...
)LATE
STARTLOOP
[> cat]
)ACTION
AGAIN
flickscreen
settingzoomscreen
setting (lots of redraws)WINCONDITIONS
sectionWIN
command in the rulesCANCEL
[ | ... | ] -> [ | ... | ]
SFX
commandsCHECKPOINT
NO
on the left side (be smart though) might only work if 1 sprite is being added. Speeds up evaluation since there will be fewer matcheswasd
plays the game and arrow keys inspect the "screen")/cc @jenniferharmon
The text was updated successfully, but these errors were encountered: