search

GreepTheSheep / openplanet-MXRandom

An Openplanet plugin that takes a random map from MX / TMX and play it
https://openplanet.dev/plugin/mxrandom
GNU General Public License v3.0
20 stars 29 forks source link

Unique Mapper Mode for RMC / RMS #131

Open phspo opened 1 month ago

phspo commented 1 month ago

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".

GreepTheSheep commented 6 days ago

You can use searching parameters with possibility to have those parameters enabled for RMC, it also enables for RMS and all other modes

image

phspo commented 5 days ago

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.

GreepTheSheep commented 5 days ago

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