It feels weird to just stick the icon in the infobox by itself. I've put it someplace else.

Check the Imperial Tricorne Page. (since it's a template a few other costume pages will have something similar until I clean them up to make sense). I have it so the icon only shows up if there's an icon in existence.

I feel like it reads well.

Thoughts? if you don't like, please have a suggestion. Like instead of broccoli, let's have ice cream! Don't just dislike broccoli.

Regarding this icon thing, don't worry about updating pages with it, since it's in a template, we can easily move it wherever we decide we want it, as long as it's within the template of course.

Yes, that's where' it's always been. But things get squishy and really ugly in infoboxes with the long names, which is the issue this thread mostly discusses lately. I'd like suggestions about where else to put the icon, besides not in the sentence (because I also do not like that for paragraphs, but I don't mind it for single lines), or where it was before. So, new suggestions.

Infoboxes really should have the page title in the top for entities, most wikis (especially game wikis) do this. Not having the name in the header was a sort of minor thought... I don't think a non-title row for the name in the infobox is a good idea - hence the changing away from "quick info," "ITEM TYPE X info," "at a glance," "key facts," etc. And turning it into a smaller font, one that's still larger than the page text. Which we've agreed works. Now, where to put the icon... yes, icons should be in the infobox. I just needed to put the icon someplace I wouldn't forget it, but also remember that some items don't have a solid icon (accessories and recolored costumes don't have a single representative icon unless a wiki editor makes one).

A row with "arsenal info" is probably best, star info can go there too. I'll get back to that after...this accessory/color pattern project I've mentioned in another thread.

After working with the infobox for several days, I'm really liking the icon in the set information section - it fits, it functions, and it lets users know without a doubt whether or not the item is part of an official set. But I'm sugarcoating it cause I'm biased (I also can't find any problems with it really). Thoughts?

If there are no "better" suggestions or objections from other users/Bopp/my brain within, say, a week or so, I'll make these changes for other infoboxes where relevant. Mostly gear items. Especially those gunner armor/helmets >,..,>

Then design discussion on other currently nonexistent infoboxes, like missioninfo, will begin, stay tuned.

I can't seem to resolve an issue with the coding of ArmorInfo's category parameters. I've put in a shoddy switch so the wiki doesn't have a ton of weird/empty entries for all relevant items. This switch, 1="new" or 1="old" will be entirely removed once issues are resolved. Could someone look into this, please? (also help implementing these changes we seem to all want would be great - once the issues are resolved, template documentation will be completed so help can be requested without too many "okay I will help but what do I do?"). If you start helping, be prepared to edit the wiki for many hours, as there are many many items and we want them all to be updated quickly so players aren't confused by different entries for items that seem to be the same type of item. I had some wonderful help with implementing weaponinfo on all the weapon pages, and feeling the sluggish speed of doing solowork again is like eating melted icecream. I don't like asking for help but man, this is a lot of icecream, and daylight's burnin, and it seems like we all want this icecream, so I shouldn't eat it by myself.

Link to summary of issue(s)

Please hold of helping until issues are resolved and documentation is in place. Unless...

If you are confident and want to help, you can edit individual pages before the issues are resolved, just know that some of the categories will not be visible until the template is fixed.

What I would suggest doing, if you want to help, is going through all the (armor and helmet) items using 1=new using the Vog Cub Coat/Cap as an example, then after all those items are done, remove the new/old switch from the template coding (retaining only the "new" parameters), and then removing "1=new" from individual pages. This keeps information published without the panic of a time crunch as we make changes. I'm doing it this way instead of using an entirely different template, for reasons stated in the link above. If you do help implement, remove repeated set info on the page itself whenever it occurs, unless the item is in a bundle or something weird like that... use the Ignition Armor page for example of what to do there. Also remove repeated categories on individual pages that the template takes care of.

We will be adding gallery stuff later, like we did for the weapon page overhaul. But that's down the road after these infobox changes, and after we finish the weapon pages (we are finished with the infobox part of the weapon pages).

Beyond weakness 1 and status 1, the categories fail to show up (the weaknesses will be red because weakness categories have not been created yet). These could also be a bit cleaner since they're repetitive. The issue is extremely apparent with implementation, and not so much with just looking at the code (unless someone with flawvision looks at it, like my mother when I tried to clean up a room as a child). For items like chaos cloak or dragon scale mail, the issue rears its head, but for items with only a single status, it's not an issue.

Because idk what's missing for the switches. A bracket somewhere? Perhaps it should be #if, or eq, instead?