Template talk:Trainerentry

From Bulbapedia, the community-driven Pokémon encyclopedia.
Revision as of 20:22, 3 November 2011 by Chosen (talk | contribs) (→‎ColoXD rematch redux: new section)
Jump to navigationJump to search

Single or double battles

What about trainers that may be battled either in single or in double battles?Piotr mil 15:41, 12 September 2008 (UTC)

If they are doubled up with another trainer, an example I've done is on Route 115, I've simply taken off the trainerdiv between the two, and added a small comment underneath both of their winnings.     -–<×vVvvv τλικ to ς1tHςι3r ^^vVv×>–- 00:01, 10 January 2009 (UTC)

Expression error: Unrecognised word "span"

The new trainer exp template is causing some problems with parsing when the level is specified as something like 19{{tt|*|Lv.60 in rematch battles}}, which can result in something like:

Trainer Pokémon
Gentleman Jeremy
Gentleman Jeremy
Reward: $3800*
Chatot Chatot Lv.19*
No item
Trainers with a Vs. Seeker by their names, when alerted for a rematch using the item, may use higher-level Pokémon.


I noticed this on Route_212#North_(clear)_area, but the issue could arise in many other places. How should we resolve it? Note that some trainers' Pokémon may level up more than once, and to different levels in different games. For example, this Jeremy guy goes from 19 to 40 to 60 in DP, but levels up differently in Platinum, ending up around 55 or something (don't have the cartridge with me to check). — Laoris (Blah) 17:35, 9 January 2009 (UTC)

The problem is simply because the trainerexp template uses the level parameter as a number in its calculations, and of course once you put text in, in this case the tt template was used, which uses span tags, then the resulting errors will occur as the text cannot be recognised as numerals thus screwing up the calculation. The only way to avoid this is if comments on rematch battles or anything added to the level parameter are not included. Besides, these Trainer templates should be used to show initial encounters only.
If rematch battle information needs to be included more often, I'll ammend it so comments can be included harmlessly.     -–<×vVvvv τλικ to ς1tHςι3r ^^vVv×>–- 23:34, 9 January 2009 (UTC)
I see. I think it would be a good idea to incorporate rematch data somehow when it is available. Is there a parser function that just lets us grab the numerical part of the level parameter and cut off the tt part? — Laoris (Blah) 23:44, 9 January 2009 (UTC)
Adding one more parameter could be easy... ish. TTEchidna 23:45, 9 January 2009 (UTC)
Not that I know of, otherwise I would have definitely used it. I'll check Wikimedia whether there does happen to be one but I doubt it, and chances are it's probably not installed here.
Yea it would be easy... for one row of Pokémon. The more Pokémon there are, the longer it stacks up, then imagine what the mess would be like, with multiple comments everywhere...     -–<×vVvvv τλικ to ς1tHςι3r ^^vVv×>–- 00:01, 10 January 2009 (UTC)

Edit Request

Bigger font size of Trainer Class; Trainer Classes with definite gender such as Swimmer♂, when changed into smaller font size and bolded, becomes Swimmer♂, the gender sign becomes unclear.. Or is it just me? Ҝəυzø8 14:47, 18 February 2009 (UTC)

Japanese names

Well, what I was trying to do was put a field for Japanese names with the formatting seen there. But for some reason it shows up on everyone and it can't be changed...so...help, please? D:—Loveはドコ? (talk contribs) 09:09, 30 April 2009 (UTC)

