Template talk:Infobox weapon

Different colors for different Unleashes?

Well, it seems that we've begun adding elemental "skins" to some infoboxes (in case anyone hasn't heard, it just changes the color scheme). I figured we could use them to make pure-element weapons stand out more, but then another idea occured to me: Should we add separate skin fields for each of a weapon's Unleashes? That question wasn't rhetorical, either; I'm really not sure if we should or not, so if anyone is for or against it, be sure to speak up! The World's Hungriest Paperweight 14:09, 4 June 2011 (CDT)

Adding skin fields to the Unleashes would certainly help them stand out, especially since the new Unleash system means that weapons now have Unleashes of multiple elements. Not to mention it would be nice to have a, easy way of identifying pure-element weapons. --Sippyjuice 14:14, 4 June 2011 (CDT)

Remove Unleash rates?

I'm thinking we should remove the whole Unleash Rate section from the weapon infoboxes because they're either 35% just about every time in GBA, or they are unknown in Dark Dawn and very likely to never be known or calculated. This redundant information makes the infoboxes longer, especially the Dark Dawn infoboxes with multiple unleashes, and that often causes the infoboxes to stretch the page out much longer than the actual page content can fill up. For the few GBA weapons that have 40% unleashes, all you'd need to do to convey the increased unleash chance is to add it to the Side Effect section at the bottom. Erik the Appreciator 14:20, 4 May 2012 (CDT)

No objections here. The World's Hungriest Paperweight 23:15, 4 May 2012 (CDT)

Pages with multiple infoboxes

On the pages where we have this infobox multiple times (like Blessed_Ankh ) it gets a bit weird on mobile. At those super compressed widths they don't stack, and they are just kind of randomly placed throughout the article. I'm not totally sure what the "solution" should be here. I want to bring it up though as over half of the people that visit the site are from a mobile device (roughly 55%). Any thoughts on how to best approach? ~ dkpat (talk) 12:12, 5 April 2023 (CDT)

Does it consistently happen like that even if the later infobox is moved down to right under the "Analysis" header in the source code? What happens with the infoboxes on Sol Blade, where they're farther apart and have section headers clearly dividing them? Erik the Appreciator (talk) 12:18, 5 April 2023 (CDT)

Yeah on mobile the second Sol Blade infobox is indeed pushed under the Analysis heading. So you get the intro paragraph, GBA infobox, table of contents and the rest of the sections then at the start of analysis the DD infobox appears. The infoboxes do appear on the page where we place them, It just doesn't really make sense for the DD ones to be where they are in the page. The obvious 'fix' is just to insert the two infoboxes together in the page, but I don't _really_ think that makes for a good user experience on mobile either; Two really long tables on top of each other makes for a lot of scrolling to get to the meat of a page.

The only things coming to my mind to address this are all kind of painful. It's either we find a way to combine the two into one (which sounds kind of painful), split the weapons into individual GBA and DD pages, or figure out some kind of tabbing system to the infoboxes letting users flip between which version they want to see. :/ ~ dkpat (talk) 17:32, 5 April 2023 (CDT)

It just occurred to me that tabbing between different games' infoboxes for the weapon in the same spot at the upper-right corner is how we would have unavoidably done it if there were more Golden Sun games treating recurring weapons with their own modified Unleash systems and warranting each of their own infoboxes. We wouldn't want 3 separate similar infoboxes for a weapon all rigidly lined up alongside the right edge while causing huge swaths of empty page space with scant few paragraphs in between them. ...So that would seem to be the only solution with any sort of forward-thinking future-proofing angle to it. Erik the Appreciator (talk) 17:47, 5 April 2023 (CDT)

In fact, I can imagine other benefits to having tabbing functions the way a lot of wikis do it. Were there ever to be Golden Sun remakes and all the characters had newly drawn official arts, we'd want those in the character infoboxes up on top but would want to allow users to click tabs underneath them to see their 2001/2003 arts in that same space. Erik the Appreciator (talk) 17:57, 5 April 2023 (CDT)

Another angle I'd like to push is that I'm not sure it would feel right for every weapon page in particular, out of all other item pages, to be split into separate articles when the wiki does a lot more than others to group together closely related subjects so that users don't have to hop between as many URLs and links. Whereas other RPG-focused wikis tend to have a separate page for every single enemy (including palette swaps), spell, and so on, we group together differently named members of monster lineages, put all stages of a given class series into one class-series article for them, put all stages of a Psynergy series together into one article, and so on...

Just in case it's not feasible to have a corner weapon infobox have a button that essentially makes the default GBA weapon template completely disappear and have its separate DD counterpart appear in its place, I suppose what could be done instead is to retire the Unleash segments forcibly conjoined with the parts of the weapon infoboxes that, on their own, mirror other items' infoboxes. Have each weapon have only one weapon infobox with merged game info like the item infobox on a page like Potion, with the DD weapon model as the caption image whenever a DD model image exists for it (and the GBA unleash screenshot would be moved to the bottom Unleash gallery in that case). Then, have all-new, game-separated, non-side-aligned Unleash information templates in the content itself that contain what was previously in the Unleash effect fields, and put them in the center of the content somewhere safely below the now-shorter corner infobox. Just throwing all this out there... Erik the Appreciator (talk) 01:25, 6 April 2023 (CDT)

I would also like to avoid splitting the pages by game. While there could be SEO benefits from it (who knows) and it would solve this dilemma, I agree that it would be inconsistent with the rest of the wiki. I don't really think readers will be thinking about which game they are wanting to know about when they arrive so having them both on one page makes it easier for them imo.

I asked in the NIWA discord for thoughts on how others have addressed this sort of problem and did get a variety of approaches. A few did suggest tabs (KH Wiki and inkipedia) Others suggested splitting all that info out into tables or sub-infoboxes more similar to our psynergy ones. Examples for that: Fire Emblem, Nookipedia (villager info section) I am a bit on the fence on this one. I would prefer to have all the information visible at the start and I think having the subsections would be a boon for readers (plus makes sense with some of the content we already have written), but that doesn't leave much for the "main" infobox. ~ dkpat (talk) 11:05, 6 April 2023 (CDT)

Oh and to complicate it, I noticed Gaia Blade has different stat mods between the games (is that just a mistake?) ~ dkpat (talk) 11:07, 6 April 2023 (CDT)

The Kingdom Hearts example was exactly what I was thinking of because it doesn't take much effort for someone searching "Lionheart" for the Chain of Memories incarnation of it to click the KHCOM tab to replace the irrelevant-to-them default infobox for the first game's incarnation. And that would make it easy to have additional future infobox versions in theory without complicating the page content below it with supplementary infoboxes or something. And yes, Gaia Blade, Knight's Greave, Silver Greave, and Ninja Sandals were among the only items Camelot adjusted the actual stats of between game generations (though that's nothing a simple break tag in the contents of the changed stat field wouldn't solve if we decide on the merged template idea with Unleash segments broken off into their own infoboxes instead, like what those latter three items demonstrate). Erik the Appreciator (talk) 12:17, 6 April 2023 (CDT)