Template talk:BattleInfo

From NeoDex
Jump to: navigation, search

Wondering if this will be needed, as the table and the image of the character on the article have since been seperate since the beginning (as shown in Pant Devil, Kanrik and other opponents of the Battledome in each of the characters "Battledome" section).--Jacob 16:49, 7 Jul 2006 (CDT)

hmm, whoops. I guess the table will work just as well then. Give me time for fix all the data properly before you delete this. NeoEva88 08:56, 8 Jul 2006 (CDT)

The tables are seperated, but the table is kinda unwieldly, I suggest we use this template without the image section, to give the table a cleaner look. NeoEva88 09:45, 8 Jul 2006 (CDT)

Okay, I've changed my mind again. I've tried to implement in the tables, and I think it's a lot more complicated, and will become a problem again after every major edit to an article. I think we should definitely just start moving images into the BattleInfo table as I have suggested and forget about the old table. NeoEva88 09:54, 8 Jul 2006 (CDT)

I was liking this tmeplate as well, and i think it would do great in replacing the old tables i've been using (smaller code to type and such ;) ). And on image use: for all characters that can be challeged/have been part of the battledome, they will have two images. One as the intro picture at the top, and the image in the template table in the "Battledome" section, which will contain battledome information and quotes. Sound good? --Jacob 13:10, 8 Jul 2006 (CDT)

Ok, I saw the proposed new layout on the Cave Chia and I've got one question and some suggestions. First, what should we do with opponents that have large pictures, but small articles? (ex. Giant Ghostkerchief) For the Giant Ghostkerchief I think the solution is simple, use only one image. The Giant Ghostkerchief is really notable only as a Battledome Opponent, and so a single picture in the Battledome template will do. However, for other opponents such as the Pant Devil or The Esophagor other images will be used also. (Gallery of Evil images, etc.) NeoEva88 16:44, 8 Jul 2006 (CDT)

Option #10[edit]

{{{Image}}}
{{{Name}}}
Difficulty: {{{Difficulty}}} Starting HP: {{{StartingHP}}}
Arena: {{{Arena}}} Released: {{{ReleaseDate}}}
Status: Unknown Challenger ID: {{{ID}}}
Found by: {{{FoundBy}}}

This revision brings in an tenth parameter for setting the colour of the border - the idea is that the border colour corresponds to the arena the challenger is from. If unspecified (for backwards compatibility, mainly) it'll default to the battledome red. Basically, at the end of the template, include "island", "battle", "tyrannian", "water", "snow", "space", or "stone" (without quotes). For example,

{{BattleInfo |The Snowager |[[Image:Snowager.gif]] |October 23, 2001 |650 |700 |65 |Ice Arena |Getting attacked by the Snowager while trying to awake him. |Snowager is an ancient ice worm from the Neopian Ice Caves. It breathes frost, and is incredibly greedy, sleeping all day on its pile of treasure. |snow}}

--Macbeth 01:12, 16 November 2009 (UTC)

And I like it. This is the wonder of stopping by and not knowing what happened for weeks. I get surprised by something pretty. :D --Jacob 16:43, 31 December 2009 (UTC)

Changing Format[edit]

Hey y'all. I'm changing the format of the battle info again. I find the colored borders really confusing. I always have to look up which color cooresponds to which arena. As such, I explicitily stating the arena in the information. Also, I am removing the "Steal" item in the table because I plan on listing ALL the weapons in the order than they are stolen for each opponent. (See Advisor Broo to see what I mean.) Sorry about editing with out explaining Macbeth, I was hoping to create an example before I talked about it.- Emerald Osprey 22:24, 28 November 2010 (CST)

Not at all, be bold and all. It'd be easy to do both the border and the arena: entry, though - have both read from the same variable. The colour coding is how the dome is identified in the 1-player challenge list, which was why it was included before. --Macbeth 22:41, 28 November 2010 (CST)
That's a good idea acutally. I have one problem though. Where the heck is the .css code for the battledome class stored? I can't find it for the life of me. :/ -Emerald Osprey 07:31, 29 November 2010 (CST)
Ha! I finally found it. It's on MediaWiki:Common.css. Dur. I feel silly for not looking there earlier. :P -Emerald Osprey 07:52, 29 November 2010 (CST)
That's right. The class was called as class="{{{8|battle}}}dome". If option 8 wasn't specified, it would default to 'battle', so it would read class="battledome". If it was set, say, to stone, it would read class="stonedome".
You can say, then, class="{{{6|battle}}}dome" at the top, and then later, in the arena row, '{{{6}}}' again. Then, the sixth option will both change the class and appear in the arena row. --Macbeth 16:06, 29 November 2010 (CST)
The one problem that I have with that is that the Arenas themselves are inconsistantly named. I want to keep the arena names the same as they are on this page. But with inconsistnat arena names like "Battledome" "Water Arena" and "Stone Dome", I can do that with the setup you mentioned. It looks like spaces are allowed in .css class names though, so I'm going to try to change the class names to "Water Arena", "Stone Dome", etc. and see if that works. If not, I'll revert it. Be bold, right?-Emerald Osprey 19:46, 29 November 2010 (CST)
I don't think spaces are allowed in class names. You'd have to escape them if they were, anyway, because to go on a tangent for a moment...
The attributes your specify in CSS must be associated with particular, specific HTML elements. The style sheet
p {background-color: rgb(0,0,255);}
will make the background of every paragraph tag blue. There are three (and a half) ways to be more specific about which paragraphs are effected.
You can either have the css effect the one element on the page with a specific id (#intro ...), all those elements with a certain class (p.blue is all paragraphs with the class blue, .blue is any element with the class blue - that's the half I mentioned), or an element in other elements: div#text p is every paragraph tag inside a division with the id of text, div div table tr is every table row inside a table inside a div inside a div.
Incidentally, spaces in the class call (i.e. <p class="battle dome">) are valid, but is parsed as 'this p is a member of "battle" AND a member of "dome"', not 'this p is a member of "battle dome"'. --Macbeth 07:17, 30 November 2010 (CST)

16th November 2013 revision[edit]

This is a more compact design I've been working on on and off for ages (see User:Macbeth/Battledome). This version doesn't have a section for hp gain per win, as that mechanic has been removed in the new Battledome, can display a description if present (i.e. older challengers), and has a section at the bottom where battle images can be displayed (this was going to be done automagically but that's a headache and they've changed where all the images are for the new battledome).

So that it won't break for those challengers that have hp gain per win in them already, option six is still hp gain per win but the template ignores it. A dummy option six will have to be included for new challengers until/unless we revise all existing challengers. Many of these options can now be specified by name as well (i.e. 4= or difficulty=).

Difficulties (speaking of) and starting HPs can now be displayed with Template:Dif, which will sort out the red/orange/green colours for you.

Hope that's all as clear as mud, --Macbeth 21:40, 16 November 2013 (UTC)

I will also be adding a switch so that the old arena names (e.g. Island Arena) will automatically convert to new arena names (e.g. Pango Palladium). Bug me if I forget to do this! --Macbeth 20:14, 17 November 2013 (UTC)