I have abstracted the Items page, as well as the Arsenals page. I have not abstracted the Consumables and Pickups pages because I would consider them "leaf pages", and thus they do not have any subcategories. This is how I plan on re-modeling every single Archives page. However, like those just noted, the bottom-most (leaf) pages will not have the Subcategory section, as this is what makes them leaf pages - they are at the end of the tree (sorry, CS nerd). I don't think leaf pages should have any specific formatting requirements, however the (possibly) pre-leaf pages should. For example, the table listing all the swords on the Sword page. This would be a pre-leaf page, as we do not want to list every single sword as a Subcategory of Swords, but rather in a more explicit and visually pleasing manner. Hence, pre-leaf pages. However not every page that lists leafs must be a pre-leaf page; Items itself lists two leafs: Consumables and Pickups, yet it does not need to be a pre-leaf page.

I am currently working on the Equipment page, now.

Actually English is my first, and only, language. I thought that would be fairly obvious as my use of grammar and language is one of the top on here. I used "Arsenals" as a name-holder for now, for lack of a better word (same with a few other words).

I don't really understand the problem you're pointing out, pauling, can you be more specific? In reality, a player would either type in the Material if they want information on it, or simply go to the page of the weapon they perhaps need the Material for. I'm just not sure what issue you're trying to describe there.

The main reason that I proposed, and am testing, this tree system is because I think that Items, for example, can be organized in a totally hierarchical way. This renders the so-called tree system I've been trying out; a 100% consistent database-like storage system for said Items (except for leaf pages, which I have yet to justify).

