-
Notifications
You must be signed in to change notification settings - Fork 198
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
Newer pokemon #323
Comments
Sadly, no. This project is abandoned, and PoGO is now well protected only version 0.35 can join to this server |
yeps... Another emulator saw the day here https://github.com/msx752/PoGoEmulator in C # but it does not work in 0.69.0 either |
Ok thanjs |
I lost interest due to the Safetynet protection and the many "uncommon" decisions niantic made for the client. However working on this project was one of the most fun tasks ever for me. I'm thinking about writing a short article about the things happened last year in relation to Pokemon GO and this emulator with a few technical insights on how the emulator was created. |
How hard would it be to write a server for it? |
I'm not following the news anymore but I think the problem lies on all the client protections which has to get bypassed first. |
oh ok |
Generation II was already coded into 0.35 but the models were missing. It should be possible to add the second generation to the game if someone is able to dump the new models. |
How would one get the newer models? |
Possibly by copying the cached models from the android file system but I'm pretty sure that there are now several protections as well. |
https://github.com/apavlinovic/pokemon-go-imagery would this help |
@maierfelix Yes more or less this, but it's in C # |
I think @msx752 relied heavily on this here, they should exchange ideas both @maierfelix maybe this will bring something good |
well its a step in the direction |
nope i stopped to coding for pogoemulator or bots, due to the same issue |
Is it possible to get the newer pokemon with this server
The text was updated successfully, but these errors were encountered: