• hh:mm:ss clock variable from engine showing time elapsed since the session started (perhaps best handled as an event, so it's updated in real-time?). I'd suggest a separate variable for each component (eg elapsedHours, elapsedMinutes, elapsedSeconds).

• This can then be used to control various time-based occurrences in the game ... Such as moving to the next season or stage in the day/night cycle by comparing it to a duration set in session creation.

• Or maybe implement it using a ProgressTimer? set to update each game second? (Would still have to calculate the difference on the fly.)

• Initial settings and all input is recorded.

• These same inputs can be fed back into the game at a later date so that the player can view it as a replay.

• User cannot affect what happens, but can view it (alter playback speed, look at play from any players' POV, etc).

• Needs a JS Interface. Should probably start and stop recording synchronized with CGame somehow. Needs a file format (pipe network packets to a file). Needs an entry point for replay (could do something wicked with CMessagePipe and the polling framework already in place for sockets, perhaps). ​http://www.wildfiregames.com/forum/index.php?showtopic=1665

• Also would need a Game Replay user interface to handle special features (selecting control of a different player, adjusting the rate of playback, rewind, etc) as well as select a replay to load (variation of Load Game screen).

Related tickets: #3168 Lets observer change perspective #3253 Save playernames to commands.txt #3255 Update directory structure to prevent overwrites #3258 Main menu entry to start replays #3261 Session panel (pause / fast forward / rewind) #3309 Fast forwarding replays doesn't work as expected #3387 Access summary screen from replays

Debug features requested by QA dept:

• Record to video

• Record to image every x seconds

• Server-side component that retrieves emailed bug reports and posts them to the bug tracker.