XMLGameEngine is a VGDL (video game description language) and an engine for running games completely contained within an XML file.
Status: Built: groups with members, columns and rows, groups inside a group, maps, and cell maps for grid puzzles. <grid> was folded into <group> and removed. Reference: objects, maps.
<group> beside <object>, with one rule: whatever a member leaves out it takes from its group. Then it must be complete like an object. Position and velocity can come in halves (the group gives <y>, each member <x>).groupName. The group’s name means every member wherever a name is taken.| Option | Verdict |
|---|---|
| One group, members override what differs | Chosen: one rule |
| Group position as an origin | Reads worse, hides off-screen starts |
| Reusable named templates | A different idea (opt-in parts; later the kit) |
| Members overriding collisions or actions | Not allowed |
<grid> made identical cells; a group listed members. Breakout was six groups, each a whole grid, to change one colour.<columns>, <rows> and <padding> instead of members (bricks.5.3: column, then row). <row number>, <column number> and <cell row column> change what they pick, from the general to the particular. Breakout’s bricks went from 104 lines to 29.number="2" picks one; several are a <number> each; <odd />, <even />.<rectangle><color>color.orange</color></rectangle>); another shape must be complete. This partial-sprite merge is what later made nesting possible.<padding>, not <x><inc>3</inc></x>: a verb inside a value would break the format’s one rule.<cell> beats both.drawOnce).<wrap />.logrow3.2), and every enclosing group’s name means them too (outerGroups). Lockstep blocks are the innermost groups.innerGroupType differs only in allowing partial sprites.Member and changes it, so the C++ reads like the file.<heading> may be given by a group, so Combat’s two tanks are one group.<map>, rows of characters. Pieces pick their character with char=; a group gets a member on every tile of it, an object takes the one tile it is on. Any character can be any piece.maze.dots.17), so two maps can each have walls; the group’s own name still means all of them.RawMap, tilesOf, placeOnMap), so a generated game lays a map out the same.The grid puzzles (Tetris, Columns, Snake, Centipede, Capsules) needed pieces that move a cell at a time, turn, settle, and a playfield that answers questions (“is this row full”).
<map> rather than a new <grid>: a map is already a grid with tile size and position, and Pac-Man’s walkers already ask whether the next tile is a wall. A map gains <columns>/<rows>, a <cells /> switch, <checks>, spawning into a cell, live column/row. Code: game/cells.cpp.<spawn> with <column>/<row>; <random /> picks a member.<shape> is rows of characters; each character is the map’s piece, so colour comes from the blocks. The shape is an undrawn holder; its cells stay when it <settle />s.<full> rows bottom up with <clear />/<collapse />; <line> of alike pieces, all at once and asked again until nothing goes (the chain); <fall /> is gravity per column. Alike is a group, not a look, since a look can change.<send object from into> and <spawn into>. A piece away from its home map is only shown, so the file needs no word for “this one is not played”.<go> on cells, <chain object> (links drawn in the rows, kept as a list), <grow />, <spawn><free />. Eating needed no word: a refused step whose touch removes the blocker goes on.<split /> cuts a chain and the link behind becomes a head. Turning is a refused step whose rules <reverse /> and hop down. <through /> makes a refused step anyway, sharing the cell, so heads are never stuck. The player’s zone is a row of undrawn pieces.<joins> gives a look by where the other half lies; <line><straight /><alike variable="hue" /> matches across classes; <fall class="pill" /> lets only halves fall.