So, uh, over the last two days I was reviewing skinning things a bit more and noticed some parts that probably should be updated?
Therefore, this thread is for multiple skin related ranking criteria things! Let's go go~
Ordered by what I think is most to least important
The wiki kinda sucks. You have this maaasssive set list to look through to check things, and if we were to include images of the elements in the set list itself it'd end up a bloated mess.
That's why I've made this!
.rar file link!
This rar file includes all elements mentioned on the skin set list. The files are divided into their sets, and optional elements are inside subfolders in those set folders. Also, due to how beatmap skinning only uses the old anchor positions for life bars, the old version elements are what are included as the template images.
I believe it would be very beneficial to somehow include a link to this .rar on the skin set list page. That way, if someone wants to, they can have some form of visual reference.
Why I strongly believe this would be a good thing:
Instead of manually looking through a list for a set, just copy the elements from the beatmap skinning templates .rar to start off your beatmap skin.
Have a visual reference instead of staring at a bunch of text
Gives you an option of a different way to look at sets.
I've found that this folder set I've made for myself has made checking maps with skins in them much much easier.
Of course, you'd still need to read the skin set list to see any notes, but this should still help a lot! I think!
Note: yes, i know the wiki can't host rar files, it could be uploaded to mediafire or something like beatmap packs are
This note should be removed:
The note on star2.png , which is in the Playfield set.
Its note currently states "must not be skinned in beatmapsets which have neither kiai time nor breaks" . This is misleading and a bit wrong, because even in maps which have no kiai time or breaks, the star2.png image is still used during combobursts.
Misc wording fixes..
The lines involving "on the Ranking Criteria Proposal." should be changed to "in the General Ranking Criteria". The proposal they are referring to was already implemented.
"presented in the draft" in the third quote could be removed entirely
->
The following tables contain all skin sets that were worked out by the skinning subdivision of the UBKRC-Project (name credits go to Ephemeral).
the current rule in the general RC says this:
This does not really account for unused files
Example 1: If you skin the default numbers, used in hitobjects for standard, you have to skin numbers 0-9. But, if you never have a combo more than 7, that means 8,9, and 0 would be unused.
Example 2: Forcing skinning of slider elements in taiko. If the taiko map never uses sliders, these would be unused files.
Proposal:
Add +
However, if a required skin element in a set would be unused, do not include it.
after the current big paragraph.
I don't know if that's the best way to fix it but it certainly should be addressed.
It should be mentioned on the skin set list page itself that when a filename has (-n) in it, this means it is animateable. Like hitcircleoverlay can either be hitcircleoverlay.png or hitcircleoverlay-0.png and it may count upwards to animate it. Why do I say this? I've seen a map where someone literally put the filename as (-n) and they couldn't figure out why it wasn't working...
Proposal:
If a filename contains `(-n)`, this means it can be animated. For example, hitcircleoverlay(-n).png means it can be named either hitcircleoverlay.png or hitcircleoverlay-0.png. It may count up from 0 with multiple images to animate the element.
I figure this could be positioned like so:
Thanks for reading 🌻
Therefore, this thread is for multiple skin related ranking criteria things! Let's go go~
Ordered by what I think is most to least important
Part 1: Make Life Easier.
tl;dr: Add a template to the skin set list!The wiki kinda sucks. You have this maaasssive set list to look through to check things, and if we were to include images of the elements in the set list itself it'd end up a bloated mess.
That's why I've made this!
.rar file link!
This rar file includes all elements mentioned on the skin set list. The files are divided into their sets, and optional elements are inside subfolders in those set folders. Also, due to how beatmap skinning only uses the old anchor positions for life bars, the old version elements are what are included as the template images.
I believe it would be very beneficial to somehow include a link to this .rar on the skin set list page. That way, if someone wants to, they can have some form of visual reference.
Why I strongly believe this would be a good thing:
Instead of manually looking through a list for a set, just copy the elements from the beatmap skinning templates .rar to start off your beatmap skin.
Have a visual reference instead of staring at a bunch of text
Gives you an option of a different way to look at sets.
I've found that this folder set I've made for myself has made checking maps with skins in them much much easier.
Of course, you'd still need to read the skin set list to see any notes, but this should still help a lot! I think!
Note: yes, i know the wiki can't host rar files, it could be uploaded to mediafire or something like beatmap packs are
Part 2, updating the skin set list page some more (while we're at it):
tl;dr: fixes not changesThis note should be removed:
The note on star2.png , which is in the Playfield set.
Its note currently states "must not be skinned in beatmapsets which have neither kiai time nor breaks" . This is misleading and a bit wrong, because even in maps which have no kiai time or breaks, the star2.png image is still used during combobursts.
Misc wording fixes..
The entirety of this skin set is gameplay relevant. Overlaps or gaps between the numbers themselves are set by the user-specific skin and cannot be influenced within the beatmap itself. Please note that the recommended sizes for all elements in this set is handled via a guideline on the Ranking Criteria Proposal.
The entirety of this skin set is gameplay relevant. Please note that the sizes of the elements within this skin set are handled via a guideline on the Ranking Criteria proposal.
The following tables contain all skin sets that are presented in the draft worked out by the skinning subdivision of the UBKRC-Project (name credits go to Ephemeral).These refer to the proposal/draft, even though it's already been implemented as the RC.
The lines involving "on the Ranking Criteria Proposal." should be changed to "in the General Ranking Criteria". The proposal they are referring to was already implemented.
"presented in the draft" in the third quote could be removed entirely
->
The following tables contain all skin sets that were worked out by the skinning subdivision of the UBKRC-Project (name credits go to Ephemeral).
Part 3, the main rule itself:
tl;dr: Unused files stuffthe current rule in the general RC says this:
When skinning gameplay elements, complete sets of elements need to be skinned in order to avoid conflicts between user-specific and beatmap-specific skins. A reference for this can be found on the Skin Set List. When skinning an element that is marked as optional, you need to include all the required elements of the respective set, but you are free to skip other optional elements unless they are grouped with the element you are skinning.
This does not really account for unused files
Example 1: If you skin the default numbers, used in hitobjects for standard, you have to skin numbers 0-9. But, if you never have a combo more than 7, that means 8,9, and 0 would be unused.
Example 2: Forcing skinning of slider elements in taiko. If the taiko map never uses sliders, these would be unused files.
Proposal:
Add +
However, if a required skin element in a set would be unused, do not include it.
after the current big paragraph.
I don't know if that's the best way to fix it but it certainly should be addressed.
Part 4, some clarification:
tl;dr: (-n) needs explanationIt should be mentioned on the skin set list page itself that when a filename has (-n) in it, this means it is animateable. Like hitcircleoverlay can either be hitcircleoverlay.png or hitcircleoverlay-0.png and it may count upwards to animate it. Why do I say this? I've seen a map where someone literally put the filename as (-n) and they couldn't figure out why it wasn't working...
Proposal:
If a filename contains `(-n)`, this means it can be animated. For example, hitcircleoverlay(-n).png means it can be named either hitcircleoverlay.png or hitcircleoverlay-0.png. It may count up from 0 with multiple images to animate the element.
I figure this could be positioned like so:
Thanks for reading 🌻
