You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
So it looks like the code responsible for that check was translated during localization before the localized names were finalized, and the bug was probably found so late in QA that it was deemed safer/faster to just use red's trades in blue than find/fix the issue.
As for why they check the name being received instead of the species? It's impossible to know without knowing what the state of the code was when that line was written. They fixed this bug in Yellow, where they do check species ID instead
I found this because I couldn't find an answer to how big their stack was, so I went looking for where they set `sp` during boot, and found this since the check had "SP" in it. The stack was 286 bytes
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
