- User Since
- Apr 10 2015, 4:45 PM (267 w, 3 d)
Apr 14 2020
What type of mission are you running?
May 26 2019
The main issue that caused this was corrected by bohemia months ago... any further issues are usually related to a bad basic.cfg
Dec 12 2017
All the Destination unreachables are port 2306
This was captured with Firewall OFFLINE.
So, GTA never had the issue, they re-coded their mission so much, they cant pinpoint what fixed it because they never had it.
Seeing as they dont do it themselves:
RoleplayUK and Grand Theft Altis both have this issue solved. There are many servers out there that are having this issue, Even Bohemia have been looking into it, would be nice if they threw a lifeline. The downside is, these servers are gaining popularity as they haven't got the kicks anymore, why would they want competition?
Actually managed to get a wireshark capture as it crashed, was doing it for my ISP to see if there was anything their end... @Dwarden I can provide if needed.
Dec 4 2017
Some servers seem to have "found their own fix" you'll have seen them posting here prior but no longer mentioning it (rpuk)
Dec 1 2017
Still getting the issue:
Nov 26 2017
Nov 2 2017
We made a button that stores gear to an array and reapplies it to a player. However this is only useful if you're told you're naked. For an enemy, they see you ad naked, and bullet damage seems to act as if you have no armor
Oct 19 2017
We also have some more information regarding a BattlEye mass-kicking, which happened to some communities over these past few months. It seems we finally found a potential solution to this problem with our senior programming staff working on it as we speak. However, it might still take us some time, because the changes require low-level and potentially risky netcode changes. For this reason the implementation and testing needs to be handled with extreme care. It means we don't have a specific date yet, but we hope to release the change in one of the upcoming Main Branch updates. Please bear with us!
Aug 31 2017
Things like this REALLY need to be posted by BIS in the tracker, otherwise, what's the point of it?
Aug 29 2017
We get this issue on a rarer occasion than Wilco above, that said, it's the exact same errors and the same actions taken.
Jun 26 2017
Do you have any messages in the log before kicks?
Jun 7 2017
May 30 2017
Still exists 1.70.141846
May 29 2017
May 28 2017
Our server actually stopped having these "mass kicks" when we stopped using "headless client".