I've been lurking around Osu! for quite some time now and recently started to take interest in creating content for the game and ran into a lot of issues while doing so, specifically in the beatmap editor.
Since it's my first post, it may be hard to actually take credit from me but I'll address some things that I have ran into.
First of all, I have to say it's that I think it's awesome that the game actually has a text based code that more advanced users can easily edit for more technical stuff.
My problems are oriented for the standard or more basic user, revising some of the changelog and consulting with other users I concluded that the functionality of the editor hasn't been heavily altered in quite some time and may lack some strong features that may simplify the usage of said program:
TL;DR The sole idea of having a friendly editor and having the files stored as text which can be edited for advanced users is great, but there are some
features that could make the editor much better for newbies and advanced users alike.
Some of the sugerences are:
General:
- Allowing the creation and/or preview of beatmaps skins inside of the editor.
- Allow 'Inherit point' resnapping when the timing is altered.
- Allow to put comments inside the bookmarks.
- Bookmark highlighting for easy navigation. (( Maybe a dedicated optional windows which displays them? ))
- Allow in the editor to loop a certain point in the song while editing for timing testing.
- Undo history.
- More friendly song navigation wich correctly displays all the existing features and luckily some of the suggested ones.
- Autosave function (( Some people aren't just familiar with Ctrl + S ))
Dedicated Editors:
Again, some people may be used to the actual system but I think it would be wonderful if the editors could have a preview of their work like in Osu!Mania and Standard instead of just testing it from certain point.
- Dedicated CTB editor:
- See: ( t/129618 )
- Dedicated Taiko editor:
- The editor basically should allow the preview of the elements as they are in gameplay.
Storyboard Editor:
- Allow the creation of layers for elements which include:
- Layers that can be:
- Locked: To prevent accidental editing.
- Hidden: Self explanatory.
- Grouped: For multi element editing.
- Highlighted: to stand out layered elements (( IE: Selected Element is behind another but still
visible via highlight.))
- Fix the undo function, which can really mess up sometimes the displayed elements when used, needing to reload the beatmap.
- Fix the overload indicator after certain (unknown) events, causing it to stuck at certain values and not displaying the actual one.
(( It may probably need recoding. ))
- The Sprite Library should display in case of animations just the animation instead of all the independent frames and the animation itself.
- The capability to edit the properties of the animation itself.
- Allow toggling the capability to select and alter elements by doing click on the screen.
- Maybe the usage of gizmos to allow more precise control of the functions.
- Allow to edit events in a specific keyframe via parameters, positional values on move, numeric value for scale, or %number in Fade.
Since it's my first post, it may be hard to actually take credit from me but I'll address some things that I have ran into.
First of all, I have to say it's that I think it's awesome that the game actually has a text based code that more advanced users can easily edit for more technical stuff.
My problems are oriented for the standard or more basic user, revising some of the changelog and consulting with other users I concluded that the functionality of the editor hasn't been heavily altered in quite some time and may lack some strong features that may simplify the usage of said program:
TL;DR The sole idea of having a friendly editor and having the files stored as text which can be edited for advanced users is great, but there are some
features that could make the editor much better for newbies and advanced users alike.
Some of the sugerences are:
General:
- Allowing the creation and/or preview of beatmaps skins inside of the editor.
- Allow 'Inherit point' resnapping when the timing is altered.
- Allow to put comments inside the bookmarks.
- Bookmark highlighting for easy navigation. (( Maybe a dedicated optional windows which displays them? ))
- Allow in the editor to loop a certain point in the song while editing for timing testing.
- Undo history.
- More friendly song navigation wich correctly displays all the existing features and luckily some of the suggested ones.
- Autosave function (( Some people aren't just familiar with Ctrl + S ))
Dedicated Editors:
Again, some people may be used to the actual system but I think it would be wonderful if the editors could have a preview of their work like in Osu!Mania and Standard instead of just testing it from certain point.
- Dedicated CTB editor:
- See: ( t/129618 )
- Dedicated Taiko editor:
- The editor basically should allow the preview of the elements as they are in gameplay.
Storyboard Editor:
- Allow the creation of layers for elements which include:
- Layers that can be:
- Locked: To prevent accidental editing.
- Hidden: Self explanatory.
- Grouped: For multi element editing.
- Highlighted: to stand out layered elements (( IE: Selected Element is behind another but still
visible via highlight.))
- Fix the undo function, which can really mess up sometimes the displayed elements when used, needing to reload the beatmap.
- Fix the overload indicator after certain (unknown) events, causing it to stuck at certain values and not displaying the actual one.
(( It may probably need recoding. ))
- The Sprite Library should display in case of animations just the animation instead of all the independent frames and the animation itself.
- The capability to edit the properties of the animation itself.
- Allow toggling the capability to select and alter elements by doing click on the screen.
- Maybe the usage of gizmos to allow more precise control of the functions.
- Allow to edit events in a specific keyframe via parameters, positional values on move, numeric value for scale, or %number in Fade.