mirrors/OpenRCT2
1
0
Fork 0
mirror of https://github.com/OpenRCT2/OpenRCT2 synced 2025-12-10 09:32:29 +01:00
Code Issues Releases Wiki Activity

Fix spelling mistake, add missing connective word

matheusvb3
2025-08-01 03:20:48 -03:00
parent 3d8a55a16c
commit d8eaedceff
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Replay-System.md

@@ -35,6 +35,6 @@ replay_normalise <input_file> <output_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.
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 is 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.
Unfortunately at this time replays x64 and x86 platforms will generate different sprite checksums. For this reason only x64 builds are checked during the CI tests. All replays in the replays repo have been recorded on x64 platforms.
Unfortunately at this time replays on x64 and x86 platforms will generate different sprite checksums. For this reason only x64 builds are checked during the CI tests. All replays in the replays repo have been recorded on x64 platforms.