I'm on it. — THE TROM — 09:19, 30 April 2009 (UTC)
Well... with the appropriate number of pipes it should work now. It's rigged up the the 36th and 37th variables... which will be a problem, as I'm sure you can understand. The two options here are putting in a whole heap of blank params, or redoing the numbering inside the template. But if we redo the numbers, all the entries will be wrong. This would be entirely possible to do, but would require mass editing as soon as possible. I'm not sure how to do it otherwise, the best bet is to let TTE take a peek when he's online next. I'm sorry I can't help more at the present stage. — THE TROM — 09:27, 30 April 2009 (UTC)
Yeah, I was wondering if changing the numbers of all the parameters would work...I didn't want to try because of yeah, mass editing. :\—Loveはドコ? (talk contribs) 09:38, 30 April 2009 (UTC)
Got it! All you need to do is label the parameters within the transcluded template. See here. — THE TROM — 09:44, 30 April 2009 (UTC)
Gah, they still use the example Kenta. D:—Loveはドコ? (talk contribs) 09:52, 30 April 2009 (UTC)
Huh? On the Solaceon page? That's what you put there, so I assumed it was the Japanese name. You can change the default in the template though, if that's what you mean. — THE TROM — 10:12, 30 April 2009 (UTC)
Er, no. The example used here is Kenta. Fuyuki is actually filled in on Solaceon Ruins, but it's displaying Kenta. I'm sorry but no, the template doesn't work yet.—Loveはドコ? (talk contribs) 13:46, 30 April 2009 (UTC)
YAY—Loveはドコ? (talk contribs) 02:08, 1 May 2009 (UTC)
Yeah, completely my fault at the end there. But it's all good coz I made it fixed. :D — THE TROM — 05:42, 1 May 2009 (UTC)

Possible improvement

<includeonly>[[Category:Locations with trainers who own {{{7|MissingNo.}}}]] [[Category:Locations with trainers who own {{{12|MissingNo.}}}]] [[Category:Locations with trainers who own {{{17|MissingNo.}}}]] [[Category:Locations with trainers who own {{{22|MissingNo.}}}]] [[Category:Locations with trainers who own {{{27|MissingNo.}}}]] [[Category:Locations with trainers who own {{{32|MissingNo.}}}]]</includeonly>

Or something to that extent. Would take 493 edits, but... easy way to find out where you can find a Pokémon for Regional Dexes.--Mew* a.k.a. Prmatt11 was here at 15:48, 17 June 2009 (UTC)

If we can program Botty to make those 493 pages so we don't have to do it, I'd say hell yes. Except with a CAPITAL T ON TRAINERS. TTEchidna 03:57, 18 June 2009 (UTC)
I'll do it!--Mew* a.k.a. Prmatt11 was here at 14:39, 20 June 2009 (UTC)
Wait, nevermind. Forgot about the login prob. Lemme ask Politoed.--Mew* a.k.a. Prmatt11 was here at 14:51, 20 June 2009 (UTC)
What exactly are you asking me...? Do you want me to do it? --ニョロトノ666 18:46, 21 June 2009 (UTC)

The new template

It's B.U.T.T. U.G.L.Y. Way too wide and UGLY! It's awful! Was there any need to remake it? I think it was totally pointless. I'm begging to bring the old Trainer template back. This one is totally shithouse. --Maxim 09:37, 17 October 2009 (UTC)

Ummmm... It's exactly the same as the old one, only roundy. What's ugly about it? It looks fine to me. --electAbuzzzz 09:41, 17 October 2009 (UTC)
Way too wide and too rounded. I'd prefer that "Rounded Template Revolution" to never happen. The more unrounded template, the better. That roundedness looks SO forced and unaesthetical. It's out of my taste. --Maxim 09:55, 17 October 2009 (UTC)
I'm sorry Maxim, but that's the way it's been decided. I see no problem with the roundy templates. You're in the minority. We're changing them. ALL of them. --electAbuzzzz 10:48, 17 October 2009 (UTC)
Of course, you and TTE is "majority". TTE himself is, to be honest. The problem is, that I spent a lot of time on putting Japanese names of HGSS trainers under their Trainer Class, now with new templates it loks terribly awkward because the Japanese characters are next to Latin ones. Just look at it. It looks terribly awkward now. So, I must relocate those names back to 36= field just because of some authoritarian autocratic pointless change of a Template. Did the admins ever let the user say what they think about that "Rounded Revolution"? --Maxim 11:33, 17 October 2009 (UTC)
This is not some sort of a private decision. A few templates were altered way way way back, then the community LIKED it. You're the first person I hear say you prefer the templates unrounded. This has been going on for MONTHS now, everyone loves it. The roundy templates look awesome. Seriously, the location of some Japanese characters in the name here is what bothers you? That's easily fixable, and you know it. It's not the issue, and it's not worth getting mad over. --electAbuzzzz 11:46, 17 October 2009 (UTC)
Doesn't change the fact that I hate those templates. The roundedness is just too forced. And the fact that ALL templates are gonna be rounded makes me puke. God. Rounded Character Infobox will be the aesthetical suicide. A few rounded templates are okay. But not ALL. --Maxim 12:00, 17 October 2009 (UTC)
That's your opinion, and your opinion alone. I personally think the new infoboxes look great. And the character infobox is definitely heading for a change, because it currently looks awful. In any case, there's no point in continuing this discussion, all points have been made. As I said, majority thinks the roundy templates are better, and therefore the roundy templates will remain. --electAbuzzzz 12:21, 17 October 2009 (UTC)

