Discussion

---

Welcome to the wiki's discussion page. You can discuss matters here. Resolved matters will be archived. Enjoy your stay! --MagiNinjA 01:02, 3 January 2008 (MST)

---

Recipes Standardization

The assembly recipe block BongBob used on the filter page is pretty nice. I've tried it with the Astral Stock Exchange software put the code in my user page. Let's use it? --Livia 16:52, 22 February 2008 (MST)

• Or even better, would it be possible to make a template for them? --Livia 16:56, 22 February 2008 (MST)
  • Also, can we suppress the content box for pages with more than 4 sections? It's often unnecessary. --Livia 17:33, 22 February 2008 (MST)
    • You can turn off the Table off Contents under my preferences/Misc --Baltar 01:16, 21 March 2008 (MST)

Clan/League Directory/Pages

I think that a directory similar to the Coldfront wiki will suffice. As time passes, TH will have it's own history with leagues, and if the history is worthy of mention, it will get mention/approval. Agree/Disagree? --MagiNinjA 01:02, 3 January 2008 (MST)

Drop Location / How To Obtain standardization

I propose 'Drop Location' be changed to 'How To Obtain. This'll make pages more standardized, and allow us to make templates and stuff.

For dropped items, I propose [[Location]]<br> *[[Enemy]] **Possible second requirement

I also propose a ===Uses=== section of each page, where recipe inclusion would be added. --MrAndersonMan

Data Namespace

Do we need a Data namespace like the KoL Wiki? I was just about to start templating in-game effects when I noticed that the de facto standard here is to include images in the "How Obtained" section for effects' source items. Item images are also used in a lot of places like monster/adventure drops, and the way things are handled now--the {{obtain}} and {{fight}} templates explicitly require the item name and image name to be input--would result in a massive amount of work if an item gets updated.

Somewhat relatedly, should {{fight}} be simplified? There are a couple of places where the template can't be used because there are more drops than there are spaces for in the template (e.g., mochi vendor). The end result is that the drops are hand-coded and end up under the "Known Resistances" heading. Perhaps the template's a little too ambitious? --Bagatelle 18:56, 21 March 2008 (MST)

• Bump? I've noticed some recent changes to {{item}} that really look like they would benefit from a data namespace. Images and plurals are/can be reused in different contexts without having to manually type them in (like what's happening with item drops in combat pages currently). --Bagatelle ^T/_C 17:59, 17 November 2008 (MST)