Skip to content
Braedon edited this page Dec 8, 2016 · 4 revisions

For testing purposes it can be useful to have a savegame to refer to. For example, to test the pathfinding system it can be useful to produce a maze map, and to make test reproducible the same maze should be used each time (ref). This is a place to collect any savegames you want to share for testing.

For each entry please include:

  • your name on Github,
  • a link to the save (probably best to use a gist),
  • the date,
  • a reference to the version of the game you used to make your save (e.g. either a SHA1 hash of a commit on master, commit number on master, or a link to a commit on your own fork),
  • links to any relevant issues / pull requests,
  • and a brief description.

Tracking the game version used is necessary because the game is still in a phase of rapid development which may unfortunately break savegame formats.

Example:

Save to test broken save/load code

  • Author: @mikejbrown
  • Save file: https://gist.github.com/mikejbrown/4539f2730471fd106f124571c24f108d
  • Date: 26 Aug 2016
  • Game version: ed1475df (I think -- unfortunately I did not record this at the time. Do as I say, not as I do!)
  • Relevant issues/PRs: #813
  • Description: There was a report of an exception thrown on saving. I made this save to show that saving works, but loading doesn't. Using the save others were able to find errors in the xml handling code and eventually fix the bug (see the PR).

StressTest, testing handling large amount of animating furniture (or any test that needs lots of fast updating furniture)