From 14a730458ece9f1e8ea96eeeb9834f3cb7a3c849 Mon Sep 17 00:00:00 2001 From: Duncan Date: Sat, 18 Apr 2020 07:46:59 +0100 Subject: [PATCH] Updated Replay System (markdown) --- Replay-System.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Replay-System.md b/Replay-System.md index 5e1361e..f89070d 100644 --- a/Replay-System.md +++ b/Replay-System.md @@ -32,4 +32,7 @@ This is practical for the tests to remove all unnecessary gaps between the comma ``` replay_normalise ``` -You can use the same output_file as input_file to overwrite the input. This process can be also used to correct pre-existing replays that will have a different sprite checksum due to game changes, running normalise on a replay will always create up to date checksums. \ No newline at end of file +You can use the same output_file as input_file to overwrite the input. This process can be also used to correct pre-existing replays that will have a different sprite checksum due to game changes, running normalise on a replay will always create up to date checksums. + +# CI Tests +All pull requests are tested by running a number of replays against the new build. They will fail if the sprite checksum differs. This can happen during logic changes. To fix a failing test you will need to rerecord it by using the `replay_normalise` command. If the replay that has failed in bpb1000Ticks then you will need to rerecord using `replay_startrecord bpb1000Ticks 1000` with the bpb save open (bpb is available in the test data folder). To help work out what has caused the failure replay desync logs are generated when playing a replay. Check the desync folder for the report after playing a replay. \ No newline at end of file