Template talk:MoveInfobox: Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
No edit summary
Line 727: Line 727:


This template should includes lgpe, swsh, and bdsp parameters that contain categories, rather than putting the usable move categories manually. [[Special:Random|<span style="font-family:Tahoma"><span style="color:#696969">'''AKUro?'''</span>]]</span> [[User talk:Akurochan|<span style="color:#010101">あくロ</span>]][[Special:Contributions/Akurochan|<sub style="color:#AEAEAE">ちゃん</sub>]] 02:48, 25 November 2021 (UTC)
This template should includes lgpe, swsh, and bdsp parameters that contain categories, rather than putting the usable move categories manually. [[Special:Random|<span style="font-family:Tahoma"><span style="color:#696969">'''AKUro?'''</span>]]</span> [[User talk:Akurochan|<span style="color:#010101">あくロ</span>]][[Special:Contributions/Akurochan|<sub style="color:#AEAEAE">ちゃん</sub>]] 02:48, 25 November 2021 (UTC)
== Super Contest Shows ==
It looks like there isn't a section for Super Contest Show move information (from BD/SP). Ideally that would include the number of Hype Points and a description. [[User:Spoonlord57|Spoonlord57]] ([[User talk:Spoonlord57|talk]]) 07:31, 17 January 2022 (UTC) ''SpoonLord57''

Revision as of 07:31, 17 January 2022

Move Infobox Parameters
n Number of move1
name English name
jname Japanese name
jtrans Japanese name translated
desc Description2 and notes.
type Type of move
basepp Base PP
maxpp Maximum PP (160% of base)
power Power
accuracy Accuracy (don't append %)3
priority Priority 4
category Contest category5
appeal Points gained in contests
jam Points negated in opponents
cdesc Additional effects in contests6
pokeforurl Key for accessing PokéFor's Movedex7
footnotes Footnotes8
  • 1: The number is not displayed, but may be useful when creating automatic cross-references. Do not prefix zeroes.
  • 2: The description is found in the battle moves panel.
  • 3: Give 99.6% as 100%.
  • 4: For moves that have priority not equal to 0.
  • 5: One of Cool, Beauty, Cute, Smart or Tough.
  • 6: The additional effects are described in the contest moves panel.
  • 7: The PokéFor Movedex key is usually the lowercase of the English name, substituting + for spaces.
  • 8: Leave blank if no footnotes.
Move properties
touches Does the move make contact with the opponent?
misses Can the move miss?
snatchable Is the move Snatchable?
magiccoat Do Magic Coat and Magic Bounce protect against this move?
useskingsrock Does using King's Rock and this move cause the opponent to flinch?
sound Is this move considered a sound move? (See Soundproof)

All values take either a yes or no (case-sensitive).

Below are the values for the target parameter, and the text that will be shown in the infobox for that value. "Any" means that a single target may be chosen from among the targets in range. "All" means that all targets in range are hit. "Adjacent" refers to a Pokémon's position in Double Battles or Triple Battles with respect to the user of the move.

Valid target values
any May affect anyone but the user
anyadjacent May affect anyone adjacent to the user
all Affects all Pokémon on the field
alladjacent Affects all Pokémon adjacent to the user
allothers Affects all but the user
foes Affects all foes
adjacentfoes Affects all adjacent foes, but not allies
foe May affect any foe, but not allies
adjacentfoe May affect any adjacent foe, but not allies
self Affects the user
allies Affects all allies
ally Affects an ally
adjacentally Affects an adjacent ally
team Affects the user and all allies
selfadjacentally May affect the user or an adjacent ally
twoteam Affects the user and one ally
(other values) Does not affect any Pokémon


Example

Volt Tackle
ボルテッカー Volteccer
Volt Tackle IV.png
[[File:|center]]
Type  Electric
Category  Physical
PP  15 (max. 24)
Power  120
Accuracy  100%
Priority  {{{priority}}}
Target
Foe Foe Foe
Self Ally Ally
May affect any foe, but not allies
Availability
Introduced  Generation III
Condition  Cool
Appeal  6 ♥♥♥♥♥♥
Jam  0  
User will be more easily startled afterwards.
Condition  Cool
Appeal  2 ♥♥
Earn +3 if the Pokémon that just went hit max Voltage.
Condition  Cool
Appeal  0  
Jamming  0  
{{MoveInfobox|
n=344 |
name=Volt Tackle |
jname=ボルテッカー |
jtrans=Volteccer |
desc=The user electrifies itself, then charges at the foe. It causes considerable damage to the user as well. |
gameimage=DPVolttackleani.gif |
type=Electric |
damagecategory=Physical |
basepp=15 |
maxpp=24 |
power=120 |
accuracy=100 |
bdesc=User is hit by recoil that is equal to one-third of the damage inflicted. |
category=Cool |
appeal=6 |
jam=0 |
gen=III|
cdesc=User will be more easily startled afterwards. |
appealsc=2 |
scdesc=Earn +3 if the Pokémon that just went hit max Voltage. |
pokefordex=volt+tackle |
touches=yes |
protect=yes |
magiccoat=no |
snatch=no |
brightpowder=yes |
kingsrock=yes |
flag7=no |
flag8=yes |
sound=no |
footnotes= }}

What this still really needs

--- 1) If move is a TM/HM, and if so what # in each version.
2) Generation of Creation (I, II, or III)
3) Perhaps: % of causing side-efffect/what side effect it has.

