Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate what's needed to maintain trade compatibility #6

Open
1 of 2 tasks
andiemmadavieswilcox opened this issue Jan 10, 2021 · 2 comments
Open
1 of 2 tasks
Assignees
Labels
Documentation Includes maintaining the repo’s wiki and README(s) Research Investigative tasks needed to facilitate other developments

Comments

@andiemmadavieswilcox
Copy link
Member

andiemmadavieswilcox commented Jan 10, 2021

Overview

...as well as potentially other compatibility concerns (see compatibility section in repo's README). I would imagine something like keeping Pokémon data stored at the same memory addresses would likely be a key factor, but this is just speculation.

Purpose

Trade compatibility is one of the project's key goals, so it's important that we get as much information as possible about how to maintain said compatibility before we start editing the code.

Notes

I know that there are problems with being able to trade between different languages of the early Pokémon games, so this could be a good starting point for researching the reasons why.

Tasks

  • Research to uncover the main reasons.
  • Document the findings in the wiki.
@andiemmadavieswilcox andiemmadavieswilcox self-assigned this Jan 28, 2021
@andiemmadavieswilcox andiemmadavieswilcox added Documentation Includes maintaining the repo’s wiki and README(s) Research Investigative tasks needed to facilitate other developments labels Jan 28, 2021
@andiemmadavieswilcox
Copy link
Member Author

andiemmadavieswilcox commented Jan 28, 2021

The trade issues between Japanese and non-Japanese versions do indeed seem to be primarily due to changes in the memory (RAM, not ROM) layout, as corroborated by this PokéBase Q&A and this Bulbapedia article:

PokéBase:

image

Bulbapedia:

image

@andiemmadavieswilcox
Copy link
Member Author

Given this new information, we should aim to not touch the existing layout where possible, which shouldn't be an issue given the GBC has quadruple the amount of work RAM (32 kB up from 8 kB) and double the amount of video RAM (16 kB up from 8 kB) compared to the DMC, and we're going to be running in GBC-exclusive mode, so we can make use of this extra memory for anything new while hopefully maintaining trade compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Includes maintaining the repo’s wiki and README(s) Research Investigative tasks needed to facilitate other developments
Development

No branches or pull requests

1 participant