A beatmap's custom skin must use image files that do not exceed the pixel size of the default skin. The only exceptions to this are score and combo numbers and combo bursts, which should be a maximum of 65x65 and 500x767 respectively. These dimensions are not exact, going over by a few pixels isn't a problem, but as a mapper you should do your best to abide by these limites.

If a beatmap uses a custom skin or forces a default skin, a custom sliderborder should be applied. This is to avoid the default sliderborder or a player's custom skin's sliderborder from conflicting with the map's specific color scheme.

At no time during a storyboard should the load go past 5.0x 4.0x is recommended. Do note that:

• ===The editor and playtesting storyboard loads calculate the resultant load differently: Use the playtesting gauge since it is more accurate.
  ===The storyboard load multiplier is calculated by how large any set of images currently displayed on the playing field compared to the default size - that is to say, to obtain a 5.0x load, you must have the equivalent of five background images stacked at once, regardless of the opacity of each. The basic background image sits at 1.0x.

going over by a few pixels

rules wrote:

If a beatmap uses a custom skin or forces a default skin, a custom sliderborder should be applied. This is to avoid the default sliderborder or a player's custom skin's sliderborder from conflicting with the map's specific color scheme.

ouranhshc wrote:

rules wrote:

If a beatmap uses a custom skin or forces a default skin, a custom sliderborder should be applied. This is to avoid the default sliderborder or a player's custom skin's sliderborder from conflicting with the map's specific color scheme.

is this for prettiness or something. or does this have to do with the future sliders

RandomJibberish wrote:

ouranhshc wrote:

is this for prettiness or something. or does this have to do with the future sliders

It's so that if, for example, you have a custom skin with a black overlay and slider border, it doesn't look awful and inconsistent when a map's skin uses a white overlay.

Shiirn wrote:

At no time during a storyboard should the load go past 5.0x 4.0x is recommended. Do note that:

• ===The editor and playtesting storyboard loads calculate the resultant load differently: Use the playtesting gauge since it is more accurate.
  ===The storyboard load multiplier is calculated by how large any set of images currently displayed on the playing field compared to the default size - that is to say, to obtain a 5.0x load, you must have the equivalent of five background images stacked at once, regardless of the opacity of each. The basic background image sits at 1.0x.

Kitsunemimi wrote:

I have a feeling this is going to fuck up my shit for the storyboard I'm making. Plus, high sb load doesn't always mean epic lag, since scaling small images tends to up the load by a ton, though they don't lag insanely. Cirno's hot spring is a good example of.... upscaled images I think. iirc it goes up to 22x load on a single image.

A beatmap's custom skin must use image files that do not exceed the pixel size of the default skin. The only exceptions to this are score and combo numbers and combo bursts, which should be a maximum of 65x65 and 500x767 respectively. These dimensions are not exact, going over by a few pixels isn't a problem, but as a mapper you should do your best to abide by these limites.

If a beatmap uses a custom skin or forces a default skin, a custom sliderborder should be applied. This is to avoid the default sliderborder or a player's custom skin's sliderborder from conflicting with the map's specific color scheme.