I was entering a few piecdes of armor in the artifact pages and it occurred to me that the data would be a lot more readable if we had resistance tables like we have on the creature pages.

Would it be hard to add a feature like that? I don't mind going back and updating all the pages. I gotta add those png things anyway

It is called templating. Anyone can make a template. The nice thing is you can modify the template and it will appear on every page. It can save tons of work if you ever make a change. Here is the creature template:

http://www.uoguide.com/Template:Creatures

Any page that begins with the "Template:" prefix can be included in other pages. If you could show me an example of what you have in mind I can try and make one up.

awesome

I'll figure this out and come up with some pretty good item templates

Here's what I've come up with for a weapon template

http://www.uoguide.com/index.php?title=Template:Weapons

Any idea how I can remove that cellpadding where the hit spell effects come in? I was trying a few CSS tags, but none of them had any effect on it. Sorry, I'm a bit of a wiki newb

I cleaned up the template to include some stuff I overlooked. The first example using this tempalte is the axe of heavens. I'm still not sure where to store the "2 handed weapon" piece of it. I think maybe we should have a category for 2 handed weapons, 1 handed weapons, and one for each weapon skill + mage weapon. I need to think about it a little more. Maybe some of you guys who are more "design-inclined" have some ideas.

There is no point in using a huge template like that where most of the fields are going to be left empty. There are only up to 6 magic properties per weapon. In this case it would be best to use a conditional template. I will try and set one up.

Cool

I was thinking of cutting out fields for the same reason, but a conditional template sounds like exactly what we need.

Ok, I just found a help on mediawiki. Tonight when I get home I'll blow through that and see what I can learn. It sounds like there is a set of conditional functions called ParserFunctions, which I think will make life a lot easier for us when it comes to templating the skill part of the pets template and equipment templates in general.

Later on, we may even be able to use the parser functions to add calculated fields to our creature data. Wouldn't that be cool! You enter the stats and it calculates the creatures min/max dmg based on base dmg and all other factors you have on the form. Also, we could make bard difficulty a calc field as well.

When I started doing this, I thought this wiki stuff was just a subset of css, but it sounds like it's a whole different animal.

The conditional template stuff is actually a plug-in. I think I have the right one installed. I will have to look into it.

gotcha

I think you have it installed because this command correctly returns "Empty" when slayer is undefined.
{{ #if: {{{Slayer| }}} | Defined | Empty }}

I am having a hard time getting it to bypass table code, though. If I try to put the block of code that displays the slayer data inside this conditional statement, I end up breaking that row of the table, which causes the slayer tag (the one I'm testing on) to still show up, but above the table instead of in it.

What I'm trying to do is use the conditional logic to bypass drawing a table row.

Ok, I figured out how to get the table rows to collapse if the parameter they represent was not passed in. I am going to see if I can figure out how to make them completely go away when their parameter is passed. You can see what I dd on the "slayer" parameter on the weapon template. I'm going to poke around with that a bit more and post here if I figure out how to kill the borders that are still showing.

I think all I need is to get it to let me collapse borders with a style, but I can't seem to get that to work.

Ok, I got it now.

You can see a working conditional template for weapons at http://www.uoguide.com/Template:Weapons

You can see it in use
http://www.uoguide.com/Axe_of_the_Heavens

I'm not completely done with the weapons template. I had taken out the <noinclude> blocks to make debugging quicker and have less impact on live pages. I'm also going to be working on cleaning up the appearance of the template here and there till I'm completely satisfied with it. I'm almost certain that the remaining work on the template will be easy.

It took me a while to get this one figured out mostly because I'm really rusty on CSS, but I think this template is a good example of how we can leverage conditional templates to make it easy for people to add wiki pages with minimal learning.

WOOT!