Edit: Also, I never used tables (I don't think) except for my Existential Listing page - which I will fix another time being as it's not important right now. Plus, I have just started Wiki editing yesterday, so that might explain my... newbness? However, nothing of what I have done really requires any advanced knowledge of Wiki coding (aside from Categories, like you mentioned, but I have yet to decipher what exactly those do). As for these categories, most pages had redlinks before I even did anything, so honestly I don't feel very out of place when it comes to those.

Also, I posted this thread for the exact reason to publicize it. That being said, if it is really unpopular, it can be easily shot back. Therefore, it is no big deal, even if I were to accidentally delete a whole page. :P

And also... aside from the fact that some of the words I have used are not "Real", would that really matter? Is a Khorovod a real sword? Is a Wolver a real animal? But really, these are all relatively non-important issues, and plus simple name-holders - but I don't think people would complain about "Equips" not being in the dictionary.

Anyways... you seem like an honest and reasonable person, which is what I'd need for constructive criticism. What exactly do you think are issues with this style? I don't mean non-existent words or any little bits like that, I mean real issue people would complain about - that sort of thing.

I get what you're saying, and respect the fact you are being honest and thus helpful. I suppose there are some extra branches/levels which I have added in for consistency sake, to be able to separate sibling branches/trees and such by distinct pages/nodes, rather than the content within them. I'm going to make a change to that now... and fixify the non-existent words just for you, pauling.

Upon the problem of these leaf-pages, I have realized that, regardless, maximal consistency cannot possibly be achieved. This has discouraged me, as always.

Aside from the point, I have already claimed the validity of the word Existential. Although the other two I do admit do not exist, a mere few words shouldn't suffice as to hinder my English-speaking capabilities. :P

... And apparently I'm not human, buahah.

Edit: Okay one thing that I really think needs to be differentiated is the Inventory-based Items (what I have called Arsenals as they go into your Arsenal/Inventory). I have just renamed this section to Inventory Items for the time being.

Edit 2: Okay I fixed it up, still with what I would consider pure consistency - just that the categorization skips over 2 places in some spots, but is made up for via the current page. It now takes the same "clicks" you were referring too, as well, and I have added the Category tab at the bottom to a bunch of pages. A few questions, though... why is "Weapons" listed on the page for Swords, for example, if no such page exists? Are Categories used solely for keywords, or do they have some sort of hierarchical meaning behind them? Lastly, should a Category tab list the current page? For example, should the Items page have the category Items included?

I did look up the meaning of both, and to be honest, I thought Existential made more sense, as the list itself obviously does exist. The list more pertains to existence, as it tells of existence, rather than stating that it, itself, does exist. Perhaps a better title would be simply be "List of Existing Items", hah. I guess it's a matter of opinion.

Thanks for the link, I'll do some practice on my (admittedly) messy list tomorrow, as I should get to sleep now.

As for the line break tags... it turns out that carriage returns don't always work. For example, directly underneath = Title = lines, the amount of blank lines doesn't seem to matter - at least for me. Anyways, I got rid of these instances anyways, with what I just did, so I'll go through and get rid of the line break tags as well (the rest of which were added for consistency). Is there anything that forces a line break? The fact that the * and # methods add a useless bullet/number is the only issue there.

Edit: Forgot to address this again, but, as I said before, the only reason I went ahead and did this was because I knew it could be undone with a few clicks. Plus, there's probably very few Wiki views within a 2-hour time span - but regardless, I'll try not to let my documentation-obsessed side get to me next time.

Also, your suggestion of the word Extant makes me want to rename it "Extant Item Listing" - which seems to make the most sense, and is the most readable, so far.

Annnnd... what does the |* do in the category tag? Also regarding questions from before: why is "Weapons" listed on the page for Swords, for example, if no such page exists? Are Categories used solely for keywords, or do they have some sort of hierarchical meaning behind them? Lastly, should a Category tab list the current page? For example, should the Items page have the category Items included?

Thanks Shango, and pauling. Sorry for the trouble earlier, sometimes I just get a bit carried away with my "consistency" issues. Just as they say, with great power comes great responsibility. We are all given the great power of being able to freely edit almost every page on the Wiki, but should all be aware that certain responsibilities must be satisfied as to not disrupt the natural flow of things. As i have said many times before, I am ambitious in the sense that I feel my real purpose, aside from testing itself, is to record all of the information I possibly can. This may delude one of the responsibilities they must still maintain; as it goes for myself. That being said, I don't really have the responsibility part covered yet, for a few reasons.... one being I should probably accumulate more than 4 hours of Wiki coding experience before I go attempting something like a complete makeover, let alone waiting for intelligent replies about such a proposition to begin with. Not to mention more than a few hours of sleep, which is a common issue for University students. My basis of jumping into it so quickly was that it could be easily reverted. I think the main problem is, just as pauling stated, I am trying to force it into too much of a database-like structure; which is not the most user-friendly way to do so in reality. This is how it is done in code, and in an actual database, and so on... but not in an encyclopedia. I think what I should have done was, rather than attempting to morph the Wiki hierarchy itself, was morph the hierarchy of my own listing (EIL) into the form I wished instead. This would make a lot more sense being as this is exactly what the listing is intended for: structured and consistent look-up, all in one single spot. I feel pretty stupid now, to say the least. I'm not a very good group-worker at all, unless of course I am working in a group that thinks the same way I do (which isn't very typical, as you might have figured).

Next time I go off like this would someone please, for the love of all that is realistic, slap me.

Anyways, I would take comfort in knowing that you at least somewhat understand what my intentions were, as far as the whole consistency and categorization stuff goes. I am now going to implement this into the EIL so that it simply lists only the names of pages as leafs on the giant tree - being links to said pages. This way, it will be easy to see which specific pages are missing (redlinks), and which need to be updated, and so on... I am currently devising a plan to make this EIL actually useful not only for readers, but also for editors. Perhaps now that it is on the Wiki itself, I can use colour coding and more advanced formatting to signify which pages need to be updated, after releases, for example, among other seemingly useful objectives. I'm thinking it would be a good way to physically see how much needs to be done, updated, or whatever the case might be - as far as specific template-based leaf pages would go (Equipment, Materials, etc...). I suppose you could call it a giant all-in-one checklist. I'm only including Items (Arsenal Items, to be exact) for now since they are the biggest issue.

Thanks. As soon as I finish the list (of which others should feel free to update and confirm things on their own), I was thinking of getting to work on the Trinkets since they don't even exist yet. That shouldn't be too much work, but my real challenge will be the template issue as I have barely any idea how to create/manage them. At least the Trinket template should be relatively simple compared to other ones, once I learn the how-to's.