osu-wiki icon indicating copy to clipboard operation
osu-wiki copied to clipboard

Published 20 hours ago • verified publisher icon ppy

Update/rewrite the storyboarding articles

Open TicClick opened this issue 4 years ago • 4 comments

all the guides and specifications on wiki are 5 to 10 years old, if not more. granted, the specs haven't changed over the time, but the approaches have.

I have no specific action items, only a list of things that should be mentioned somewhere, possibly in a separate article (something like "best practices"):

  • history of storyboarding: strager's osq2osb (I think it was called that, or just osq), Moonshade's SGL, Wafu's osbpy and SGL optimization article, Damnae's storybrew
  • relatively modern concepts, like particle systems, spectrums, 3d models and stuffs
  • tools such as storybrew (can't stress its importance enough), OSB optimizer, particle and spectrum generators, whatever floats nowadays
  • things from https://osb.moe/learn/ (these could probably be incorporated into the existing articles directly)
  • anything from Damnae's storyboarding server

TicClick avatar Jan 21 '21 20:01 TicClick

slightly related: #974

TicClick avatar Feb 08 '21 14:02 TicClick

I've been planning on a rewrite of the entire storyboarding section of the wiki (over a few more months than I'd like to admit). Below is a blueprint of what should be where. Suggestions and additions are welcome! I intend to be working on this over the coming couple months (or a few short bursts, depending on how I manage my other projects)

Structure

Formatting

Formatting conventions I intend to use that don't appear in the Article Styling Criteria.

  • Syntax specifiers should always be in code-blocks, with variables in camelCase enclosed with curly braces ({}) (honestly this should apply everywhere in the wiki), followed by a list explaining the variables Hit object syntax: {x},{y},{time},{type},{hitSound},{objectParams},{hitSample}

Remarks

  • osu!_File_Formats/Osb_(file_format) is currently just a stub that links to Storyboard. For this structure, it would still just link to Storyboarding/Specifications/Scripting_language, but this could alternatively work in reverse.
  • Storyboarding/Best_practices would basically be a glorified guide, and although I don't currently know what should be mentioned there, it could be a good "things you should know" section detailing common pitfalls and things to avoid (with Optimisation containing more details on that)
  • I'm pretty much of the opinion that Storyboarding/Specifications/Scripting_language should be a single article, not split up into lots of pieces (it should be a reference sheet), while Storyboarding/Specifications/Concepts (name suggestions welcome) can be split up into multiple articles since there can be more in-depth information here, but I'm not sure yet.
  • Storyboarding/Specifications groups together the related sections (a lot of technical information)
  • This separates this section of the wiki into Storyboarding and Storyboard, just like Beatmapping and Beatmap, which I think is definitely the way to go.

Walavouchey avatar Dec 10 '21 08:12 Walavouchey

very well thought out. one thing is that I had to merge Storyboarding and Storyboard in the past due to lack of content in the former — hopefully your work will allow these two to coexist as different articles again

TicClick avatar Dec 10 '21 12:12 TicClick

https://twitter.com/tochiiDesign/status/1668759156126543872

TicClick avatar Jun 16 '23 00:06 TicClick