XMLGameEngine is a VGDL (video game description language) and an engine for running games completely contained within an XML file.
Status: Built.
<group> of hidden members was a pool that <fire>, <release>, <reveal> and <spawn> took from, and its size capped how many were out.<member /> lines or <columns>, its size is a guess, a fired shot keeps its old state, and an unlimited count cannot be said.<template>, <inplay>, <exists>. Chosen: spawn/despawn and <exists>, since what a rule cares about is whether something exists.<exists>false</exists> made an object (or a group) a description: in the file, never in the game. Its position may be left out. A description is now a piece of the game’s <kit> that a spawn names, and <exists> is gone from the file (kit); the engine still marks the piece it puts in beside the spawner as not existing.<spawn>, <fire> and <release> of a description (now a kit piece) make a new copy, named name.N with the lowest free N; a group’s members are copied in turn. A copy’s <random>s are drawn for it, its variables and timers are its own, and its own name and self in its rules mean the copy. <spawn> of an object that exists copies it too.<most> caps how many copies exist at once; at the cap the verb is refused (and the rest of the press, as for any refused verb).<despawn /> takes a copy away for good (its name free again) and puts one the file wrote out until a reset.std::vector; copies made during a frame wait in a std::deque and join when the frame ends, and despawned copies are erased then, so nothing a frame is iterating moves under it. Caches keyed by position or pointer (names found, live numbers, collision partners, run-in-top) are rebuilt when the list changes. The vector reserves room at load so references to loaded objects stay good.<despawn object>); a copy’s own name can be written too (abm.1), found by what it copies, so a tether can join a copy that comes and goes.<member /> lines and the comments explaining pools.<reveal>: Frostbite’s igloo, a door, Atlantis’ and Air-Sea Battle’s planes). Show/hide as verbs were an earlier idea; <reveal> and <die /> are that pair.<most>-less descriptions that pile up grow them). The collision partner table is rebuilt for every list change, O(n²) in objects; fine at these sizes, worth a measure if a game spawns every frame.<fire>: an enemy is a shooter with a facing and a timer; its shots are copies of a piece of the kit. No aiming. Space Invaders (both) and Demon Attack fire this way (Berserk’s robots now <aim> first); the aliens’ catch-all rule (<collision><die /></collision>) had to name the cannon’s bullet so their own bombs do not kill them.Only the front invader of a column firing, an event queue, mutable game-wide variables (object variables did the job in every game), timers whose numbers follow variables beyond the interval.