-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Number Ranking Criteria rules #3289
Comments
not sure what you mean by this, add the symbols where? |
Add them before each rule/guideline as a reference point. § 3.1 Hit objects must never be off-screen in 4:3 aspect ratios. |
Does this symbol have some special meaning? I'm not immediately sure how it improves organisation. |
I think the important part of this proposal is the numbering, not the section symbol (not sure that's the correct way to use it) for referencing i see what u mean bc it's easier to say "RC rule 3.1" instead of a potentially long rule with many exceptions etc... but at the same time, I've personally only seen RC references in places where the explanation of the rule was necessary, like mod discussions for navigation i dont see how this would help or change anything |
The symbol seemed like a good idea to my sleep deprived brain but the numbering is the important part since it allows referencing rules. This would allow me to write articles for each rule/guideline explaining things such as:
If I were to try and write rule articles atm, referencing them would be impossible |
post to RC forum if you want to see this go anywhere, there are a lot more mappers/modders watching that forum than here |
Going to close for now since ranking criteria stuff shouldn't go here |
This would make referencing the Ranking Criteria easier and allow for expansion of each rule/guideline into its own article
This would be a first step to making the Ranking Criteria more accessible as per #3143
I've planned to take the lead in this and see that it gets done but would appreciate opinions and discussion on how exactly this should be implemented
The text was updated successfully, but these errors were encountered: