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

In sun and moon, GTS list screen not valid if only one pokemon #27

Open
k20stitch opened this issue Jan 28, 2018 · 8 comments
Open

In sun and moon, GTS list screen not valid if only one pokemon #27

k20stitch opened this issue Jan 28, 2018 · 8 comments

Comments

@k20stitch
Copy link
Contributor

So if there's only one pokemon on the GTS list screen it comes up as invalid and panics then goes to recovery mode

@Naturally-Delicious
Copy link

By "one Pokémon in GTS list screen", you mean you only have one Pokémon registered in your dex?

@k20stitch
Copy link
Contributor Author

k20stitch commented Jan 29, 2018 via email

@SteveCookTU
Copy link
Collaborator

I will have to test this out myself and inspect it for issues. Seems weird it would go into panic mode. Ideally it would just read one on the page, notice it is trade-able or not, and then trade or re-search.

@k20stitch
Copy link
Contributor Author

it fails as the "is correct screen" section. My guess is the address is different when containing one pokemon? I'll dump the address when it panics

@SteveCookTU
Copy link
Collaborator

The block of gts will always be the same but not sure why the value at the screen detection address wouldn't change just cause it's only one entry.

@k20stitch
Copy link
Contributor Author

Maybe that address doesn’t contain the left and right scroll bars?

@Bappsack
Copy link
Contributor

The Answer is:

Currentscreen != 4180 when only one Entry is present, the Offset contains 0x40C0 then.

@Bappsack
Copy link
Contributor

Issue was fixed with Commit: f4f15fe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants