Template talk:Spindata/GO

Catch rate, escape rate, etc.

There's coding for this that people have found, right? Shouldn't we have that listed too? Nutter Butter (talk) 20:13, 8 August 2016 (UTC)

Max CP (Lv 40)

Suggest pls add info Max CP (Lv 40) in template Tomarzig (talk) 04:50, 9 March 2017 (UTC)

Attack power, charge bars

Maybe power of attacks, and charge moves... Shouldn't they have a charge bar info? Kubson302 (talk) 12:10, 9 April 2017 (UTC)

That's on the moves' pages. glik^glak 11:31, 9 April 2017 (UTC)

Thanks for explaining

Replace Egg Distance field

Egg Distance in this context doesn't seem that helpful since Ninantic is frequently changing whether or not a Pokémon can even hatch from an egg. And the vast majority of Pokémon have "N/A" for that field anyways. Better use of that space could be:

• Base catch rate
• Flee rate
• New Attack cost

(Might even want to add a note to denote STAB in bold and legacy moves in italics, but that's not as important.) TehPerson (talk) 01:44, 18 January 2019 (UTC)

Update suggestion

Due to new stuff being added like the New Attack Cost, and seeing how fields like Egg Distance are too fast-changing to be species-relevant, I propose an update to the template, which I put in User:TehPerson/Spindata/GO. Here's what it would look like:

Pokémon GO HP Atk Def ? ? ? Max CPLv. 40 Max CPLv. 50 ??? ??? Buddy Distance 20 km New Attack Cost 100,000 + 100 Encounter Base capture rate 30% Base flee rate ?% Dodge type ? ? ? ? Fast Attacks Thunder Shock Charged Attacks   Evolution N/A

Pokémon GO HP Atk Def ? ? ? Max CPLv. 40 Max CPLv. 50 ??? ??? Buddy Distance 3 km New Attack Cost 10,000 + 25 Encounter Base capture rate 20% Base flee rate 10% Dodge type ? ? ? ? Fast Attacks Vine Whip, Tackle Charged Attacks   Evolution

It adds the cost for a new attack along with base catch rate and flee rates, and put in the type icons as well. TehPerson (talk) 17:07, 21 January 2019 (UTC)

I like this, and while it does deal with what I think is currently the main problems with the current template (listing Egg distances and not listing New Attack costs), you haven't provided examples of how it addresses my next two issues with it: Displaying legacy and special moves, and displaying branched evolutions (e.g. Poliwhirl). Could you provide examples of how those would look?

Also, I'm not sure types are necessary in this template, since they're always the same as the core series. --SnorlaxMonster 23:51, 25 January 2019 (UTC)--SnorlaxMonster 23:51, 25 January 2019 (UTC)

Oh I have a simple idea for legacy moves. Like how the core series move list italicizes, bolds, etc certain moves, we can just do that on the move list as well, and leave a footer note saying "Bold moves denote stab, † denotes Legacy moves..." (whichever convention you prefer and I'll put it in the template).

And as for branched evolution, see the Poliwhirl, Slowpoke, etc pages as they are. I already re-formatted those using the current templates.

Listing the type icons under the Pokemon sprite is just an aesthetic thing, since I added a new row, I figured we need something nice looking to fill the space. TehPerson (talk) 16:52, 27 January 2019 (UTC)

Automatic way to update all stats

Almost all the stats for the older Pokémon on the mainspace are grossly outdated, and after manually editing a few pages, I realize that updating the stats page-by-page isn't humanly efficient. Instead, I made a sort of "lookup table" for the stats:

• User:TehPerson/GO HP
• User:TehPerson/GO Attack
• User:TehPerson/GO Defense

I have already fully tested the template, even when used within other templates, here.

Usage

To get the stat for a specific Pokémon, like Bulbasaur, simply type in the dex ID you would for Template:MSP

{{User:TehPerson/GO HP|001}} → 128

It also uses the same naming convention for alternative forms, so if you need stats for Alolan Raichu, simply type 026A instead of 026:

{{User:TehPerson/GO Attack|026}} → 193

{{User:TehPerson/GO Attack|026A}} → 201

I'm not going to continue updating the pages one-by-one, and it doesn't seem like anyone else wants to either. These lookup templates takes me only seconds to update, in case Niantic puts changes into the gamemaster file. And if any of the admins want, I can share the spreadsheet I use to parse the gamemaster file into these templates. (It's basically just a copy-paste operation)

TehPerson (talk) 23:57, 5 February 2019 (UTC)

Using a lookup table like this would be a huge use of parser functions which we've been trying to limit the use of since they can only be used a certain amount on every page. We are investigating better ways to display this information but for now we haven't found anything that isn't parser-intensive.--MisterE13 07:56, 6 February 2019 (UTC)

What specifically is the limit on it? (I haven't been able to find anything specific about it.) I might be able to make a work-around it to reduce the overall number of search operations. TehPerson (talk) 18:15, 6 February 2019 (UTC)

On another note, if it helps, I can have the parsers divided up by Region, so that it reduces the operations by ~4. I was also able to fit every entry, using these parsers, onto my entire list of GO stats, which has nearly 500x the parsers we would need to use for one page. TehPerson (talk) 20:06, 6 February 2019 (UTC)

There doesn't seem to be a way to find out what the actual limit is but we've hit it on pages before and fixing it then became quite the emergency. This is especially relevant with species articles which are already pretty complex and are supposed to be Bulbapedia's flagship resource. Lookup tables of any kind are never really going to be the solution here since even breaking them up won't change the number of parser calls in a significant way.--MisterE13 08:14, 7 February 2019 (UTC)

If that's the case, the only alternative I can think is writing a web-crawling bot to automatically update the pages one-by-one whenever a new update (which is somewhat frequent in PoGO) comes along. But that would be something only admins should handle. Otherwise, find someone who has too much time on their hands. :\ TehPerson (talk) 17:08, 7 February 2019 (UTC)

Another update suggestion

This is a v2 that I made, but is incredibly ambitious, found here (along with thorough documentation that you can copy-paste to use).

Example

Pokémon GO     Stats Range At Lv. 20 At Lv. 40 HP: 207 123 - 132 163 - 175 Attack: 109 65 - 74 86 - 98 Defense: 98 59 - 68 77 - 89 CP: 554 - 700 969 - 1226 Buddy Distance: 3 km Base Capture Rate: 50% Flee Rate: 10% New Attack Cost: 50,000 + 50 Evolution Cost: ← 50 ← 50 + Fast Attacks Gyms & Raids Trainer Battles Type Move Energy boost Power Energy boost Power Water Gun +5 5 +3 3 Confusion +15 20 +12 16 Charged Attacks Gyms & Raids Trainer Battles Type Move Energy cost Power Energy cost Power Water Pulse User:TehPerson/Energy bar-50 70 User:TehPerson/Energy bar-60 70 Psyshock User:TehPerson/Energy bar-33 65 User:TehPerson/Energy bar-45 70 Psychic User:TehPerson/Energy bar-100 100 User:TehPerson/Energy bar-70 100 Struggle* 0 35 User:TehPerson/Energy bar-100 35

This would basically make our GO information on-par with that of other online sources. It has a format to capture multiple evolution (albeit hard-coded, but that's already the case anyways) and a detailed movelist to denote legacy moves, if any.

Other stuff I might be able to include:

• The bottom row can be utilized to add (optional) notes like "Raid only", etc.
• Stat ranges for Power Up level 30, wild Pokemon range (I might need to add some sort of note to clarify that it's Power Up level, not Trainer level).
  • Level 20 was chosen as a max Egg range, and lv 40 simply as a max level range.

TehPerson (talk) 05:51, 23 February 2019 (UTC)

Yet another update proposal

This is a version that allows for alternate forms to be displayed (up to 27). The "Other forms" is expandable. Also, stat ranges for Power Up Lv. 30 is also added.

User:TehPerson/Spindata/GO3

TehPerson (talk) 20:43, 18 March 2019 (UTC)

Template Update Proposal - Previews

I created the following to show what my updated proposals would look for all Pokémon, using the most up-to-date data, grouped based on evolutionary family and ordered by region:

• Kanto
  • Bulbasaur - Oddish
  • Paras - Seel
  • Grimer - Jynx
  • Electabuzz - Mew
• Johto
  • Chikorita - Heracross
  • Sneasel - Celebi
• Hoenn
  • Treecko - Electrike
  • Plusle - Absol
  • Snorunt - Deoxys
• Sinnoh
  • Turtwig - Gible
  • Lucario - Arceus, Meltan

I hope this would help better visualize what a change this drastic would look on the mainspace, for all possible cases. TehPerson (talk) 16:30, 15 April 2019 (UTC)