Forum:Spirit battles: Difference between revisions

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
(Created page with "{{forumheader|Proposals}}<!-- Please put your content below this line. Be sure to sign your edits with four tildes: ~~~~ --> Alright. About damn time I put this up. To put it...")
 
mNo edit summary
Line 58: Line 58:


Obviously this is one example, but I hope that it still gets my idea across. [[User:Aidanzapunk|<span style="color: black;">'''Aidan'''</span>]], [[User talk:Aidanzapunk|<span style="color: orange">'''the Spooky Rurouni'''</span>]] 13:00, October 26, 2021 (EDT)
Obviously this is one example, but I hope that it still gets my idea across. [[User:Aidanzapunk|<span style="color: black;">'''Aidan'''</span>]], [[User talk:Aidanzapunk|<span style="color: orange">'''the Spooky Rurouni'''</span>]] 13:00, October 26, 2021 (EDT)
'''I like this'''. I feel like there's a lot of bloat and unnecessary info in these tables, specifically in the "inspiration" table, and what is on the Roxas table is just ridiculous. I'd prefer having precision rather than having more trivia points just to explain the obvious. [[User:Cookies and Creme|<span style="font-family: Georgia;color: black;">Cookies</span>]][[File:CnC Signature.png|20px]][[User talk:Cookies and Creme|<span style="font-family: Georgia; color: black;">Creme</span>]] 13:10, October 26, 2021 (EDT)


{{Proposal}}
{{Proposal}}

Revision as of 13:10, October 26, 2021

Forums: Index Proposals Spirit battles

Alright. About damn time I put this up.

To put it bluntly: I really dislike the formatting of the inspiration column in the spirit battle pages. It makes short points that break the flow of reading, sometimes pointing out blatantly obvious information, and, in worse cases, making speculative statements that stretch harder than Wii Fit Trainer's taunts. I'm proposing that this formatting be changed to combine points of similar information, removing anything not as well as making an effort to not make short, blunt points that take away from any information that could (and theoretically should) be provided. While this does make the points a little bit longer, which can potentially be an issue in a cramped column of information such as this one, I believe priority lies in how we present the information itself, rather than how it looks on the page.

As an example, let's use the newly released Roxas. I'm putting these behind show/hide bars so that this page isn't insanely huge.

This is how it's formatted at the time of posting this forum.

Spirit Battle parameters Inspiration
No. Image Name Enemy Fighter(s) Type Power Stage Rules Conditions Music
1,507
SSBU spirit Roxas.png
Roxas Sora SoraHeadWhiteSSBU.png (160 HP)
Neutral
13,800 Hollow Bastion (Dive to the Heart, Roxas) •Health Recovery
•Move Speed ↑
•Attack Power ↑
Stamina battle
•The enemy has increased attack power after a little while
•The enemy has increased move speed after a little while
The enemy starts the battle with a Killing Edge
Fragments of Sorrow Spirit Battle inspiration:
  • Sora is the origin of his Nobody, Roxas.
  • The stage references the Station of Serenity, the location of Roxas' boss battle in Kingdom Hearts II Final Mix.
  • The stage and music represent Roxas' Dive to the Heart station in Kingdom Hearts II.
  • The Attack Power ↑ and Move Speed ↑ rules reference how Roxas uses quick and powerful attacks during his boss battle.
  • The Health Recovery rule references the Cure spell in the Kingdom Hearts series.
  • Sora starting off with a Killing Edge references how Roxas dual-wields his Oathkeeper & Oblivion Keyblades.

Other trivia:
  • This spirit's Support type references Roxas' role in aiding Sora in the Kingdom Hearts series.
  • This spirit's Neutral type references Roxas' status as an ally and enemy in the Kingdom Hearts series.
  • This spirit's Weapon Attack & Move Speed ↑↑ ability further references how Roxas uses quick and powerful attacks using his dual Keyblades during boss battles.

This is nearly identical to the way I had made it, with some minor touchups since that edit of mine, but is nonetheless how I think stuff like this should be formatted.

Spirit Battle parameters Inspiration
No. Image Name Enemy Fighter(s) Type Power Stage Rules Conditions Music
1,507
SSBU spirit Roxas.png
Roxas Sora SoraHeadWhiteSSBU.png (160 HP)
Neutral
13,800 Hollow Bastion (Dive to the Heart, Roxas) •Health Recovery
•Move Speed ↑
•Attack Power ↑
Stamina battle
•The enemy has increased attack power after a little while
•The enemy has increased move speed after a little while
The enemy starts the battle with a Killing Edge
Fragments of Sorrow Spirit Battle inspiration:
  • Roxas is Sora's Nobody in Kingdom Hearts II. He is able to dual-wield Keyblades, primarily using the combination of Oblivion and Oathkeeper, referenced here by Sora starting off with a Killing Edge.
  • The overall battle represents Sora's battle with Roxas in Kingdom Hearts II Final Mix, where Sora meets with Roxas in The World That Never Was, and is pulled into battle at the Station of Serenity. Initially just a cutscene in Kingdom Hearts II, the scene was expanded upon in Final Mix to turn it into a fully-fledged boss battle.
  • The Attack Power ↑ and Move Speed ↑ rules reference how Roxas uses quick and powerful attacks during boss battles.

Other trivia:
  • This spirit's Weapon Attack & Move Speed ↑↑ ability further references how Roxas uses quick and powerful attacks using his dual Keyblades during boss battles.

Obviously this is one example, but I hope that it still gets my idea across. Aidan, the Spooky Rurouni 13:00, October 26, 2021 (EDT)

I like this. I feel like there's a lot of bloat and unnecessary info in these tables, specifically in the "inspiration" table, and what is on the Roxas table is just ridiculous. I'd prefer having precision rather than having more trivia points just to explain the obvious. CookiesCnC Signature.pngCreme 13:10, October 26, 2021 (EDT)


Proposed.png This discussion is in regards to a proposed change on SmashWiki. The discussion must first meet with a consensus before it is implemented.