Closed samwfowler closed 9 years ago
Oh, and I'm guessing the numbers in "Expected 14 ExtEntries but received too many (9)" were the wrong way round haha, it make more sense if it were "Expected 9 ExtEntries but received too many (14)"...
Looks like I goofed the ProtocolExtension checks a bit. Next update will fix this! Thanks for taking the time to report this problem.
ExtEntries warning text fixed in d7ec7dcf70d016edcebf97275fdf076769492af4
The rest will be fixed shortly.
enabledExtensions.clear()?
I've noticed that now, if you click the "Try to reconnect" button after losing connection- all extensions suddenly disable and the client refuses to send the extinfo and extentry packets- with the following debug messages:
"11:34:35 [WARNING] Expected 10 ExtEntries but received too many (9)! This ext will be ignored: ClickDistance with version 1 11:34:35 [WARNING] Expected 11 ExtEntries but received too many (9)! This ext will be ignored: CustomBlocks with version 1 11:34:35 [WARNING] Expected 12 ExtEntries but received too many (9)! This ext will be ignored: ExtPlayerList with version 2 11:34:35 [WARNING] Expected 13 ExtEntries but received too many (9)! This ext will be ignored: EnvWeatherType with version 1 11:34:35 [WARNING] Expected 14 ExtEntries but received too many (9)! This ext will be ignored: EnvMapAppearance with version 1 11:34:35 [WARNING] Expected 15 ExtEntries but received too many (9)! This ext will be ignored: EnvColors with version 1 11:34:35 [WARNING] Expected 16 ExtEntries but received too many (9)! This ext will be ignored: ChangeModel with version 1 11:34:35 [WARNING] Expected 17 ExtEntries but received too many (9)! This ext will be ignored: MessageTypes with version 1 11:34:35 [WARNING] Expected 18 ExtEntries but received too many (9)! This ext will be ignored: EmoteFix with version 1"
This ONLY happens when you reconnect, not when you join normally. Cheers.