Page MenuHomeFeedback Tracker

Mass Battle Eye Kicks on Multiplayer servers.
New, NormalPublic

Description

For the past 10 months our 4 servers have had an issue with battle eye kicking everyone off of the server. I was wondering if this was something you are already aware of.

I have done some research into the issue and this is what I have found.

  1. It is not OUR mission file that is at fault. I know this because our servers are not the only affected servers. Popular servers such as Olympus and Asylum are also having these "Mass kicks". I have downloaded about 8 different servers worth of mission files and they are all different. That can almost guarantee that it is not the mission files doing.
  1. Both modded and un-modded servers are having the issue with the battle eye kicks. As I said before I have tried wasteland missions, king of the hill missions, life missions and modded missions. They all have "Mass battle eye kicks"
  1. This is not something that you guys did intentionally, since servers reported having the issues at different times. What I mean by that is Olympus started having mass battle eye kicks in September, Asylum started having kicks in June, A3 wasteland started kicks in October, etc....This concludes that is was not a patch that went out and broke something.

I can tell you that our servers have tried multiple fixes, such as switching databases, buying new hardware for the servers, we even thought 64 bit would fix it. We even re-wrote the mission file in an attempt to see if that would work. All attempts to fix the issues have failed.

I am not sure what exactly is happening since I do not have experience on the network side of things. However, what seems to be happening is that when a large amount of packets are coming through (50 players or more) sometimes the packets do not make it to the client. It ends up blocking up somewhere and then battle eye mass kicks everyone to clear the blockage.

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
Windows 10 pro
Category
Server
Steps To Reproduce

When there is more than 50 players on the server it starts to mass battle eye kick people.

https://gyazo.com/abb5a5d41ed106cb322eb3c1f541e99f

Additional Information
NOTE: I have only noticed the battle eye kicks when there are about 50 players or more on a server.

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Here's a post from one server experiencing the issue that has a touch of detail.

https://www.roleplay.co.uk/topic/79772-altis-life-uk-server-development-feedback/?page=7#comment-484144

Wilco added a subscriber: Wilco.May 17 2017, 6:31 PM
Wilco added a comment.EditedMay 17 2017, 6:34 PM

Can confirm Roleplay UK is also having this issue which started around September/October 2016

Just checking in to lend our hand if BIS need any logs/info or need to run any server-side tests with us.

Can also confirm we are still experiencing this with 1.70

Gaming-Asylum started having the issue in May/June (more heavily in June).

I'd have to OK things with our server owner, but I'm also willing to provide whatever I'm able and allowed to try and help resolve the issue.

Our server actually stopped having these "mass kicks" when we stopped using "headless client".

