Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

"Order" field not populated for Pokémon whose level-up moves are not in numerical order

Aperta
#1,534 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
python
Ambito
api, data

Direzione di ricerca

Inizia confrontando i learnset sorgente collegati in data/pokemon/evos_moves.asm e data/pokemon/evos_attacks.asm con l'attuale rappresentazione dei learnset dell'API, quindi ricostruisci come vengono importati i dati di Pokémon Sword and Shield e Brilliant Diamond and Shining Pearl. Identifica ogni learnset interessato con un ordine errato e definisci i valori order previsti; il lavoro è completato quando l'API conserva l'ordine previsto delle mosse per i casi documentati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

There are a handful of cases in the Pokémon games where their level-up movesets are not ordered numerically. This can actually impact gameplay, mostly just in terms of what moves wild Pokémon know (and in what order), but in Sword and Shield it really matters.

  • In Pokémon Yellow, Primeape's learnset lists Thrash at Level 46 then Screech at Level 45. Primeape still learns the moves as normal at the appropriate levels. If you catch the Level 46 Primeape on Kanto Route 23 I'm not sure what order the moves are in (I didn't find anything in my research notes about this case), but they could theoretically be impacted.
  • In Generation II, Muk's learnset lists it's moves completely out of order. As Bulbapedia notes, this means that wild Muk (which can only appear up to Level 33 in Gen 2) will only know Poison Gas, Pound, and Harden (and not Minimize and Screech, which they would know if their learnset was ordered correctly).
  • In Pokémon Sword and Shield and Pokémon Brilliant Diamond and Shining Pearl, Dragonite's learnset lists Outrage at Level 41, but sorts it between the Level 62 and Level 80 moves. In Sword and Shield at least (apparently I never actually tested BDSP), this prevents Dragonite from learning the move by level-up at all. (I made a Twitter thread detailing my research on this topic in 2023, but I have since privated my Twitter and don't plan to undo that. I can repost the details in this thread if desired.) However, it can still learn Outrage via the Move Reminder starting at Level 41; additionally, the wild Level 71 Dragonite at Ballimere Lake knows Outrage (since it's above Level 62).

Those are the only cases I'm aware of in the core series games, but it's possible there are some in other games that I'm not aware of. They're certainly the only cases in Gen 1, 2, and SwSh/BDSP.

I think it would be worth including "order" values for the entire learnset in cases like these, since it does actually make a functional difference.

Lingua principale
Python
Stelle
5.4k
Fork
1.2k
Merge medio
2g 12h
PR unite (30g)
18

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PokeAPI/pokeapi

Tutte le issue di PokeAPI/pokeapi

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.