This repository has been archived by the owner on Sep 16, 2024. It is now read-only.
Replay now uses Botplay to simulate previous sessions #440
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Did a video about it that would explain quite a lot but, 200mb is too much for Github so here we go.
Replays will now save notes hit in the .kadeReplay file to reuse them while the replay is playing to tell which notes to hit and which notes to let go. The notes that are let go will be counted as a miss automatically (calling noteMiss is overkill, trust me).
It will also now save scroll speed and note direction (/\scroll or /scroll). That's about it.
Also, gotta make sure to warn people that this isn't retroactive, so old .kadeReplay files won't work with this new version.
There are problems though, for some reason, some replays might fail to play properly because the amount of health lost might vary due to the logic used in BotPlay, but I didn't see that happening enough to become a real problem.
Other than that, it's working now.