Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Missing Trade Encounters

オープン
#1,451 コメント 8 件 リアクション 2 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
45/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
python
領域
api, database

調査の方向性

Encounter_Conditions.csv、リンクされている Pokémon XD: Gale of Darkness PR、リンクされている Bulbapedia の generation-I の交換リストから始め、既存の generation 7 の NPC 交換データと比較します。選択した generation の NPC 交換エンカウントが、交換条件と NPC または要求された Pokémon の詳細を含めて表現され、プレイヤー間の交換を扱っていなければ完了です。

索引モデルが issue の本文から書いたものです。

説明

The API is missing a lot of trade encounters, what I've noticed so far is:

All RBY trades are missing.

All GSC Trades are missing:

All RSE Trades are missing:

All FRLG Trades are missing:

All G4 Trades are missing in HGSS and DPPt:

All G5 Trades are missing in BW and B2W2:

All G6 Trades are missing in XY/ORAS:

Gen 7 is the only gen with encounters that actually has the NPC trades, and it has them for both LGPE and SM/USUM!

Obviously they're missing in gens 8/9 as well, but there's currently no encounter data at all for them yet in the API anyway.

In addition to this, as discussed in my PR for Pokemon XD: Gale of Darkness, I think we should be add a new Encounter_Condition in Encounter_Conditions.csv called Trade.

And then, when adding NPC-Trade encounters to the API, we should add an encounter condition for each one that says what Pokemon to trade for them, and what the NPCs name is if they're named. Let's use Mimien the Mr. Mime as an example:

  • 108,15,trade-REYLEY-abra,0

This notes which NPC to trade with and which Pokemon to give them. We would have to go back and add the conditions for the gen 7 pokemon trades as well.

Lastly, I do think it's important to have this data in the API. Certain Pokemon are only catchable in games via trade from an NPC, such as Mr Mime, Farfech'd, and a few others.

Things I think this issue should not cover:

  • Trading for a Pokemon with another real gameboy

That is a much bigger task, out of scope with the NPC-Trade encounter_method, and also solvable by the end user.

Currently I'm working on a website with a friend and we can have the site display trade or transfer from X game just by using logic to deduce if the Pokemon is in the selected game or not, and what is the nearest game you could receive it from, so I don't think it's necessary to include in the API at all.

As with any issue like this I bring up, I'm of course willing to do the work and write down all these encounters. I would probably do 1 PR per gen as to not make a massive PR with like 85 trade pokemon from 7 regions and 10 games.

I would start with gen 1 and work my way up, but if anyone is interested in doing any of these I'd ask you post here so we don't both do the same gen at once!

主要言語
Python
スター
5.4k
フォーク
1.2k
平均マージ
2日 12時間
マージ済み PR(30日)
18

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

PokeAPI/pokeapi のほかの issue

PokeAPI/pokeapi の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。