1. -> It shows you ALL rules and guidelines ALL the time even if they're not relevant to your map. Compare this to programs like mapset verifier or aimod which only show you points your map is currently breaking or is at risk of breaking.
   
   Like why would you care about a giant storyboard section if your map has no storyboard? Why care about skinning if you have no skin? Why care about metadata (TV Size) standardization if you're mapping a full length English pop song?
2. -> With the community growing over the years, a lot of things that used to be "commonly understood" became more obscure with more new people coming in that didn't know those "common sense" rules yet, so more and more of the common understanding for the basic tenets of what we expect from every map had to be written down to keep it accessible and relatively easy to learn.

1. From my knowledge many of the features of mapset verifier will be built into lazer, so right now we're in a bit of a limbo where it's not in-game but is very helpful in showing you only what you need to know and check for your map. Something in-game to help direct you to getting the program when you upload your map could be very helpful.
2. Break RC into more sub pages, so people can just check the pages they care about. Just General, Beatmap, Audio, Timing should be kept on the main page as they ALWAYS apply to ALL maps.
3. Use the breathing room this gives to add images, graphs etc when needed. Many people are visual learners and a wall of text can be a huge turn off. For example, an image would be really helpful to glance at instead of having to read all of the bullet points for how spread requirements scale based off of beatmap length.

Noffy wrote:

Break RC into more sub pages, so people can just check the pages they care about. Just General, Beatmap, Audio, Timing should be kept on the main page as they ALWAYS apply to ALL maps.

eiri- wrote:

PLEASE break up the rc into sub pages it is so long and unnecessarily confusing to new people and foreigners as the massive amount of text is just a lot to sift through to find the handful of things that one may actually need

yaspo wrote:

I think subpages would be cool, beyond using images it also allows us to codify certain goals/ideas/whatevers that are associated with certain sections eg. describe the general principles behind metadata and not just the specific rules. Same idea, more space = more different kinds of content

Noffy wrote:

[...] add images, graphs etc when needed. Many people are visual learners and a wall of text can be a huge turn off. For example, an image would be really helpful to glance at instead of having to read all of the bullet points for how spread requirements scale based off of beatmap length.

clayton wrote:

was there another discussion involving "page length" or somethn, this seems like a really random non-problem to bring up among the others

yaspo wrote:

Otherwise the second point invalidates the first so lol ?, the RC is indeed split up clearly enough to work with subpages

Noffy wrote:

clayton wrote:

was there another discussion involving "page length" or somethn, this seems like a really random non-problem to bring up among the others

not really page length specifically, but it being hard to approach and difficult to parse, my op is just my perspective on how that could be addressed but we can look at other methods too.

Nao Tomori wrote:

tbt to loctav randomly saying "rc isnt a picture book" and banning images