https://wiki.qeng.org/ 2026-10-30T11:39:51+0000 https://wiki.qeng.org/ https://wiki.qeng.org/lib/tpl/bootstrap3/images/favicon.ico text/html 2026-09-18T06:51:04+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.qeng.org/doku.php?id=en:authors_main:lifecycle:running_and_closing&rev=1789714264&do=diff Running and Closing a Game While a game is on, the engine runs by itself: levels are handed out, codes are accepted, hints open on time, auto-transitions fire. No manual action is required after the start. Everything you can step in with, though, sits in one place — in the black admin block above the table on the text/html 2026-09-18T06:51:04+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.qeng.org/doku.php?id=en:authors_main:lifecycle:testing&rev=1789714264&do=diff Testing a Game Before launching a game for actual players, it is extremely important to make sure that all tasks are displayed correctly, codes are accepted without failures, and hints arrive on time. 1. Quick Testing by the Author (Single Test) Any author can test the game in one click, straight from the