Evkl 04:31, 25 Feb 2005 (UTC)

In addition

How about adding a box that shows what generation that move was introduced in? That's a fairly valuable piece of information for anyone planning movesets for the older generation games.

That's what I meant by Generation of Creation--guess I wasn't specific enough. ~Ev


Here's an excerpt from DarkBot:

[15:35:02] <DarkBot> [NUMBER] 289
[15:35:02] <DarkBot> [NAME] SNATCH
[15:35:02] <DarkBot> [DESCRIPTION] Steals the effects of the move the foe uses next.
[15:35:02] <DarkBot> [TYPE] DARK
[15:35:02] <DarkBot> [BASE PP] 10
[15:35:02] <DarkBot> [BASE DAMAGE] 0
[15:35:02] <DarkBot> [BASE ACCURACY] 100%
[15:35:02] <DarkBot> [TARGET] Last opponent who moved
[15:35:02] <DarkBot> [EFFECT] If the opponent is using a move to boost itself, cancels the opponent's turn and the user uses the move instead, uses a priority modifier
[15:35:02] <DarkBot> [PRIORITY] This move by default goes first (4)
[15:35:02] <DarkBot> [TOUCH] No [CAN MISS] No [CAN MAGIC COAT] No [CAN SNATCH] No [USES KING'S ROCK] No [SOUND MOVE] No

All of this information is important and should be shown somewhere, either in the infobox or elsewhere on the move pages.

Jshadias 21:37, 25 Feb 2005 (UTC)

Picture

Should we include a picture with each move? Just a thought. Also, the stuff like touches and misses is now covered under the Template:MoveProperties.

King's Rock

I don't know how to change this, but when it says whether or not to use the King's Rock, the link should be the following, not whatever it is now:

http://bulbapedia.bulbagarden.net/wiki/Items#King.E2.80.99s_Rock

Evin290 23:51, 28 June 2006 (UTC)

Better question... why in the world are there so many weird apostrophes on that page? It's the difference between ’, which I think is what some programs like word might use by default for apostrophes, and ', which is what the text editors on Bulbapedia use when you hit the apostrophe key. I mean, I think, anyway. You can't even tell 'em apart unless you look at them in the Bulbapedia's text editor thing whatever I'm typing in now. Let me see if I can do something about that. --Pie 00:08, 29 June 2006 (UTC)
Okay. Are things fixed now? =D --Pie 00:13, 29 June 2006 (UTC)

Cool, Smart, Tough, etc. Images

Do you think we might be able to get the little coloured box images for the Contest Categories? They're a nice little aesthetic touch, I think. ~ Megalomania 23:23, 31 March 2007 (UTC)

External MoveDex Links

I'd like to inquire as to why the Serebii.net Attackdex's are excluded from the links. Its included on the Pokémon so why not here? --Serebii 20:20, 24 November 2007 (UTC)

Why aren't we linking to Serebii's Attackdex? Is it just because Serebii's URL's don't have spaces in them for multi-word moves? Aren't there string manipulation wiki functions we can use to remove spaces from a parameter? Same question for the Legendary Pokémon URLs–is there no way to just replace spaces with +'s instead of requiring another parameter to the template? — Laoris (Blah) 21:49, 24 November 2008 (UTC)

Mystery Dungeon Data

The following should be added to the infobox to better reflect data in Mystery Dungeon:

  • PP (this is typically different from the main games)
  • Accuracy (this is typically different from the main games)
  • Critical (base critical hit probability)
  • Target Type (one of the following)
    • Enemies only
    • Player and allies only
    • Any Pokémon
    • User
    • User, then foe
    • All except user
    • All allies except user
  • Range Type (one of the following)
    • Tile in front
    • 3 tiles diagonally and in front
    • 1-tile range
    • All in room
    • Up to 2 tiles ahead
    • All on floor
    • User
    • Tile in front, cuts corners
  • Flags
    • affected by Magic Coat
    • affected by Snatch
    • affected by Muzzled status
    • does not damage Frozen Pokémon
    • affected by Taunted status
    • affected by Ginseng

This is needed to better improve Wide Slash and Vacuum-Cut. KelvSYC 06:30, 3 May 2008 (UTC)

So I'm thinking...

Maybe we ought to add what TM it is. (about time, too) TTEchidna 20:49, 23 July 2008 (UTC)


{{#if: {{{tm1|}}}|*[[TM{{{tm1}}}]] in [[Generation I]]}}
so i think is better. (you dont need 2 parameters for one thing)
{{#if: {{{tm1|{{{tm2|{{{tm3|{{{tm4|{{{hm1|{{{hm2|{{{hm3|{{{hm4|{{{mtdp|{{{mte|{{{mtc|}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}||*Not a [[TM]], [[HM]], or [[move tutor]] move.}}
and this should check the na parameter--Hanmac

PS:

{{#switch: {{{protect|}}}
| yes=* '''Affected by {{m|Protect}}''' 
| no=* Not affected by Protect 
}}

is this better for the extra values?

|- style="background: #{{{{{damagecategory}}} color}}; {{#ifexpr: {{{spm|0}}} = 1 | display: none; }}" 
! <span style="color:#{{{{{damagecategory}}} textcolor}}">[[Damage category|Category]]</span>
| [[{{{damagecategory|Uncategorized}}} move|<span style="color:#{{{{{damagecategory}}} textcolor}}">{{{damagecategory|Uncategorized}}}</span>]]
there must be a template for !, | and |- because of Template:??? textcolor
i think so:
{{#ifexpr: {{{spm|0}}} != 1 | 
{{!~}} style="background: #{{{{{damagecategory}}} color}}" 
{{~}} <span style="color:#{{{{{damagecategory}}} textcolor}}">[[Damage category|Category]]</span>
{{!}} [[{{{damagecategory|Uncategorized}}} move|<span style="color:#{{{{{damagecategory}}} textcolor}}">{{{damagecategory|Uncategorized}}}</span>]] }}

and

{{#if:{{{gen|}}}|[[Category:Generation {{{gen}}} moves]]}}
{{#if:{{{damagecategory|}}}|[[Category:Generation {{{damagecategory}}} moves]]}}
so Vacuum-Cut (move) an other work corect
Well, Zhen said we ought not use too deeply-nested statements... I'll ask him. TTEchidna 20:18, 28 July 2008 (UTC)

Edit request

I'm requesting an edit. Please make it possible to choose a size for the image. This is why. --Baby G (talk to me) (see my edits) 00:37, 29 September 2008 (UTC)

as noted on my page, if i go to that page, Scratch, it looks fine. it might just be your browser or something. that being said, its a different image for me...? -- MAGNEDETH 00:50, 29 September 2008 (UTC)
Sorry Baby G, your image quality is appalling. i cant allow that. -- MAGNEDETH 00:55, 29 September 2008 (UTC)
Animations are supposed to be used in place of regular screenshots. --Baby G (talk to me) (see my edits) 01:07, 29 September 2008 (UTC)

Move targets

I really think this template should have a field that specifies the targets of the move in a double battle (one target, both foes, user, all but user, random foe). Some of the non-single-target moves say so in their article, but some don't and it's not standardized. If we don't put it in this template, we should at least devise a standardish way to specify it in the article. — Laoris (Blah) 16:45, 25 November 2008 (UTC)

Contact

There is now an article on contact. The infobox mentions contact but does not contain a link to the article contact. Should this be added to the info box? -TIMMY 11:17, 12 December 2008 (UTC)

PP

Please change the [[PP]] on this template to {{PP}}. PP is a redirect to Power points, and the PP template links automatically to Power points with PP text. UltimateSephiroth (about me · chat · edits) 19:02, 1 January 2009 (UTC)

A stack of Edit Requests

As well as BUMPing the three above, could we also color the text of the "Damage Category" link to match the text beside (ie with a switch code or something) coz it's illegible as is. — THE TROM — 22:14, 31 January 2009 (UTC)

not done, done, done, and done. the move targets would have to be coded into it, adn i have a feeling TTE is working on a new template, so, itd be best to add it in then. the new template is also getting a "Gen Introduced" spot i think. -- MAGNEDETH 22:24, 31 January 2009 (UTC)
Thanks deth. Er, it's got an intro slot, but whatever. Moz-borders and colors will be awesome, I assume that's what's coming! — THE TROM — 22:28, 31 January 2009 (UTC)
of course! they will be pretty. -- MAGNEDETH 23:15, 31 January 2009 (UTC)

Move properties

Shoudn't 'Move properties' list (not/affected by Magic Coat, Protect, etc.) be left aligned? Currenty it is centered and that's not really help reading. Tenno Seremel 16:50, 4 February 2009 (UTC)

That issue should now be fixed. Thanks for pointing it out! - Kogoro | Talk to me - 17:07, 4 February 2009 (UTC)

Category:Moves in need of a screenshot

Since manually categorizing all the moves that fall into the category will take too long, could an admin edit it so that the game image area reads:

{{#if: {{{gameimage|}}} | [[Image:{{{gameimage}}}|{{{gameimagewidth|240px}}}|center]] | <includeonly>[[Category:Moves in need of a screenshot]]</includeonly> }}

?

~ overgrownsol 01:50, 4 March 2009 (UTC)

Er, well, I suppose that request is void now. Never mind then. ~ overgrownsol 01:51, 4 March 2009 (UTC)

Help for target parameter

any, may hit any of the three

  • Can hit foe 1
  • Can hit foe 2
  • Can hit ally
  • Will not hit self

all, affects all participants

  • Will hit foe 1
  • Will hit foe 2
  • Will hit ally
  • Will hit self

allothers, affects all but user

  • Will hit foe 1
  • Will hit foe 2
  • Will hit ally
  • Will not hit self

foes, affects both foes

  • Will hit foe 1
  • Will hit foe 2
  • Will not hit ally
  • Will not hit self

foe, affects one foe

  • Can hit foe 1
  • Can hit foe 2
  • Will not hit ally
  • Will not hit self

self, affects self

  • Will not hit foe 1
  • Will not hit foe 2
  • Will not hit ally
  • Will hit self

ally, affects ally

  • Will not hit foe 1
  • Will not hit foe 2
  • Will hit ally
  • Will not hit self

team, affects team

  • Will not hit foe 1
  • Will not hit foe 2
  • Will hit ally
  • Will hit self

By the way

This is according to the game. Yeah that means heading to the Hotel Grand Lake and battling in the Seven Stars Restaurant. Sorry guys.

AND YES IT DOES MATTER THE DIFFERENCE BETWEEN "ANY" AND "ALLOTHERS". Thunderbolt is "any", Earthquake is "allothers". Any questions? TTEchidna 09:28, 18 April 2009 (UTC)

Numbers

Can we add the numbers into the number articles (such as 001)? ht14 17:33, 23 May 2009 (UTC)

As in, move number? We could, but at the same point, how many people search for a move based on it's number? I don't think that number would be more than one or two people, at most. -- Jïörüjï Ðērākō.>.cнаt^ 10:55, 25 May 2009 (UTC)

Paunch!

This template notes whether a move is a sound-based move or not. Can the same be added for punching moves? Yenreb 10:03, 8 December 2009 (UTC)

The only reason you need punching moves is for Hitmonchan's Iron Fist ability, which itself has a list of punching moves on it (out of the couple hundred moves, fifteen are punching moves, and a majority of them are named "____ Punch".
As it is, I don't think it's quite necessary to add a whole new line to the already large infobox for punching moves. If they were harder to find (like sound-based moves are), or if there were more of them, maybe. -- Jïörüjï Ðērākō.>.cнаt^ 17:29, 8 December 2009 (UTC)

Suggestion

Any way to merge some of the AbilityInfobox and TownInfobox styles and put it on here? What I mean is, add flavor text per generation, provide screenshots from each generation, etc? I'm not that great with templating and began attempting it, but it's not up to my/BP's standards... See this for a vague idea of what I'm talking about. The latter has yet to be implemented so as not o crowd the image section, but I think it'd be pretty successful. ht14 22:53, 24 May 2010 (UTC)

Maybe add the use of the RouteInfobox style where there are small images? ht14 16:38, 30 August 2010 (UTC)

Edit request

Can we make the default image scale none at all? So if the parameter is left out, the image is shown as its actual size? Most screenshot are 256 × 192 pixels, and even png thumbnails don't look too flash. たかはり 10:13, 30 August 2010 (UTC)

It's now optional. If the image isn't stupidly big, you can remove the scaling parameter from some of the pages. —darklordtrom 11:07, 30 August 2010 (UTC)

Given the Triple Battle layout, wouldn't it make more sense to have the user in the Triple Battle grid at the lower left or lower right rather than the lower center? If it's it the lower center, it doesn't show if a Pokémon can hit a foe's Pokémon on the other end of the battle. Giratina's Embodiment - Please don't hurt us... 16:55, 21 November 2010 (UTC)


Brightpowder Flag

This should be that it can be copied by Mirror Move. Why is this listed as Brightpowder? If Aerial Ace is being listed as rolling for accuracy (which is the same thing as the brightpowder flag), then something is probably wrong. Could someone please fix this because this error is pervasive and embarrassing. surskitty 00:19, 12 December 2010 (UTC)

Links

You should at least add the links to Magic Coat and such even if the move isn't affected by them. What if someone saw that a move wasn't affected by Magic Coat and didn't know what it was? --I hide in the dark! 13:33, 11 May 2011 (UTC)

Now someone has to do with Magic Bounce redlink! AKUro? あくロちゃん 06:32, 12 May 2011 (UTC)

Description

I noticed that description differs between generations. Eg. Explosion:

  • II:Very powerful but makes user faint.
  • III:Inflicts severe damage but makes the user faint.
  • IV:(from article)The user explodes to inflict damage on those around it. The user faints upon using this move.
  • V:Unknown. Anyone has info about it?

or Selfdestruct:

  • II:Powerful, but makes the user faint.
  • III:Inflicts severe damage but makes the user faint.
  • IV:(again from article)The user attacks everything around it by causing an explosion. The user faints upon using this move.
  • V:I don't know it. Again.

See Gen II and Gen III there.

(note - That stuff under Selfdestruct in Gen III is thing informing that Pokémon has Pokérus)

Note that description does not exist in Generation I. Marked +-+-+ 10:30, 24 June 2011 (UTC)

I think that it would be a good idea to separate it from this infobox, and make a separate section of the page where we include them all, like Pokédex entries or item descriptions. --SnorlaxMonster 14:32, 26 June 2011 (UTC)
Sure, why not? Marked +-+-+ 14:35, 26 June 2011 (UTC)

Thrash, Petal Dance, Outrage

Currently the targets for all three of these pages are incorrect, Thrash and Outrage being any foe and Petal Dance Being all adjacent foe. Could somebody with the power to edit this page possibly add an option for any adjacent foe? Also, would a specific page on move targets be a bad idea? I noticed that there's no "Target" page. - Blazios talk 21:46, 7 October 2011 (UTC)

So they specifically can't be targeted at their allies? Werdnae (talk) 02:50, 8 October 2011 (UTC)
They target randomly and can only hit adjacent opponents. - Blazios talk 09:04, 8 October 2011 (UTC)
Fixed. --SnorlaxMonster 13:03, 13 October 2011 (UTC)


Flag8 and Flag7

What is their functions? Are they for a future update, or maybe were used in the past?--Qwilava 15:56, 27 December 2011 (UTC)

Bdesc

When is field bdesc used? Marked +-+-+ 14:17, 6 February 2012 (UTC)

It's not in the template anymore. I think it was an old parameter that was removed. Probably replaced by the "effect" section on pages. --SnorlaxMonster 14:40, 6 February 2012 (UTC)

Target categories

  • Would it perhaps be useful to have this template generate (currently non-existent I think) categories based on moves' targeting type? I was kinda surprised to see this missing so far, and felt it'd help searching for certain kinds of moves. - Tycho 04:35, 29 February 2012 (UTC)
I agree, it would be useful. Added. --SnorlaxMonster 11:55, 2 March 2012 (UTC)
And how about make also categories based on the relation of the move with other effects (Magic coat, snatch, king's rock)? I think it would be useful, since sometimes it's hard to tell if a move is affected by one of that effects or not.--Frikiman 22:28, 11 March 2012 (UTC)
Check any move, it already had that there. :) Frozen Fennec 22:31, 11 March 2012 (UTC)
Yes, it's specified in the infobox of the move, but I was talking about making a category for that kind of effects to ease the search. Let's say, for example, that I want to see which moves are affected by Magic coat. Of course I can look in the infoboxes of every move which ones are affected and which ones not, but it would be infinitely easier if there was a category including all moves that are affected by Magic coat.--Frikiman 15:05, 17 March 2012 (UTC)

Linking

I see the current version of this has a link to Contact and Protect. So why don't Snatch, Magic Coat, and King's Rock have links? Frozen Fennec 12:40, 13 March 2012 (UTC)

Effect move categories

Since it's hard to remember all of the moves which are affected by effects like king's rock or other moves like magic coat or snatch, I think it'd be a good idea use this infobox for making categories based on this effects, something like [[Category:Moves affected by Snatch]] with this, the search for these movements would be pretty easy and nobody would have to look at each move to know if it is affected or not.--Xtr11 (talk) 15:12, 7 February 2013 (UTC)

Mystery Dungeon information?

Could we possibly add Power and Hit Ratio (accuracy) information from Mystery Dungeon to the infobox? ChiefbozX (talk) 20:58, 17 February 2013 (UTC)

Mystery Dungeon info now has its own infobox, Template:MDMoveInfobox, which should go further down the page. Werdnae (talk) 05:24, 18 February 2013 (UTC)
Ok, cool, thanks! ChiefbozX (talk) 06:49, 18 February 2013 (UTC)

Edit request: Contest

Since the contest conditions have been moved from "{{{category}}} Contest" to "{{{category}}} (condtion)", changes should be made in the infobox to reflect this. – Chosen of Mana 10:58, 16 September 2013 (UTC)

Edit request: Screenshots

I've made some Archives edits for Water Shuriken, but I have a problem. Could someone make a third place for the screenshots? Thanks.

Pokéglare (talk) 18:21, 24 December 2013 (UTC)

Edit request

Could someone change the code "Contest categories" to "Contest condition" so it doesn't redirect (on every move page...)? Tiddlywinks (talk) 02:58, 15 June 2014 (UTC)

Links to Smogon movedex broken for renamed moves

Hello.

It would appear that the links to Smogon's movedex on moves that have been renamed are broken, as Smogon uses the original name of the move (e.g. Conversion2 and Faint Attack) while the template here links to the new name (Conversion 2 (broken link) and Feint Attack (broken link). I went through both lists (II-III and V-VI), and all but a single move are affected (Smokescreen still works as it was only a caps change).

I don't suppose the template has a parameter for overriding these links, does it? :)

For what it's worth, as I went through the list, I produced a table of corrected link names... although I'm not sure how best to share it. I can confirm, however, that for all 22 entries in the tables I linked above, a working link to the move on Smogon can be produced by taking the old name, and substituting spaces with underscores. ExpHP (talk) 20:35, 19 June 2014 (UTC)

They should now all be fixed. --SnorlaxMonster 06:47, 21 June 2014 (UTC)
Ah, very thorough! :) I hadn't even noticed until now that the one of the Conversion 2 pages actually did have a space. It's very refreshing to see a video game wiki with such responsive staff. ExpHP (talk) 13:54, 21 June 2014 (UTC)

Parameters for Contest Spectaculars

Now that Bulbapedia is once again unlocked to the majority of users, I would like to start adding information on a variety of moves regarding their effects in Contest Spectaculars. What would be the parameters to do so in the template? It looks like the skeleton of the necessary code is already available (since there seems to be a panel for Contest Spectaculars), but I don't know what parameters change what the panel displays for appeal, jamming, and move descriptions. Are these parameters available yet, and if so, what are they? Superbreeder 08:13, 3 December 2014 (UTC)

  • category6 - Gen VI Contest category, only needed for Gen I-IV moves if their category has changed (such as Beauty -> Beautiful) since Gen IV.
    • The original category parameter can be used for Gen V-VI moves.
  • appeal6 - Appeal.
  • jam6 - Jamming.
  • cdesc6 - Description.
I hope that helps. - Kogoro - Talk to me - 08:21, 3 December 2014 (UTC)

Template edit request - TM/HM Gen VI split

The following TM/HM were split in Generation VI:

I'd request for a new column that shows the move split. Raymond 09:09, 5 December 2014 (UTC)

ORAS tutor moves

Needs mtoras parameter. --Johans (talk) 01:50, 12 January 2015 (UTC)

Underrated post. AKUro? あくロちゃん 10:49, 11 February 2015 (UTC)

Request: Alter a number to allow a larger pool

Could the line: "style="{{#ifexpr: {{{n}}} >= 621 | display: none; }}" have the number 621 be changed to at least 622 for moves like Hyperspace Fury? --Super goku (talk) 06:22, 14 January 2015 (UTC)

Referenced edit. Would not work with anything higher than 620 and it needs to work at 621 since that's the move ID. CycloneGU (talk) 06:56, 14 January 2015 (UTC)

Suggestion: "Affected by Crafty Shield" Move property

Not sure if I had mentioned this previously, but I was thinking we should have a "Affected by Crafty Shield" move property since we have one for Protect, which Crafty Shield is similar to. Superjustinbros. (talk) 00:01, 18 January 2015 (UTC)

Actually, never mind; I noticed that some moves that "block/protect" other moves like Wide Guard don't have move properties in the template. Superjustinbros. (talk) 00:09, 18 January 2015 (UTC)

Z-move effects

Perhaps there should be an entry for Z-moves, particurly for Z-status moves? Since (almost) all of them have a corresponding effect when in Z-form. --FIQ (talk) 12:01, 28 February 2017 (UTC)

I'd like to mention that the German Pokéwiki has done this (for all moves). While I believe it's useful for status moves, the way they did it, for damaging moves, I repeatedly confused their power as a Z-Move with their regular power. So if we do this, I believe we should make the difference clearly visible. Nescientist (talk) 17:02, 28 February 2017 (UTC)

Flag reform

I think we seriously need to reform the "flags" in the infobox. This post is going to be long, so my most basic ideas here:

  1. It really shouldn't matter whether something is implemented as an actual flag by the developers; it is either useful, or it is not.
  2. I think a move's infobox should complement other parts of the wiki, most notably the move's own Effect section. It can condense, sure, but if you'd have to read the Effect section anyway, having it in the infobox isn't really that useful on its own.

So, this is a list of "flags" I think are worth discussing:

And here are a few more considerations:

  • I think the Effect section should always contain the most defining aspects of the move. (That includes additional effects, charge/recharge etc.) We would not need it in the infobox as well.
  • We factor in distance in our target parameter (and I think that's better).
  • Many of these change between generations, and if they're important, we should note those in Effect sections anyway. Currently, we (try to) stick to GenVII behavior for the parameter (except for field, which is yes if it ever was a field move).
  • I don't think all of them are important enough for Effect sections. I really like how Snatch (move) or King's Rock have a table, and if you want to know whether something is affected by that, you'd be looking there anyway.
    • protect is quite trivial; except a very status moves (noted at Protect (move)), it depends on the target (more specifically, on the hit target), unless it is a defining feature of a move (that needs to be in the Effect section)
  • Just saying "is a <X> move" (sound-based, for example) covers many effects that are elsewhere on the wiki (categories in particular). Outsourcing it there (with a link) reduces the need to update any <X> move. And it also removes fluff from Effect sections*.

So, I'm leaning towards including (only) the following parameters:

aromaveil, authentic*, bite, bullet, contact, dance, field, gravity, heal, mirror*, (naturalobject), (nonsky), powder, pulse, punch, sound

I also think each of those should have a category. naturalobject and nonsky are for a few past games only, but I tend to think these should also be in the infobox. kingsrock, magiccoat and snatch change quite often, so I'm inclined to believe maybe they're better off at their respective pages only, with neat tables of affected moves per generation. I think mirror only changes for the few cases we already list at List of modified moves, and most authentic changes are due to them making sound moves hit through substitute in GenVI, so maybe we can include them, if we want to. I believe protect may not really need a param, but if it does, it should certainly bold "no".

So, I think this seriously requires some very open mind. I'm hoping for some input. (And then, I'm hoping for an implementation of our results.) Nescientist (talk) 14:45, 22 April 2017 (UTC)

One thing I'll say is, it may be wise to just make the template with your desired modifications in your userspace. I mean, for one thing, that's less work for someone else if it's accepted. For another...I, for one, can't really deal with that blob of text above well enough to give any sort of "real" answers, and examples could only help. Tiddlywinks (talk) 15:02, 22 April 2017 (UTC)
Note that the King's Rock moves aren't consistent between generations, see http://bulbapedia.bulbagarden.net/w/index.php?title=King%27s_Rock&redirect=no#Moves_affected_before_Generation_V --FIQ (talk) 18:00, 22 April 2017 (UTC)
Yeah, that's what the "kingsrock, magiccoat and snatch change quite often" part was about.
For this discussion, I imagine actually reading my line of reasoning will help more than potential examples can. (Though I admit examples could help.) The template itself will work either way; I guess it's not rocketscience to add or remove yes/no params at will. Basically, what this is about is: which ones? Nescientist (talk) 11:01, 23 April 2017 (UTC)

New template

I created one here that addresses the last two sections and some other ideas (see here). I would happily take feedback, before eventually working toward launching it. Nescientist (talk) 15:38, 22 June 2017 (UTC)

Targetting color changes

This template has always been super confusing with the targetting colors. This is mostly because moves that may affect some targets and others that will affect specific targets use colors that are way too similar, it's almost indistinguishable. I think a more proper distinction should be made to ease up on the confusion. Maybe something like #FFBF00 could be used for attacks that have choice of targets could make things so much clearer, without being too clashing with the rest of the color scheme. hfc2X 05:01, 9 October 2019 (UTC)

TR

"Not a TM, HM, or Move Tutor move." should be changed to "Not a TM, HM, TR, or Move Tutor move." Pikcahu (talk) 18:59, 26 December 2019 (UTC)

Adding a Field for Z-Power and Max Power

Just a sugguestion, there should be some (optional) field to include the Z-Power and Max Power for each move. TehPerson (talk) 02:57, 10 January 2020 (UTC)

Update

I think this template has to be updated to support 3 graphics. I think we'll need 3 graphics for Eternabeam. --TheICTLiker4 07:38, 7 March 2020 (UTC)

I'd really rather not do that. Ideally we would only have one image for each move, but at least two makes sense in a lot of cases (e.g. Solar Beam). Three is too much, so we'll just have to pick two frames for complex animations like Eternabeam. --SnorlaxMonster 08:33, 7 March 2020 (UTC)

Priority bug

I noticed that some pages render the priority value red and somewhat bigger. My guess is that the recent update has the expression error style take over, whenever the #ifexpr gives an error (compare Bide and Quick Attack). For this template, just replacing the #ifexpr by an #ifeq should suffice. Nescientist (talk) 16:33, 28 April 2021 (UTC)

Ah, yes I can see what happened there. I've applied that fix (and replaced all of the cases of #ifexpr with #ifeq when just checking equality). I doubt this is the only template with this kind of issue, so be sure to point it out when you see another. --SnorlaxMonster 11:14, 29 April 2021 (UTC)

Usable/Unusable Categories

This template should includes lgpe, swsh, and bdsp parameters that contain categories, rather than putting the usable move categories manually. AKUro? あくロちゃん 02:48, 25 November 2021 (UTC)

Super Contest Shows

It looks like there isn't a section for Super Contest Show move information (from BD/SP). Ideally that would include the number of Hype Points and a description. Spoonlord57 (talk) 07:31, 17 January 2022 (UTC) SpoonLord57