search

kuroppoi / entralinked

A standalone Game Sync emulator for Pokémon Black & White.
MIT License
105 stars 7 forks source link

Persistent 20100 Error #31

Closed DoctorDisease closed 5 months ago

DoctorDisease commented 7 months ago

Have followed the quick start guide to the letter, as well as the posted solution for this error code, yet it still persists.

kuroppoi commented 7 months ago

Please attach the program log file

DoctorDisease commented 7 months ago

2023-11-15-1.log 2023-11-15-2.log 2023-11-15-3.log latest.log This is all 4 Log files I have. Unsure if you are able to see from the log files but the .jar and its entire folder were on the desktop with permissions to read and write, as well as being run from an administrator CMD.

kuroppoi commented 7 months ago

Double-check your DNS settings and delete your other access point configurations if you have any. Make sure that your connection is stable, and keep an eye out for any changes in the error message.

DoctorDisease commented 7 months ago

Will do when able, I'll get back to you then. Thank you very much for starting this project in the first place, let alone still being active on it.

DoctorDisease commented 7 months ago

Alright I've finally had time to sit down. My DNS was correct, I deleted my other saved connection setting and I am now encountering a communication error with no code. It reads "Communication error... Disconnecting from Nintendo WiFi Connection." which only appears onscreen for about 2 seconds before flashing to "Communication error..." I did encounter this issue several times beforehand and neglected to mention that earlier. Log: latest.log

kuroppoi commented 7 months ago

Peculiar. When does the error appear exactly? Immediately after the Musharna screen ends, or does it hang on the tuck-in screen for a good while? Might be worth checking out #19

DoctorDisease commented 7 months ago

This error appears after the Musharna screen but before I have the option to tuck a Pokemon in if it will help I can record a video really quick

kuroppoi commented 7 months ago

A video would be helpful, if it's not a hassle :)

DoctorDisease commented 7 months ago

Here you are, it is incredibly similar to the video already posted in #19 https://youtu.be/HQF_wPnioDo?si=jofK8uo0Q-hZkrGT And the log from the connection attempt in the video latest.log

kuroppoi commented 7 months ago

I don't know why this happens, but switching to another network solved the problem for the other person.

DoctorDisease commented 7 months ago

Unfortunately that did not work for me, the network I switched to was a mobile hotspot and the error in the video persisted.

kuroppoi commented 7 months ago

I'm gonna look into it

DoctorDisease commented 7 months ago

I have managed to obtain a game sync ID by switching to my Japanese cartridge on an Original NDS model, as well as using the hotspot. I am now at the stage of waiting 1 day to use the service, Is there anyway to skip that?

kuroppoi commented 7 months ago

I don't know of a way to bypass the cooldown, sorry

ashgx commented 7 months ago

I remember that you can get around this restriction by modifying the time to reach it, for example, today, November 16th, and then modifying it to be after November 17th

I have managed to obtain a game sync ID by switching to my Japanese cartridge on an Original NDS model, as well as using the hotspot. I am now at the stage of waiting 1 day to use the service, Is there anyway to skip that?

I remember that you can get around this restriction by modifying the time to reach it, for example, today, November 16th, and then modifying it to be after November 17th

kuroppoi commented 7 months ago

Sorry for taking a while, I've just pushed release v1.3.5 which adds a few lines of debug logging.

If you could try to reproduce the issue on the new version then hopefully the new debug log file located at logs/debug.log will provide more insight as to where exactly it goes wrong.