XMLGameEngine is a VGDL (video game description language) and an engine for running games completely contained within an XML file.
Status: Built, including states from= others. Open: object-level conditions, copying a state with scenes, taking things out of a copy. Reference: states and scenes.
A state is a mode: menu, play, pause, game over. It says what is shown, which keys run which commands, which conditions to watch, and its own timers.
<push>/<pop>; pause pushes paused and Space pops it. A bare <reset /> from a state collapses the stack to the first state, so menu, play, game over, menu does not grow it.<pop state="x" /> replaces the current state (“this one goes, that one takes its place”). Chosen over a <goto> verb or <reset to=>: no new verb, and it reads as what happens.<shows>, <keys> and <conditions> sets at the top of <states>, one set per tag, since sets="a b" would be a list in a string. Since states own their objects few games use show sets.from=: 17 games had win and lose screens differing in one text. The same word and change rule as scenes and the kit: keys replace by key, conditions and timers by name. Done in shared C++ (takeStates). Rejected: one end state revealing one of several texts (needs a hide verb).<become>s it before pushing. Numbers go by path. Shelved: a reserved name for the object that triggered it (a name whose meaning changes while running).if.<atleast>, <atmost>, <above>, <below>, <equal>, <remaining>. <atmost> because a variable can skip zero; <above> is strict since a tie is a third outcome.<above>gun2.score</above>, Condition::live). It replaced object=/variable= on the test tag, which read ambiguously.<all> and <any> of <condition>s, nesting, one test each, since the tests of a real “and” are about different things. Rejected: and=/or= chains, <not> (each test has its opposite).total= (count, sum, highest, lowest) makes one number over everything matched, so “at least three bullets in flight” needs nothing new.distance= measures to the nearest of a name; with total="lowest", “nothing near” is one test (Asteroids’ respawn).<condition>: the test inside <all>, <any> and a rule was once <check>; the schema gives one word two shapes by where it stands.<keeps> lists objects a full reset passes over; <copy variable into> sets one variable from another. Taken “for now”; rejected a flag on each object (scatters what survives a reset).<content>, <number> and <letter> parts (initials are three numbers); a group’s text naming the group’s variable means each member’s; <rank variable into> takes the first place it beats. A tie goes below, as on the arcade machines.saves/<game>.xml when a new game starts and on close, read a line at a time without an XML library (a generated program has none). Nothing in the game file asks for it.<demo> is a seed, a length and key changes. Rejected: a scripted computer player, replaying positions.<random>s, noticing an older recording.