Condensing Category pages and re-drafting others as Lists.

The StyleEquip template currently lists "Enchant Availability" to reflect the categories an equipment is a part of, and I feel it may generate some confusion. Let's look at Guard Cylinders as an example.

Both Guard Cylinder and Rebis GC are part of the Categories: Magic Armor, Shield, Guard Cylinder, Steel. This causes their equipment page to display, next to Enchant Types, "/ Magic Armor / Shield / Guard Cylinder / Steel /". Nowhere here is there a distinction of Cylinder, which may create the false perception that GCs can't get regular Cylinder enchants, like Synergy (but they can!)

In addition, Magic Armor and Guard Cylinder aren't (to my knowledge, please correct me if I'm wrong) Enchant Types at the moment. The Category:Guard_Cylinder page could easily be merged into Category:Cylinder page, with any redirects forwarding the user to a dedicated section for Guard Cylinders, and Category:Magic_Armor would probably be better as a list (because, again, it doesn't correspond to an enchant type, and it isn't used for more than a reference for any users looking for equipment that confer M.Def/M.Pro bonuses).

TL;DR - Merge/redraft as List/otherwise edit any Categories so that they accurately correspond with Enchant Types.

Just checking for a go-ahead from a superuser, or any feedback or recommendations against the idea from other wiki editors.

For your example: So you're saying make Guard Cylinder a sub category of Cylinders...that right?

Also most of the data comes from the xml files and what not, which makes data input much simpler for the wiki's automated template generation.

I guess while the topic's here, there is only 1 ES that works with Instruments for Rank 9 Suffix (as far as I'm concerned), and that is Cherished enchant. Raven didn't work despite having the "Weapons" tag (on in the case of my Lyre, One-Handed Weapon). Oh well...only took me 1 run for the enchant but not like I'll ever farm it again.

I put it in its own category because certain idiots would eventually bitch about it.

If there is a consensus or someone else wishes to do it, they can be moved (or added) to Cylinders.

Much like how: Ranged Attack ≠ Throwing attack ≠ Combat ≠ Anything that that pings range? Totally.

Forgive me for my lack of knowledge of how the equip and weapon templates work nowdays, but can't we just edit tags like Guard Cylinder, Magic Armor, and other non-enchant related tags to not show up and make Guard Cylinder trigger the Cylinder tag? I don't really see a need for a category merge assuming it doesn't autodetect categories, rather it looks at the xml string of an item's itemdb entry.

Yeah, maybe I'm just misinformed, I know that it doesn't automatically copy over every Category for many skill equips. As an example, many items are part of categories "Reforgeable equipment," "Blacksmithed equipment," etc., but they do not show up on Enchant Type tab.

So I guess the question is if it's possible to A) remove inaccurate enchant types (see: earlier example; Magic Armour, Guard Cylinder) and B) add in ones that an equipment isn't necessarily categorized as. For example, Guard Cyl showing Cylinder without actually merging it.

Okay, it should now say Shield and Cylinder enchant tags on that section, and it is still in the Guard Cylinder category. I also removed the Magic Armor enchant tag but didn't touch categorization so all magic armor and guard cylinders are still under that category. I am not sure how remove guard cylinders from the magic armor category (without touching actual magic armor) due to limited knowledge.

Nice fix! I think it may be worth keeping them a part of the Magic Armor category for now, as they do meet the requirement of being an equipment that adds M.Pro/M.Def, if any improvement is to be made it'll be just converting this page into a List page.

Converting which page into a list?

Only Category:Magic_Armor, it's a superfluous thing though, really.

I'm just going to put this here, since it's vaguely relevant. Anyone have experience with Semantic MediaWiki? Were they good or bad experiences? I think in theory it could benefit the wiki quite a bit. One way would be getting rid of manually updated list pages. Another way is being able to search for pages by properties.

Manually Updated List Pages?

What is this heaven?

In the form of inline queries!