View difference between Paste ID: fqTEinVz and PUdBtrb7

-So, I patch finally hit for console. We all knew this was coming, now it's time to start the discussion about what to do with the leaderboards. So far it's only hit PS4, and the build is the same as the current PC build, 1.03 (where the default build would be 1.0). So here I'm going to be outlaying some options about what to do.
+So, a patch finally hit for console. We all knew this was coming, now it's time to start the discussion about what to do with the leaderboards. So far it's only hit PS4, and the build is the same as the current PC build, 1.03 (where the default build would be 1.0). So here I'm going to be outlaying some options about what to do.
 
 Variable vs Sub-Category:
 
 In the long term, sub-categories for separation on builds will be the go to. But in the short term, that might not be the best option, as we don't exactly know if there will be further patches, in between patches, small patches, patches that impact mechanics, etc. I'll talk more about that in the future, but for now I'll just show what the difference is.
 
-A variable looks like this:
+A variable is like what we have for the consoles. You can see the info on the leaderboard, and choose to filter it as you view, but the default listing is just 'whatever is fastest'. The issue with this long term is that someone playing on a patched version, even if they were to filter the leaderboards, would still have their submission competing with the unpatched version. For example in this picture, the submission would still say "6th" on their personal profile, which isn't particularly accurate for competition on that version.
-<link>
+
-It can be filtered on the leaderboards, but the default listing is just 'whatever is fastest'. The issue with this long term is that someone playing on a patched version, even if they were to filter the leaderboards, would still have their submission competing with the unpatched version. For example in this picture, the submission would still say "6th" on their personal profile, which isn't particularly accurate for competition on that version.
+A Sub-Category is what we already have for "Beat the game" and "All Emeralds". This will be the long term solution. But how to actually handle the sub-categories is something that needs to be discussed. For example, how to distinguish the sub-categories. This for both ILs and full game runs, and choosing an option that works for both simultaneously may prove tricky
 
-A Sub-Category looks like this:
+One option is to simply use the build number, e.g. the sub-categories would be V1.0 and V1.03. The two obvious issues with this option, would be then someone on 1.0 would be excluded from competing without using the glitch. Take for example Alluusio's run for Studiopolis 2, which was done on PS4 on Sept 1st, using build 1.0. However, he did not use, or attempt to use, the glitch that is only available in that build. For all intents and purposes, it should be competing with the runs on build 1.03. You could still name them as such and just submit to the one that applies to you, but that would seem rather confusing to a submitter, and incorrect labelling. The other obvious issue would be if there where multiple builds, it would create a potentially huge amount of sub-categories, separating competition unnecessarily and making the middle builds barren and uncompetitive (and potentially unaccessable in future)
-<link>
+
-This will be the long term solution. But how to actually handle the sub-categories is something that needs to be discussed. For example, how to distinguish the sub-categories. This may more apply for ILs than full game runs, where separation may be more obvious.
+
 
-If you were to just use the build number, then someone on 1.0 would be excluded from competing without using the glitch. Take for example Alluusio's run for Studiopolis 2, which was done on PS4 on Sept 1st, using build 1.0. However, he did not use, or attempt to use, the glitch that is only available in that build. For all intents and purposes, it should be competing with the runs on build 1.03. You could still name them as such and just submit to the one that applies to you, but that would seem rather confusing to a submitter, and incorrect labeling.
+
 
 The issues with this are this would mean for full game runs, if a build was made beyond 1.03 then all 1.03 runs would be grouped together with 1.0 runs, at a disadvantage. It also means runs which were allowed in the "Newest Build" may then have to be moved later on to the other sub-category. However I find this preferable to them having their own sub-categories, because a) I don't think anyone will optimise a good run before the last build is released anyway (they won't be patching this in 2020), and b) the competitiveness for an in between build will almost certainly be 0, so it'd just be sitting there as dead weight. The same would apply to ILs under the same unlikely criteria as described above, but I think anyone who is using a bug that ends up getting patched just has to be aware to know that could be happening in the future, as has to suck it up if it does.
 
 Last point on the IL charts, but the "overall board" (This one: https://www.speedrun.com/sonicmania/individual_levels) will only display the default sub-category. I'm amusing the community response based on actions from what I've seen so far is that the majority would prefer the default in that case to be the "Patched" runs. So that for example, that board would display Level_Select's 2'51"77 on Titanic Monarch 2 Sonic, instead of his 48 second time on console, even though both could be submitted under different sub-categories. Either way not everyone will agree no matter what we choose, but I'd like to hear everyone's thoughts so we can make the most people happy.