forum

about the "do not manually edit .osu file" rule

posted
Total Posts
23
Topic Starter
[CSGA]Ar3sgice
hmm, the problem is, is 3.0x sv rankable? I've seen some people say it's unrankable, some say rankable


this is technically possible to do in the editor, you can change to mania mode, set to 3.0x, and change back to osu! mode

but this way is probably too weird to make it through this rule 0,0
whymeman
As far as I look at it, Slider Velocity is one of those "common sense" things that have to be logical. Just setting it up that high for the sake of doing so wouldn't make sense, especially if doesn't play stable with it at all like... that 1x to 3x jump. It's EXTREME, especially @ 144 BPM. And don't forget that it also changes how distance snap behaves too. There's been some cases where using inherited speed ups in a higher velocity would require some actual math applied to keep it within sanity levels without the hitnote spread being too large or smaller than the ideal seeked.

As for the "do not edit .osu file" thing, the reason for that as I would recall is that unsupported edits and such that could cause a bug or break in the file in the long run. The only time the .osu file should be altered is to fix SB stuff or C/P timing signatures and bookmarks as far as I can see it.
Ayesha Altugle
you used actually 0.4x in one of your map
--------------------------------------------------
with that strat. you can make a hold sliders

Edit 2:
Cygnus
I think this should be in the guidelines though. Some songs really require speed ups more than 2.0 in my opinion. But that's just me. :p
mm201
You know in this example you can double your base SV, change all the x1 sections to x0.5, and change the x3 to x1.5? So you didn't need to hax the .osu file.
Last I checked, haxing .osu files wasn't itself unrankable. Rather, the odd things you may create are what's unrankable.
MillhioreF
[quote="Ranking Criteria":95d86]
  1. Do not manually edit anything in an .osu file that cannot be changed through the Editor. The only exceptions are .osu-specific storyboards and skin-related options such as SliderBorder and SliderTrackOverride.
It's a bit of a silly rule, given how much explanation is required about the exceptions, but it's there. It leaves grey areas for some things, too (like changing video offset in intervals less than 200)
whymeman

vahn10 wrote:

you used actually 0.4x in one of your map

with that strat. you can make a hold sliders
I'm sure hold sliders have been unrankable for a long time now....
Ayesha Altugle

whymeman wrote:

I'm sure hold sliders have been unrankable for a long time now....
yeah :(
Luvdic
I know that some people manually edit slider lengths to make it fit perfectly to timing changes (granted that apparently it is done if the new offset doesn't mess up with weird slider ticks), but yeah, point is that to do this, one have to manually edit the .osu file
Kodora
fun sliders are back? yay.
TheVileOne
I've been skirting around the idea of manually snapping slider ends to red lines by manually editing the .osu. I consider it the lesser of the two evils when the other evil is unsnapping the slider end beyond the red line. I'm not sure what the staff thinks of this. Personally I feel it does no harm, and ziin's map utilizes it.
Kodora
also you again able now to create CS 8 maps w/o editing .osz

cool
D33d
So far, I haven't came across anything that requires hacks. I don't see this rule as being unreasonable, because the editor has enough flexibility to make something that works. For timings and snapped sliderends, a BPM change could be used on a slider to make it fit, which I consider a much easier approach than fiddling with the file, bit by bit.

As for those crazy SV changes, do what mm said and also refrain from doing daft things with SV. I'm willing to bet that certain parts of the map could be given more impetus by changing the patterns alone--speedups aren't entirely necessary, but I don't see why they can't be done tastefully.
TheVileOne
The problem with adding red lines to adjust sliders is that it wil create inconsistent red lines across difficulties, and breaks a rule against using red lines for this purpose.
D33d

TheVileOne wrote:

The problem with adding red lines to adjust sliders is that it wil create inconsistent red lines across difficulties, and breaks a rule against using red lines for this purpose.
Not if the timing's done properly, so that every difficulty has a BPM change in the same place and still allows for the right slider placement. If there's a part in the music where there really needs to be a slider, then I can imagine that the slider could be used in the other difficulties. Of course, omitting the slider or shortening it would skirt the problem completely.
TheVileOne
I don't like this method. changing the BPM changes the slider speed as well. Changing the slider end through the .osu doesn't alter the speed the slider will move. I don't feel like having to double the amount of red lines in my map and having to place specific slider velocity speed changes to keep the slider flow consistent. This also doesn't solve the issue that occurs when the slider start is on the red line for a timing section and it ends on another red line section. If you change the BPM, it will render the sounds between the two red lines unmappable or it will violate a rule that doesn't need to be violated if I modify the .osu.
Kodora
I must say that we already have approved maps with codehacked sliders and they fits & works as well

http://osu.ppy.sh/s/27448
http://osu.ppy.sh/s/29705

dont see any problems with using them now, especially if you can create them w/o editing .osz
They not harm timing, they readable (epic slоw sliders have huge numbers of ticks what makes them very easy to read), people love them. So, whats the problem?
HakuNoKaemi
Wait, we should have another topic about this...
and... well... wasn't that rule deleted O.O?
peppy itself said it was to maintain the code stability and avoid bugs... now osu!'s code is much more stable, and you can manually edit the .osu whenever you want

https://osu.ppy.sh/forum/t/77277/start=15

Nuke on Existant Rule, means the rule should have got deleted
TheVileOne
I forgot about that thread. I guess someone forgot to remove it. The general thoughts from most of the people in this thread have reflected the same reasoning. Anything that can be changed through the editor is allowed unless specifically said otherwise (like stack leniency). It can be removed so people can use different slider velocities, edit slider ends, and whatever else needs to be edited through the .osu.
Kodora
So we still not able to use tick rate 0.5 but able to change speed of sliders?
HakuNoKaemi
you arleady know it from me
yep, you won't be able to do anything that wasn't directly permitted ( Tick Rates <1 and Stack Leniency 0 aren't permitted, so yu can't do them editing the .osu)
Kodora

HakuNoKaemi wrote:

you arleady know it from me
yep, you won't be able to do anything that wasn't directly permitted ( Tick Rates <1 and Stack Leniency 0 aren't permitted, so yu can't do them editing the .osu)
I just was waiting for confirming, thanks for explaining before.
Ephemeral
If provisions are not made within the editor to allow for various map settings, assume they are not rankable.

These can be assessed on a case by case basis and do not need individual justification within the ranking criteria.
Please sign in to reply.

New reply