RakNetServerSession will handle same packet multiple times #26
Comments
Repository owner
locked and limited conversation to collaborators
Feb 22, 2017
whirvis
added a commit
that referenced
this issue
Nov 6, 2019
In this new verison 2.5, I actually fixed #23, and I also fixed #26 and #27! I also added a new feature requested in #25 so you can add and remove new MaximumTransferUnit values to work with using the RakNetClient. By default, the client adds the machines MTU with 2 retries and then what MCPE uses. However, this can be modified and they can be removed easily to use something when connecting to a server :)
whirvis
added a commit
that referenced
this issue
Nov 10, 2019
In this new verison 2.5, I actually fixed #23, and I also fixed #26 and #27! I also added a new feature requested in #25 so you can add and remove new MaximumTransferUnit values to work with using the RakNetClient. By default, the client adds the machines MTU with 2 retries and then what MCPE uses. However, this can be modified and they can be removed easily to use something when connecting to a server :)
whirvis
added a commit
that referenced
this issue
Feb 10, 2020
In this new verison 2.5, I actually fixed #23, and I also fixed #26 and #27! I also added a new feature requested in #25 so you can add and remove new MaximumTransferUnit values to work with using the RakNetClient. By default, the client adds the machines MTU with 2 retries and then what MCPE uses. However, this can be modified and they can be removed easily to use something when connecting to a server :)
whirvis
added a commit
that referenced
this issue
Feb 11, 2020
In this new verison 2.5, I actually fixed #23, and I also fixed #26 and #27! I also added a new feature requested in #25 so you can add and remove new MaximumTransferUnit values to work with using the RakNetClient. By default, the client adds the machines MTU with 2 retries and then what MCPE uses. However, this can be modified and they can be removed easily to use something when connecting to a server :)
whirvis
added a commit
that referenced
this issue
Feb 22, 2020
In this new verison 2.5, I actually fixed #23, and I also fixed #26 and #27! I also added a new feature requested in #25 so you can add and remove new MaximumTransferUnit values to work with using the RakNetClient. By default, the client adds the machines MTU with 2 retries and then what MCPE uses. However, this can be modified and they can be removed easily to use something when connecting to a server :)
whirvis
added a commit
that referenced
this issue
Feb 22, 2020
In this new verison 2.5, I actually fixed #23, and I also fixed #26 and #27! I also added a new feature requested in #25 so you can add and remove new MaximumTransferUnit values to work with using the RakNetClient. By default, the client adds the machines MTU with 2 retries and then what MCPE uses. However, this can be modified and they can be removed easily to use something when connecting to a server :)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the RakNetServerSession class there is a glitch where the class will actually handle the CONNECTION_REQUEST_ACCEPTED packet multiple times since it is resent as the login packets are unreliable (for some stupid reason).
The text was updated successfully, but these errors were encountered: