Wiki

**Makanyane** · 03-28-2008, 23:33

@Viking - thanks for linky - that's pretty much same syntax as I was trying....

*thoughts* - might be to do with what version of WikiMedia we are running - saw something in their version notes about 'magic words' being added in later versions....

- the {{ if }} maybe supposed to be a template that does something itself? Wikipedia does seem to have one which I tried borrowing but that didn't help, and TWC doesn't seem to have one although 'if' clause works there.... so that isn't getting very far as a solution...

EDIT: sorry drone wasn't ignoring your post am just a slow writer and didn't see it first.
you could try converting the table elements to just use the |- type syntax and avoid the html if you think that might work: http://meta.wikimedia.org/wiki/Tables
maybe try getting the table part working that way first then re-try the 'if' part?

**Viking** · 03-28-2008, 23:54

@both

Yes, I was thiniking maybe this wiki does not support {{#if:|}}. If typed at Wikipedia it gives a blank field; at the Org wiki it gives, yep, just {{#if:|}}. The If template at wikipedia is missing the "#" so that is definately not it.

For now, I'll just scratch my head, as I am just as, or maybe more, clueless as/than you.

**drone** · 03-28-2008, 23:57

I don't think {{#if:}} is a template, it's part of the MediaWiki ParserFunctions extension.
http://meta.wikimedia.org/wiki/Help:ParserFunctions
Maybe it needs to be turned on in the Org's wiki?

The problem with the pipe(|) format is that it gets trashed in conditionals. This is why I added the {{!}} template:

Originally Posted by http://en.wikipedia.org/wiki/Help:Table

A pipe character for a table row may be desired as part of a parameter value in the call of a template or parser function (in particular, it can be in code made optional using ParserFunctions). However, expansion of templates and parser functions happens before interpretation of table syntax. This causes a pipe character in a parameter value to be interpreted as a separator between parameter definitions. To avoid this these pipe characters are put with a special template:! ( talk edit history links ), see template:Table example with optional row ( talk edit history links ).

With the {{!}} template, I can get ok results, but the #if never has any effect, it always performs the "true" option and puts the "{{#if: |" at the top of the page as if it's an error.

Spoiler Alert, click show to read:

This is the code I'm using:

Code:

{{#if: {{{apmelee|}}}|
!colspan="2" style="text-align:center;"{{!}}Armour Piercing Melee Attack
{{!}}-
}}

I just want a centered line after the Discipline value that writes "Armour Piercing Melee Attack" if anything is passed into the "apmelee" param.

My head hurts, I'm going drinking. Hopefully I can work on this some more tomorrow. I would like to get this working before I start creating any pages for specific units, it will probably mean less work in the end. Have a good weekend!

**TosaInu** · 03-31-2008, 23:06

Hello drone,

I don't know.

An if condition seems to me like something very basic.

I do not know whether it needs to be configured, it could be (I'll look at it).

**drone** · 04-01-2008, 23:32

Due to the differences in build requirements, costs, and other stats, I think I'm going to separate the MTW and VI campaigns with a MTW and VI prefix. Since the engine is the same, the stat templates can be shared, but I think it's just going to be easier to split it up. This will lead to some duplication, but will give a cleaner page overall. Let me know if you think this is unwise.

I've got templates for units, ships, and buildings. I also have navbar templates for VI and MTW building (pseudo-tech tree style) and a combined unit navbar (which I will break out into MTW and VI). An agent template might be in the works, if I think it's worth it. I will be creating a projectile template for missile and artillery weapons, once I figure out the meaning of all the columns from ProjectileStats. Once this is done, I'll remove the missile stats from the overall unit template to clean it up some, and use the new template to display the unit's missile capability in detail. Splitting this out may also be a way around the conditionals problem.

I haven't gotten around to actually creating individual unit or building pages yet. Hunting around in the GnomeEditor to suss out any quirks I've forgotten. frogbeastegg was concerned about using her text, being credited with it, having someone change her text, and then being asked about the modified text. Completely understandable, so I'm looking for other solutions. I could write my own text, but it's just going to look like a poor imitation of her guide. I thought about putting her text in a locked page, and then including that into the modifiable unit page. Is that something that sounds doable?

**Viking** · 04-02-2008, 05:45

Yeah, you can make a template in which you copy the guide and protect such that only administrators can edit it.

**drone** · 04-03-2008, 20:37

Created a template for personal missile weapon stats, Template:MTW_Hand_Projectile_Stats along with templates for each individual missile type (not artillery yet). So in the unit description for kerns, for example, the template could be called like:

Code:

{{MTW_Javelin|ammo=4}}

The Template:MTW_Javelin fills in the various bits like range/lethality/etc. so each unit page only needs to worry about how much ammo is available to the unit and which weapon is used. Artillery units will be different, since each is unique there is no need for a weapon type template, although I will probably create one overall stats display template for artillery that each can use.

Also created a woefully inadequate page on ProjectileStats.txt, if anyone else wants to add some more detail go ahead. It's meant to be information for both players (to understand how missile weapons work) and modders (specifics and gotchas). I've never modded it before, so I'd love it if someone with more experience could spruce it up. I only ask that the field sections remain as they are named, I'm linking to them from the missile template column names.

With missile display in place, I'll remove that stuff from the MTW_Unit template to clean it up. Might get rid of some of the other conditionals, maybe a catchall "Notes" row for stuff like elite, AP attack, etc.