Template:Shared Draft 226

=Opening Notes=
 * Image, Title, Character, Notes
 * Number (Release Date), Type, (Release Type)
 * Title/Character/Type
 * Exclude Release Date as # can sort? Will have '#' double as the release date sorter
 * Line-break for title like with Events?
 * Science/Magic Side division already done in the column list
 * Can a dividing line be done in a table?
 * 28 Endless Summer is definite in the post-release ones

Notes section-related:


 * Inspiration under Notes
 * Use sort for notes to have pseudo-sort for one other thing as though it had a column of its own?
 * Moves?
 * Release type will be done at the top of the Notes section.
 * Available at initial release.
 * Released in standard pick-up gacha on [Date].
 * Released with event "Event" on [Date].
 * Notes section
 * Release details, Scene inspiration, similar details, and only then, any moves/stat details
 * Variant type, colour, side, stats, moves are stuff for below?
 * Point of Release (Launch, Standard Gacha, Specific Events etc)
 * Scene Sources, Inspirations, Allusions, References etc
 * New Character/Variant notes
 * [RELEASE TYPE] on 20XX/XX/XX.
 * Hidden note/Template:HR?

,

Release Type Possibilities
The first part of the notes and the sortable element riding on the Notes column's sort function. All will be of form [RELEASE TYPE] or [RELEASE TYPE] on [DATE]. Date being DD/MM/20YY, 20YY/MM/DD or Dth MM 20YY, unfinalized - either way the '#' columns sort functions effectively carries out any date-related sorting.

Type 1: Available at initial release.
 * Note: Mostly finalized. Wording tweak if really needed but pretty much done. Doesn't really need a date?

Type 2: Released in [X] gacha on [Date].
 * Released in standard gacha on [Date].
 * Released in pick-up gacha on [Date].

Type 3: Released [...] event [...] on [Date].
 * Released with/in...
 * Just event or element before event in some cases (e.g. collab/Summer/Halloween/Christmas event etc)(given possibility of variant data afterwards covering it as well).
 * Uncertain whether to include event name here or below in the Anchor 1 data area given circumstances of the table and content.

Variant Data Possibilities
Considering having a bit after the release type bit, that has brief information regarding the variant of character in question. Considered possibilities include:
 * 'Collab character's or something similar for ones from another series (e.g. KonoSuba, Shana), and a collab-themed variant one (wording not settled on yet) for characters wearing outfits based on other series (e.g. NieR).
 * Seasonal variants (e.g. Summer/(Swimsuit?/Festival?), Halloween, Christmas, New Years, Valentines etc)(though possible overlap with other possibilities)
 * Other possibilities - Maid, Butler, Bride/Wedding Dress, Swimsuit etc
 * Variant info specific to characters in question? (here or in Anchor 1 area)

One other possibility considered was noting stuff like when it is a 'new character' (in IF out of Toaru), the first 3-star variant of a character, or the first battle-type version of a character, but not sure about whether it would work (in part or full).

Anchor 1 Position Data Possibilities

 * Event name or remaining variant detail if not in first part (Release Type).
 * Scene Sources, Inspirations, Allusions, References etc, similar details.

Anchor 2 Position Data Possibilities
Previous notes extract:
 * Moves/stat details
 * Variant type, attribute, side (covered by column list above?), stats, moves are stuff for below?

Boom-App Wiki Sample

 * Rarity: ☆ 3 ☆ 2 ☆ 1
 * Attributes: Red, Blue, Green, Yellow, Purple
 * Type: Battle/Assist
 * Attack Type: Physical/Supernatural
 * Side: Science, Magic, Other
 * Directions: 1-3 (L, M, R)
 * Obtaining

Moves:
 * Attack
 * Skill
 * Special

Passives?

Stats:
 * HP
 * 器用, Dexterity?
 * Physical Attack (物理攻撃)
 * Supernatural Attack (異能攻撃)
 * Physical Defense (物理防御)
 * Supernatural Defense (異能防御)

Sample
=Toaru IF Combined Table Experiment=

=Other=