XMLGameEngine is a VGDL (video game description language) and an engine for running games completely contained within an XML file.
Status: Built, the mouse and pads too. Reference: input.
<action name="up">); a state binds a key to that name (<input button="w"><trigger object="paddle1" action="up" />); the key is only a label.<move>s record each direction’s step and the velocity is worked out from all four on every key change, so Down held and Up tapped cancel and two keys make a diagonal. Replaced last-key-wins.<keys> set holds inputs; a state takes them (a <keys> each, not keys="a b"), its own inputs going over them key by key.<fire> with none free, a hop in the air, <leap> off the ground). Each verb already knew; it now says so. Commands before it still run, which Berserk’s <aim> before <fire> needs. The same holds in rules, keys and conditions; later rules still run.<try><then> wrapper (the same order in more tags).| Option | Behaviour |
|---|---|
| Latched to the press | Hold Left through pause and the paddle moves on the pause screen. Built first, replaced |
| Live held keys | The current state decides what a held key means. On a change the old bindings are let go and the new state’s held verbs resume for keys still down. One-shots and state changes need a real press |
| Cancel on change | Press again after every pause. Simple but annoying |
Built by a state change count compared in Engine::syncHeldKeysToState() after each key event and frame.
on="press|hold|release" (press if left out, so no game changed), rather than a <charge> verb; a charge is hold, <inc> and <smallest>. release as a value does not clash with the <release> command, and a <demo> already writes a let-go key as <release>.hold and release answer only a press made in the current state, or Space held from the title would charge and strike.mouse.left, pad1.a), so binding, held keys and sets all apply. A pad’s d-pad and stick past halfway are the same four directions.Window::controls() diffed in Engine::handleControls), one place for the rules instead of five event loops.axis= binding plus <track />: the Atari paddle is a position, not a direction. <track path> follows a path’s legs. Rejected: a velocity from a stick, a range on <track>.test_engine_input.