Collapse

Is it possible if we make this collapsable just for the walkthrough?--ForceFire 09:05, 5 December 2009 (UTC)

Instructions?

Can someone PLEASE add detailed instructions for this template either here on the talk page, or, even better, as a <noinclude> on the template page itself? Actually, that should be done for EVERY commonly-used template, they are far from self-explanitory to those of us no well-versed in template code, especially the ones with all the variable expressions and switches and all. It’s S.O.P. on Wi- er, “that other wiki”, and while I know and appreciate that we are not them, a few of their ideas and policies, like this one, are very effective and useful and worthy of adoption. --LaprasBoi 15:01, 22 February 2010 (UTC)

See Template:Trainerentry/doc for the documentation. --Minimiscience 14:39, 9 August 2010 (UTC)

Colosseum and XD rematches

As I mentioned on the Trainerfooter talk page, this template too needs to include support for XD and Colosseum rematches. Specifically, parameter 38 needs an value for these games to designate rematches since they don't use items like pokegear, nav, vs. seeker. --PagodaGiftShop 00:39, 5 May 2010 (UTC)

Also, it would be nice if there were some way to designate shadow pokemon using this template. Otherwise, the party template has to be used which is not always necessary since there are lots of insignificant trainers in XD and Colosseum that carry shadow pokemon. --PagodaGiftShop 00:59, 15 May 2010 (UTC)

Late reply. I think that wouldn't be such a bad idea actually. Anyone else want to chime in? ht14 00:57, 29 July 2010 (UTC)

Rematches

I tried to improve this template, so rematch battles would also fit in. The best result I got is this:

Trainer Pokémon
Sailor Ernest
Sailor Ernest
Reward: $1056
Trainer's Eyes/Match Call
First battle
Wingull Wingull Lv.33
Bag Hard Stone Sprite.png Hard Stone
Wingull Wingull Lv.34
Bag Hard Stone Sprite.png Hard Stone
Second Battle
Pelipper Pelipper Lv.35
Bag Hard Stone Sprite.png Hard Stone
Pelipper Pelipper Lv.36
Bag Hard Stone Sprite.png Hard Stone
Pelipper Pelipper Lv.37
Bag Hard Stone Sprite.png Hard Stone
Third one
Pelipper Pelipper Lv.50
Bag Master Ball Sprite.png Master Ball
Swimmer Nolen
Swimmer Nolen
Reward: $272
Tentacruel Tentacruel Lv.34
No item
Trainers with a PokéNav by their names will be registered in the Trainer's Eyes or Match Call function after the first battle, and may have a rematch with the player with higher-level Pokémon.


This table uses my own template, User:Piotr mil/evo2 and its sub-template User:Piotr mil/evo2/table. Notice that the second trainer is made using Trainerentry template, so my template is compatible with your headers and footers. Unfortunately, I couldn't manage to make the inner borders colored in so nice way than in the Trainerentry version.... I couldn;t find the "inner borders style" wiki code.Piotr mil 01:48, 11 August 2010 (UTC)

ColoXD rematch redux

OK, the footer says that a Poké Ball should show up near any trainer in Orre that is rematchable, but there is no option to bring up a Poké Ball under paramameter 38 to add it. Could somebody with mod powers add |Poké Ball|ball|poké|rematch=[[File:Ballfull.png|Rematch]] to parameter 38? - Chosen of Mana 20:22, 3 November 2011 (UTC)