-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unique Mapper Mode for RMC / RMS #131
Comments
Thank you for the reply @GreepTheSheep, however my suggestion was different, I probably didn't explain it too well: The idea would not be to filter authors in general but prevent repetition within a run. This also requires tracking of a list during a run. Example: You start a run, let's say RMC, in the beginning the list is empty. Now you play a Yannex map and beat it, Yannex is added to the list for this run and the next time the API fetches a map with Yannex as author it skips and moves to the next map. This way every map you play WITHIN ONE RUN has a different mapper. This could be an interesting alternative because it shows a broader variety of mappers. However, this requires tracking of state (the list). UI-Wise this would then be represented with a checkmark (prevent mapper repetition) and could be used for both RMS and RMC. Quickly browsing through the code I saw that a related option was already partially implemented (prevent single maps from repeating). I guess that this could also be another checkmark, as soon as the history is tracked both modes basically come for free. |
Ah I understand well. We'll try to implement this, at the moment this will not be our main focus but we'll let in our to-do |
Currently, few mappers dominate the map pool heavily, which in itself is not an issue. However, it could be an interesting variation of the commonly played challenges to avoid repetition of a mapper during a specific RMS/RMT/RMC run. This variation would result in a broader variety of maps being played and maybe present a nice alternative.
This would require keeping track of already played mappers and using the current implementation it might lead to significant slowdown since many randomly fetched maps might belong to mappers that were already played in the current run.
UI wise this could easily be implemented as a checkbox under "Advanced Settings".
The text was updated successfully, but these errors were encountered: