XMLGameEngine

XMLGameEngine is a VGDL (video game description language) and an engine for running games completely contained within an XML file.

View the Project on GitHub beefviper/XMLGameEngine

Design index

These files record why: what we looked for, what we looked at, what we chose, and what is still only an idea. How the engine works today is the reference; when the two disagree, the code and the reference win and the design file should be fixed.

Status words: Built is in the code. Decided is chosen, not built. Open is undecided. Idea is floated, not adopted. Each file is one topic: scan the table and open only the one you need. The backlog is open-work.

Language

File Topic Status
vision What we want; declarative with triggers; the VGDL landscape Built
file-format Why XML; attributes name, content computes; commands in groups Built
arithmetic Text arithmetic and <formula> Built
values-and-names <random>, values read when used, evaluation order, variables, names Built; anchors Idea
objects What an object is, storage, layered values, lockstep Built
groups Groups, columns and rows, groups inside a group, maps, cells for grid puzzles Built
states-and-conditions The stack, from=, conditions, keeps, best tables, turns, demos Built
input Actions, refused presses, held keys, key moments, mouse and pads Built
timers Timers, look timers, time left Built
pools-and-enemies Spawn and despawn, enemies firing back Built
vocabulary-map How the words fit together, and what kinds are missing Map
scenes Scenes inside a state, ways, what conditions count Built
kit The kit, from= and the one change rule Built

Behaviour

File Topic Status
collisions Detection, sweeps, pixels, riding and carrying, contacts, knocks, bounce by the normal Built
collisions-open Weaknesses, response alternatives Open
motion The verb principle, gravity, thrust, headings, hops, pulls, altitude Built
platforming Standing, leaping, ladders, arc and grip Built; air control Idea
chase-and-paths Chasing, aiming, mazes, paths, computer players Built; curves Idea
tables-and-tracks Mini golf, artillery, pinball, racing Built
board-games Moves, the picker, puts, <think> Built; action lookahead Open
cards Decks, piles, hands, patterns, tricks, melds Built; single cards Open

Pictures and sound

File Topic Status
pictures One bitmap path; lines, polygons, bitmaps, SVG, turning, holes, light Built
animation-and-looks Animation, looks, poses, mirror, blinking Built
text Text, fonts, styles, <choose> Built
sound Notes made into samples, loops, music Built

Generating, engine, tools, games

File Topic Status
generator XSLT writes the game as the engine’s data Built; readable output Open
backends Interfaces and factories, scale, the library Built
build-and-layout CMake, output, folders, pipeline Built
cli, gui xgecli; xgegui Built
games-classic What each early game forced Built
games-written-by-ai Three games from the schema alone Built
games-atari The 2600 list and after Built
ideas Scrolling, target profiles, state export, game ideas Idea
open-work Backlog and what is untested Open

Keeping these files