Asylum had reconfigured everything in preparation for a move to Headless Client and had subsequently stopped using it prior to the increase in mass BE kicks. (i.e, we've had the issue without using headless client)

Interesting. What mod/version you running? We accidentally ran Headless last night, mass kick

reekoj added a subscriber: reekoj.May 29 2017, 2:32 PM

I thought i was the only one having this issue.
Everytime i start my headless client, even if he does nothing, when we reach more than 100 players, after few minutes everyone gets kicked.
That's why i stopped using HC.

Wilco added a comment.May 31 2017, 3:31 PM

Just to update

We have tried without the headless client and mass kicks still happen, Not as much in volume of players being kicked but it still exists.

KevinP added a subscriber: KevinP.Jun 5 2017, 10:46 PM
BoGuu added a subscriber: BoGuu.Jun 19 2017, 1:27 AM

any comment from BI on this. seem as normal you guys hide under rocks ?

wallop added a subscriber: wallop.Jun 19 2017, 7:58 PM
KevinP added a comment.EditedJun 20 2017, 5:40 AM

We are experiencing this at around 100+ players, some times it is fine but other times BE randomly starts kicking at around 105~ players...

Wilco added a comment.Jun 22 2017, 7:16 PM

Just to confirm after the 1.72 update we are still experiencing mass kicks.

dedmen added a subscriber: dedmen.Jun 22 2017, 7:58 PM

My server has mass kicks very frequently, so tonight I tried running it without any BE filters. We lasted 4 hrs 15 mins with 70+ players and no issues, then I turned the filters on and within 40 minutes a mass kick occurred.

I'll do more tests tomorrow removing individual filters to see if its a specific type of filter causing my problems and then post my results here.

Wilco added a comment.Jun 25 2017, 5:53 PM

After speaking with Connor we tried disabling a few BE Filters but it was only 20 mins later we had a mass kick, We restarted the server and removed all the filters, another 15 mins in and another mass kick.

Removing BE Filters did not work for us, In the past connor we survived 24 hours without any kicks so it might have just been luck or whatever is causing this was not triggered during that time. :(

Norman added a subscriber: Norman.Jun 25 2017, 6:25 PM

We completed testing with no filters, I don't think they are the issue

Do you have any messages in the log before kicks?

Nothing logged other than the log of the kick

Wilco added a comment.Jun 28 2017, 4:53 PM

I think it's a shame that I had to tweet the Twitter account to find out the QA team are trying to reproduce this in-house rather than someone simply reply here that it's being worked on considering its affecting a lot of busy servers.

I would also invite the QA team to work with either ourselfs or another busy server to reproduce this in a live enviorment seeing we will recieve a kick 2-5 times per evening so this can be figured out sooner rather than later as past experiences of mass kicks/server crashes it, unfortunately, killed a lot of smaller community's starting up back in 2014/2015 which is a shame to see considering the efforts that go into setting something up on Arma 3 and engaging and maintaining a playerbase.

Anyone reading this from other community's please send a tweet linking this feedback ticket so we are not forgotten as many tickets on here are still unsolved from 2013/2014!

We hope to be updated soon!

Gnashes added a comment.EditedJun 28 2017, 6:35 PM

@Wilco Asylum is keeping an eye on this. Seems based on our internal experiments that a hard restart alleviates the issue, but if left unchecked the server will continue to kick every time it fills back up (every 15 mins or so) until it naturally hard restarts.

This can either mean a single instance if an Admin is on a server when it kicks and hard restarts it, or dozens of times in a few hours if nobody is around and monitoring the servers.

We suspect it has something to do with server memory, and the amount of data being held in memory by Arma for variables, but haven't been able to actually validate that in any substantial way.

MrSmirnoff added a subscriber: MrSmirnoff.EditedJun 28 2017, 6:56 PM

Our life servers are suffering from this as well. Some servers suffer from it more than others even though they all run the same mission. We tried disabling BE filters but we still suffered mass kicks regularly. This is a very serious issues since when mass kicks happen players lose progress and money in game.

Please fix this Bohemia thank you.

Bamf added a subscriber: Bamf.Jun 28 2017, 11:45 PM

Gaming Asylum has extensive logging inside of Splunk of data around the times this issue occurs. I'm happy to provide data to BIS as necessary.

This is one of the largest issues facing the modding community though, and I'm sure anyone with a large server would be more than happy to assist you in tracking this down.

After a few more days of tests I'd like to clear up my last message.
I do still get mass kicks without battleye filters, they are just not as frequent.
As you guys have said its clearly not the cause of the problem, just me shooting myself in the foot with the amount of filters I had.

Azeh added a subscriber: Azeh.Jun 30 2017, 7:48 PM
Erik added a subscriber: Erik.Jul 2 2017, 9:55 AM
TikTak added a subscriber: TikTak.Jul 3 2017, 2:09 PM

This issue is hugely affecting our Arma 3 community and servers. Would love to hear Bohemia's answer on this.

Can you guys give us a hand here? @Alwin @razazel @Jawsh

Azeh added a comment.Aug 7 2017, 1:37 PM

Bohemia pls

Bohemia have commented on this via twitter saying they are still investigating the issue

Wilco added a comment.Aug 15 2017, 6:06 PM

They have indeed... I know this might be a complex issue but a reply on your own feedback tool should come way before a reply on twitter, Many servers here would indeed love to help and run any builds or tests BIS requires.

I can only take from the twitter reply that they have pinned it down to being a BE problem, It would be nice to have a proper update and someone assigned to this feedback task who can communicate going forward.

As mentioned on the Twitter we are looking into the issue together with BE developers, searching for a suitable solution. Unfortunately that is the only info I have for now, I'll try to keep this updated with the progress (once I know something).

Wilco added a comment.Aug 29 2017, 8:46 PM

@razazel @Dwarden can I ask why BIS believe this is a BE issue?

Over the weekend the issue has been worse, we have received 5 mass kicks per day, so far today there has been 2 and we are just entering our peak times.

Not meaning to sound shitty but myself and other servers in this situation are completely fed-up, I know BIS needs to make money hence the DLC is taking up everyone's time but this is a bloody big issue! Its not been assigned major or as it actually been assigned to anyone unlike other very small tickets

No one so far has been asked to provide their RPT, so considering BIS cannot reproduce this in-house I am a little confused why BE is being blamed for this ? Maybe thats just lack of communication from BIS to the server owners as this issue is yet to come up in a SITREP

Leading up-to the kicks there are tens of thousand lines with network message is pending

19:10:19 Server: Network message 4c59d07 is pending
19:10:19 Server: Network message 4c59d07 is pending
19:10:19 Server: Network message 4c59d1b is pending
19:10:19 Server: Network message 4c59d1b is pending
19:10:19 Server: Network message 4c59d1f is pending
19:10:19 Server: Network message 4c59d21 is pending
19:10:19 Server: Network message 4c59d34 is pending
19:10:19 Server: Network message 4c59d34 is pending
19:10:19 Server: Network message 4c59d35 is pending
19:10:19 Server: Network message 4c59d38 is pending
19:10:19 Server: Network message 4c59d38 is pending
19:10:19 Server: Network message 4c59d39 is pending
19:10:19 Server: Network message 4c59d4b is pending
19:10:19 Server: Network message 4c59d4d is pending

We also have these following errors in the lead-up for multiple players:

18:57:02 NetServer: users.get failed when sending to 1788678648
18:57:02 Message not sent - error 0, message ID = ffffffff, to 1788678648 (Calum Williams)
18:57:02 NetServer::SendMsg: cannot find channel #1788678648, users.card=115
18:57:02 NetServer: users.get failed when sending to 1788678648
18:57:02 Message not sent - error 0, message ID = ffffffff, to 1788678648 (Calum Williams)
18:57:02 NetServer::SendMsg: cannot find channel #1788678648, users.card=115
18:57:02 NetServer: users.get failed when sending to 1788678648
18:57:02 Message not sent - error 0, message ID = ffffffff, to 1788678648 (Calum Williams)
18:57:02 NetServer::SendMsg: cannot find channel #1788678648, users.card=115
18:57:02 NetServer: users.get failed when sending to 1788678648
18:57:02 Message not sent - error 0, message ID = ffffffff, to 1788678648 (Calum Williams)
18:57:02 NetServer::SendMsg: cannot find channel #1788678648, users.card=115
18:57:02 NetServer: users.get failed when sending to 1788678648
18:57:02 Message not sent - error 0, message ID = ffffffff, to 1788678648 (Calum Williams)
18:57:02 NetServer::SendMsg: cannot find channel #1788678648, users.card=115
18:57:02 NetServer: users.get failed when sending to 1788678648
18:57:02 Message not sent - error 0, message ID = ffffffff, to 1788678648 (Calum Williams)
18:57:02 NetServer::SendMsg: cannot find channel #1788678648, users.card=115
18:57:02 NetServer: users.get failed when sending to 1788678648
18:57:02 Message not sent - error 0, message ID = ffffffff, to 1788678648 (Calum Williams)
18:57:02 NetServer::SendMsg: cannot find channel #1788678648, users.card=115
18:57:02 NetServer: users.get failed when sending to 1788678648
18:57:02 Message not sent - error 0, message ID = ffffffff, to 1788678648 (Calum Williams)
18:57:02 NetServer::SendMsg: cannot find channel #1788678648, users.card=115

and also the following as been noticed:

Observer C MedellinCartel:3 (HenrikEng) REMOTE (civ_48) in cargo of C MedellinCartel:3 (HenrikEng) REMOTE (civ_48); message was repeated in last 60 sec: 18611

Now considering there is very little documentation from BIS about these errors and little to no answers to the feedback people have reported on this very tool.... I personally do not know if this is connected but i guess by the RPT that goes upto 130,000 + lines sometimes more that it might just well be!

In the connection log it just says the following for multiple players:

9:11:42 Player PC Darkk [EA655] kicked off by BattlEye: Client not responding
19:11:42 Player Cpl. Kieron [UNMC] kicked off by BattlEye: Client not responding
19:11:42 Player (SOS) RCT. Andrew kicked off by BattlEye: Client not responding
19:11:42 Player Jaybeesemer kicked off by BattlEye: Client not responding
19:11:42 Player Michael Anthony kicked off by BattlEye: Client not responding
19:11:42 Player Tyrone Burmingham kicked off by BattlEye: Client not responding
19:11:42 Player Rick Sanchez kicked off by BattlEye: Client not responding
19:11:42 Player Joe [T] kicked off by BattlEye: Client not responding
19:11:42 Player Kattana kicked off by BattlEye: Client not responding
19:11:42 Player Morgan Dunne kicked off by BattlEye: Client not responding
19:11:42 Player Pvt. Myron [UNMC] kicked off by BattlEye: Client not responding
19:11:42 Player LCpl. Shelby Tom[UNMC] kicked off by BattlEye: Client not responding
19:11:42 Player o l l i e kicked off by BattlEye: Client not responding
19:11:42 Player Metseven3 kicked off by BattlEye: Client not responding
19:11:42 Player mrsnaps kicked off by BattlEye: Client not responding
19:11:42 Player Emil kicked off by BattlEye: Client not responding
19:11:42 Player PC Wally[AT926] kicked off by BattlEye: Client not responding
19:11:42 Player Vincent kicked off by BattlEye: Client not responding
19:11:43 Player Oliver kicked off by BattlEye: Client not responding
19:11:43 Player Jamie kicked off by BattlEye: Client not responding
19:11:43 Player Vlad kicked off by BattlEye: Client not responding
19:11:43 Player Vladynson kicked off by BattlEye: Client not responding
19:11:43 Player Sam Turret kicked off by BattlEye: Client not responding
19:11:43 Player Tropical kicked off by BattlEye: Client not responding
19:11:43 Player [V] Joe Moore kicked off by BattlEye: Client not responding
19:11:43 Player Peter kicked off by BattlEye: Client not responding
19:11:43 Player Regin kicked off by BattlEye: Client not responding
19:11:43 Player EL BLONDE kicked off by BattlEye: Client not responding
19:11:43 Player HARRY kicked off by BattlEye: Client not responding
19:11:43 Player (SOS) RCT. Wang kicked off by BattlEye: Client not responding
19:11:43 Player Fierce PC kicked off by BattlEye: Client not responding
19:11:43 Player PC Mystix kicked off by BattlEye: Client not responding
19:11:43 Player [JINC] Moh Lester kicked off by BattlEye: Client not responding
19:11:43 Player Bonne kicked off by BattlEye: Client not responding
19:11:43 Player Pfc. Dyrling [UNMC] kicked off by BattlEye: Client not responding
19:11:43 Player Jake kicked off by BattlEye: Client not responding
19:11:43 Player Daniel kicked off by BattlEye: Client not responding
19:11:44 Player Nema kicked off by BattlEye: Client not responding
19:11:44 Player Hector Torres kicked off by BattlEye: Client not responding
19:11:44 Player Keith fishwick kicked off by BattlEye: Client not responding
19:11:44 Player jespe kicked off by BattlEye: Client not responding
19:11:44 Player KH kicked off by BattlEye: Client not responding
19:11:44 Player Oscar Mike kicked off by BattlEye: Client not responding

I wish we reported this earlier, this started in October for us and we thought it was an issue with our code/our servers but this topic does say otherwise! So a big thanks to aslyum for coming forward.

We are approaching a year now since this issue first started happening and we are being told to "wait until after the DLC" ... It's just not good enough it's making people not play arma until its fixed and not play on the servers affected

So again we offer our helping hand seeing the twitter has already confirmed no one has been able to reproduce this in-house

If there is an internal requirement for an issue to be considered major when a certain number of people subscribe then please tell us, our community alone could get a few hundred to a thousand players who are affected by this issue daily on this within a few hours and I am pretty sure the other large servers that are here could too!

Neology added a comment.EditedAug 29 2017, 9:12 PM

We get this issue on a rarer occasion than Wilco above, that said, it's the exact same errors and the same actions taken.

I personally believe it has nothing to do with Battleye too, we see it even more whilst using our headless client, fortunately, we're rewriting its system so get the kick less, however it all points to network activity as shown in the logs above.

I implore @razazel and @Dwarden to take the offers from communities such as Asylum, and get tests done you can't do in-house. We offer our services too!

Wilco added a comment.Aug 29 2017, 9:52 PM

@Neology not to guide BIS off track, When you previously wrote about the HC we, in fact, turned ours off for multiple restarts and had the kicks just the same, So did another populated server we speak to.

We believe this not to be HC related but more network traffic related, Some of the bigger German servers are not here because they're not having kicks so I believe it to be down to something we are all using or some command.

I hope one day we will find out! It reminds me of the server crashes of 2015.... that was apparently down to an animation (we never got told the exact reason) The RPT in the lead up is very similar!

Bamf added a comment.Aug 29 2017, 10:17 PM

To echo what has been said today, please let me know what sort of reporting you need from us to help you track down this issue. We keeps logs of virtually everything, and have them going back for several years. I am personally happy to help getting this tracked down as it has plagued our community going back to May of last year.

@Bamf our logs show ours started on October 11th 2016, There were no mass kicks before that date.

Out of interest what date in May did your's start?

Bamf added a comment.Aug 30 2017, 12:57 AM

@Wilco let me dig through the logs a touch. Looks like it actually began before May. It's been so long since I pinpointed the start date - and I had May in my head for some reason.

Wilco added a comment.Aug 31 2017, 7:24 PM

Just to keep everyone else in the loop

Some promising news from BIS today on twitter: https://twitter.com/Arma3official/status/903174679183192065

Fingers crossed!

Neology added a comment.EditedAug 31 2017, 7:53 PM

Things like this REALLY need to be posted by BIS in the tracker, otherwise, what's the point of it?

Not the first time we get answers through twitter.

Lakotiz added a subscriber: Lakotiz.Sep 3 2017, 9:27 PM
Azeh added a comment.Oct 19 2017, 5:13 PM

maybe one day

l9th9l added a subscriber: l9th9l.Oct 19 2017, 6:49 PM

@Dwarden hey cucklord, any response?

https://dev.arma3.com/post/sitrep-00204

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!

As happy as I am to finally have had something said about it, it took them far too long to even comment on it. Running a server is stressful as it is, chasing the producer of the game certainly doesn't help this.

This really should have been something that was 'being worked on' the day it started happening

Eyad added a subscriber: Eyad.Nov 26 2017, 1:19 PM

unban tyrone

Dell added a subscriber: Dell.EditedNov 26 2017, 3:28 PM

I assume that this is due to poor configuration of basic.cfg.
https://community.bistudio.com/wiki/basic.cfg
Also look at the research on the forum.
Also try to disable BattlEye. I'm sure the problem will remain

Unfortunately not.

See my quote from the SITREP above.

Dell added a comment.Nov 26 2017, 3:34 PM

We faced the same problem. But the correct setting of basic.cfg helped. I do not know why, but I also had off battleye. It seems that because of the dll.

Hey guys, have you by any chance tried the latest RC build? The potencial fix mentioned in the SITREP is already there so, it might be worth a shot giving it a try and reporting back in case something is still broken :)

Azeh added a comment.Nov 27 2017, 12:55 PM
This comment was removed by Azeh.
Neology added a comment.EditedDec 1 2017, 9:23 PM

Still getting the issue:

20:06:33 BEServer: registering a new player #1577864936
20:06:37 NetServer: cannot find channel #1577864936, users.card=46
20:07:06 Server: Network message 115523 is pending
20:07:06 Server: Network message 115523 is pending
20:07:07 NetServer: cannot find channel #516779254, users.card=46

Bamf added a comment.Dec 4 2017, 7:47 PM

The latest update does not appear to have fixed the BE mass kick issue for Asylum. In the last 72 hours we have had approximately 13 such mass kicks with the same messaging as before the 1.78 patch.

Some servers seem to have "found their own fix" you'll have seen them posting here prior but no longer mentioning it (rpuk)

hope you don't mind Bamf, i'm quoting you on our forums as people are saying its "just us"

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.

Azeh added a comment.Dec 5 2017, 12:05 AM

Some servers seem to have "found their own fix" you'll have seen them posting here prior but no longer mentioning it (rpuk)

hope you don't mind Bamf, i'm quoting you on our forums as people are saying its "just us"

Zero-One still have them too.
https://i.gyazo.com/f9c9845ae0e7fea211052b5a2f7a4a1a.png

Thats 5 communities that is suffering with this some have been suffering for over 12 months, can we get some sort of acknowledgement that this issue still exists, you contact bohemia to report it and they say post here, when you do nobody ever responds....

@Neology Haha, feel free. I largely just stopped answering our community and began directing them to this ticket.

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?

Azeh added a comment.Dec 5 2017, 6:37 PM
This comment was removed by Azeh.
This comment was removed by Neology.
Neology added a comment.EditedDec 6 2017, 1:48 AM

Seeing as they dont do it themselves:

[7:17 PM] Dwarden: good news about the BE troubles ... and bad news about the BE troubles ...
[7:17 PM] Dwarden: will know more after next DEV branch tomorrow 😁
[7:18 PM] Dwarden: fixed some if not all of it ... lot of brave programmers fallen on the battlefield today

Posted 05/12/2017 (dd/mm/yyyy)

So, GTA never had the issue, they re-coded their mission so much, they cant pinpoint what fixed it because they never had it.

All the Destination unreachables are port 2306
This was captured with Firewall OFFLINE.

An example of log before everyone is kicked:

19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:28 Server: Network message 57896cf is pending
19:58:28 Server: Network message 57896cf is pending
19:58:28 Server: Network message 5789d5e is pending
19:58:28 Server: Network message 578a84d is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:32 NetServer: cannot find channel #1373936035, users.card=72
19:58:32 Message not sent - error 0, message ID = ffffffff, to 1373936035 (ツ| Flames  )
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 5790d50 is pending
19:58:32 Server: Network message 5790d50 is pending
19:58:32 Server: Network message 5790d52 is pending
19:58:32 Server: Network message 5790d52 is pending
19:58:32 Server: Network message 5791043 is pending
19:58:33 Server: Network message 57923c3 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
Azeh added a comment.Dec 14 2017, 3:13 PM
This comment was removed by Azeh.