« previous next »
Pages: [1] 2

Author Topic: Is this a DDOS?  (Read 3397 times)

-Paint-

July 16, 2015, 02:11:29 AM
I was gonna join Paintingcan's server today, but it wasn't up. I never shut it down so I checked the console on Putty. It was filled with this:

Is this a ddos?

Add-Ons/Weapon_DWeapons/basic.cs (476): Unable to find object: '' attempting to call function 'setControlCameraFov'
BackTrace: ->ProjectileData::onExplode->ProjectileData::radiusDamage->ShapeBase::Damage->[gc_MilGearPackage]Armor::Damage->[MagicStone]Armor::Damage->[MagicLightning]Armor::Damage->Armor::Damage->[VCE_Main]GameConnection::onDeath->[Slayer_Modules_TLT]GameConnection::onDeath->[VCE_Cash]GameConnection::onDeath->[MagicIce]GameConnection::onDeath->[gc_ScopesPackage]GameConnection::onDeath

Starting arranged connection to 67.49.9.191:7906...
   o possible[0] = 67.49.9.191:7906
   o possible[1] = 10.1.0.34:7906
   o possible[2] = 127.0.0.1:7906
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Starting arranged connection to 207.255.19.50:50426...
   o possible[0] = 207.255.19.50:50426
   o possible[1] = 192.168.1.113:50426
   o possible[2] = 192.168.1.108:50426
   o possible[3] = 25.237.52.18:50426
   o possible[4] = 127.0.0.1:50426
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Starting arranged connection to 207.255.19.50:50426...
   o possible[0] = 207.255.19.50:50426
   o possible[1] = 192.168.1.113:50426
   o possible[2] = 192.168.1.108:50426
   o possible[3] = 25.237.52.18:50426
   o possible[4] = 127.0.0.1:50426
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Starting arranged connection to 67.49.9.191:7906...
   o possible[0] = 67.49.9.191:7906
   o possible[1] = 10.1.0.34:7906
   o possible[2] = 127.0.0.1:7906
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Starting arranged connection to 77.100.31.69:50209...
   o possible[0] = 77.100.31.69:50209
   o possible[1] = 169.254.172.243:50209
   o possible[2] = 169.254.123.79:50209
   o possible[3] = 169.254.37.72:50209
   o possible[4] = 192.168.1.6:50209
   o possible[5] = 25.13.240.81:50209
   o possible[6] = 127.0.0.1:50209
Sending punch packet to 77.100.31.69:50209
Sending punch packet to 169.254.172.243:50209
Sending punch packet to 169.254.123.79:50209
Sending punch packet to 169.254.37.72:50209
Sending punch packet to 192.168.1.6:50209
Sending punch packet to 25.13.240.81:50209
Sending punch packet to 127.0.0.1:50209
Starting arranged connection to 67.49.9.191:7906...
   o possible[0] = 67.49.9.191:7906
   o possible[1] = 10.1.0.34:7906
   o possible[2] = 127.0.0.1:7906
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Starting arranged connection to 189.234.165.118:36853...
   o possible[0] = 189.234.165.118:36853
   o possible[1] = 169.254.99.244:36853
   o possible[2] = 192.168.1.71:36853
   o possible[3] = 169.254.224.225:36853
   o possible[4] = 127.0.0.1:36853
Sending punch packet to 189.234.165.118:36853
Sending punch packet to 169.254.99.244:36853
Sending punch packet to 192.168.1.71:36853
Sending punch packet to 169.254.224.225:36853
Sending punch packet to 127.0.0.1:36853
Starting arranged connection to 99.13.69.6:7673...
   o possible[0] = 99.13.69.6:7673
   o possible[1] = 127.0.0.1:7673
   o possible[2] = 192.168.1.87:7673
Sending punch packet to 99.13.69.6:7673
Sending punch packet to 127.0.0.1:7673
Sending punch packet to 192.168.1.87:7673
Starting arranged connection to 191.33.241.50:26792...
   o possible[0] = 191.33.241.50:26792
   o possible[1] = 169.254.109.192:26792
   o possible[2] = 192.168.1.2:26792
   o possible[3] = 169.254.143.241:26792
   o possible[4] = 127.0.0.1:26792
Sending punch packet to 191.33.241.50:26792
Sending punch packet to 169.254.109.192:26792
Sending punch packet to 192.168.1.2:26792
Sending punch packet to 169.254.143.241:26792
Sending punch packet to 127.0.0.1:26792
Starting arranged connection to 76.94.138.243:63507...
   o possible[0] = 76.94.138.243:63507
   o possible[1] = 192.168.0.6:63507
   o possible[2] = 127.0.0.1:63507
Sending punch packet to 76.94.138.243:63507
Sending punch packet to 192.168.0.6:63507
Sending punch packet to 127.0.0.1:63507
Starting arranged connection to 81.106.169.108:41603...
   o possible[0] = 81.106.169.108:41603
   o possible[1] = 169.254.182.237:41603
   o possible[2] = 169.254.146.99:41603
   o possible[3] = 169.254.212.139:41603
   o possible[4] = 192.168.0.8:41603
   o possible[5] = 127.0.0.1:41603
Sending punch packet to 81.106.169.108:41603
Sending punch packet to 169.254.182.237:41603
Sending punch packet to 169.254.146.99:41603
Sending punch packet to 169.254.212.139:41603
Sending punch packet to 192.168.0.8:41603
Sending punch packet to 127.0.0.1:41603
Client 462638 disconnected.
Issuing Disconnect packet.
Saving persistence for BLID 38818
CDROP: 462638 - grasshopper - 23.240.187.54:59776
Posting to master server
Posting to rtb server
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 77.100.31.69:50209
Sending punch packet to 169.254.172.243:50209
Sending punch packet to 169.254.123.79:50209
Sending punch packet to 169.254.37.72:50209
Sending punch packet to 192.168.1.6:50209
Sending punch packet to 25.13.240.81:50209
Sending punch packet to 127.0.0.1:50209
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 189.234.165.118:36853
Sending punch packet to 169.254.99.244:36853
Sending punch packet to 192.168.1.71:36853
Sending punch packet to 169.254.224.225:36853
Sending punch packet to 127.0.0.1:36853
Sending punch packet to 99.13.69.6:7673
Sending punch packet to 127.0.0.1:7673
Sending punch packet to 192.168.1.87:7673
Sending punch packet to 191.33.241.50:26792
Sending punch packet to 169.254.109.192:26792
Sending punch packet to 192.168.1.2:26792
Sending punch packet to 169.254.143.241:26792
Sending punch packet to 127.0.0.1:26792
Sending punch packet to 76.94.138.243:63507
Sending punch packet to 192.168.0.6:63507
Sending punch packet to 127.0.0.1:63507
Sending punch packet to 81.106.169.108:41603
Sending punch packet to 169.254.182.237:41603
Sending punch packet to 169.254.146.99:41603
Sending punch packet to 169.254.212.139:41603
Sending punch packet to 192.168.0.8:41603
Sending punch packet to 127.0.0.1:41603
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 77.100.31.69:50209
Sending punch packet to 169.254.172.243:50209
Sending punch packet to 169.254.123.79:50209
Sending punch packet to 169.254.37.72:50209
Sending punch packet to 192.168.1.6:50209
Sending punch packet to 25.13.240.81:50209
Sending punch packet to 127.0.0.1:50209
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 189.234.165.118:36853
Sending punch packet to 169.254.99.244:36853
Sending punch packet to 192.168.1.71:36853
Sending punch packet to 169.254.224.225:36853
Sending punch packet to 127.0.0.1:36853
Sending punch packet to 99.13.69.6:7673
Sending punch packet to 127.0.0.1:7673
Sending punch packet to 192.168.1.87:7673
Sending punch packet to 191.33.241.50:26792
Sending punch packet to 169.254.109.192:26792
Sending punch packet to 192.168.1.2:26792
Sending punch packet to 169.254.143.241:26792
Sending punch packet to 127.0.0.1:26792
Sending punch packet to 76.94.138.243:63507
Sending punch packet to 192.168.0.6:63507
Sending punch packet to 127.0.0.1:63507
Sending punch packet to 81.106.169.108:41603
Sending punch packet to 169.254.182.237:41603
Sending punch packet to 169.254.146.99:41603
Sending punch packet to 169.254.212.139:41603
Sending punch packet to 192.168.0.8:41603
Sending punch packet to 127.0.0.1:41603
AUTHCHECK: Luio88 = internet client -> internet server, regular auth
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 77.100.31.69:50209
Sending punch packet to 169.254.172.243:50209
Sending punch packet to 169.254.123.79:50209
Sending punch packet to 169.254.37.72:50209
Sending punch packet to 192.168.1.6:50209
Sending punch packet to 25.13.240.81:50209
Sending punch packet to 127.0.0.1:50209
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 189.234.165.118:36853
Sending punch packet to 169.254.99.244:36853
Sending punch packet to 192.168.1.71:36853
Sending punch packet to 169.254.224.225:36853
Sending punch packet to 127.0.0.1:36853
Sending punch packet to 99.13.69.6:7673
Sending punch packet to 127.0.0.1:7673
Sending punch packet to 192.168.1.87:7673
Sending punch packet to 191.33.241.50:26792
Sending punch packet to 169.254.109.192:26792
Sending punch packet to 192.168.1.2:26792
Sending punch packet to 169.254.143.241:26792
Sending punch packet to 127.0.0.1:26792
Sending punch packet to 76.94.138.243:63507
Sending punch packet to 192.168.0.6:63507
Sending punch packet to 127.0.0.1:63507
Sending punch packet to 81.106.169.108:41603
Sending punch packet to 169.254.182.237:41603
Sending punch packet to 169.254.146.99:41603
Sending punch packet to 169.254.212.139:41603
Sending punch packet to 192.168.0.8:41603
Sending punch packet to 127.0.0.1:41603
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 77.100.31.69:50209
Sending punch packet to 169.254.172.243:50209
Sending punch packet to 169.254.123.79:50209
Sending punch packet to 169.254.37.72:50209
Sending punch packet to 192.168.1.6:50209
Sending punch packet to 25.13.240.81:50209
Sending punch packet to 127.0.0.1:50209
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 189.234.165.118:36853
Sending punch packet to 169.254.99.244:36853
Sending punch packet to 192.168.1.71:36853
Sending punch packet to 169.254.224.225:36853
Sending punch packet to 127.0.0.1:36853
Sending punch packet to 99.13.69.6:7673
Sending punch packet to 127.0.0.1:7673
Sending punch packet to 192.168.1.87:7673
Sending punch packet to 191.33.241.50:26792
Sending punch packet to 169.254.109.192:26792
Sending punch packet to 192.168.1.2:26792
Sending punch packet to 169.254.143.241:26792
Sending punch packet to 127.0.0.1:26792
Sending punch packet to 76.94.138.243:63507
Sending punch packet to 192.168.0.6:63507
Sending punch packet to 127.0.0.1:63507
Sending punch packet to 81.106.169.108:41603
Sending punch packet to 169.254.182.237:41603
Sending punch packet to 169.254.146.99:41603
Sending punch packet to 169.254.212.139:41603
Sending punch packet to 192.168.0.8:41603
Sending punch packet to 127.0.0.1:41603
AUTHCHECK: Chewy = internet client -> internet server, regular auth
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 77.100.31.69:50209
Sending punch packet to 169.254.172.243:50209
Sending punch packet to 169.254.123.79:50209
Sending punch packet to 169.254.37.72:50209
Sending punch packet to 192.168.1.6:50209
Sending punch packet to 25.13.240.81:50209
Sending punch packet to 127.0.0.1:50209
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 189.234.165.118:36853
Sending punch packet to 169.254.99.244:36853
Sending punch packet to 192.168.1.71:36853
Sending punch packet to 169.254.224.225:36853
Sending punch packet to 127.0.0.1:36853
Sending punch packet to 99.13.69.6:7673
Sending punch packet to 127.0.0.1:7673
Sending punch packet to 192.168.1.87:7673
Sending punch packet to 191.33.241.50:26792
Sending punch packet to 169.254.109.192:26792
Sending punch packet to 192.168.1.2:26792
Sending punch packet to 169.254.143.241:26792
Sending punch packet to 127.0.0.1:26792
Sending punch packet to 76.94.138.243:63507
Sending punch packet to 192.168.0.6:63507
Sending punch packet to 127.0.0.1:63507
Sending punch packet to 81.106.169.108:41603
Sending punch packet to 169.254.182.237:41603
Sending punch packet to 169.254.146.99:41603
Sending punch packet to 169.254.212.139:41603
Sending punch packet to 192.168.0.8:41603
Sending punch packet to 127.0.0.1:41603
AUTHCHECK: RedcoatJoe = internet client -> internet server, regular auth
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 207.255.19.50:50426
Sending punch packet to 192.168.1.113:50426
Sending punch packet to 192.168.1.108:50426
Sending punch packet to 25.237.52.18:50426
Sending punch packet to 127.0.0.1:50426
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 77.100.31.69:50209
Sending punch packet to 169.254.172.243:50209
Sending punch packet to 169.254.123.79:50209
Sending punch packet to 169.254.37.72:50209
Sending punch packet to 192.168.1.6:50209
Sending punch packet to 25.13.240.81:50209
Sending punch packet to 127.0.0.1:50209
Sending punch packet to 67.49.9.191:7906
Sending punch packet to 10.1.0.34:7906
Sending punch packet to 127.0.0.1:7906
Sending punch packet to 189.234.165.118:36853
Sending punch packet to 169.254.99.244:36853
Sending punch packet to 192.168.1.71:36853
Sending punch packet to 169.254.224.225:36853
Sending punch packet to 127.0.0.1:36853
Sending punch packet to 99.13.69.6:7673
Sending punch packet to 127.0.0.1:7673
Sending punch packet to 192.168.1.87:7673
Sending punch packet to 191.33.241.50:26792
Sending punch packet to 169.254.109.192:26792
Sending punch packet to 192.168.1.2:26792
Sending punch packet to 169.254.143.241:26792
Sending punch packet to 127.0.0.1:26792
Sending punch packet to 76.94.138.243:63507
Sending punch packet to 192.168.0.6:63507
Sending punch packet to 127.0.0.1:63507
Sending punch packet to 81.106.169.108:41603
Sending punch packet to 169.254.182.237:41603
Sending punch packet to 169.254.146.99:41603
Sending punch packet to 169.254.212.139:41603
Sending punch packet to 192.168.0.8:41603
Sending punch packet to 127.0.0.1:41603

Is my console.log where it starts to get shady. "MagicIce" is the person who started it. Earlier that day someone called DDoS joined but left just as I restarted, so the ID was wiped from bricks page.

Ad Bot

Advertisement

Kyuande

July 16, 2015, 04:15:07 AM
Interesting, multiple IPs are doing this. If the server was lagging vadly, I guess you could call it a DDoS.

Kyuande

July 16, 2015, 04:15:31 AM
Badly* haha oops

-Paint-

July 16, 2015, 09:37:10 AM
It managed to crash it.

Damp

July 16, 2015, 09:48:31 AM
aw i wanted to join bad

Greek2me

July 16, 2015, 09:54:37 AM
No, that looks like a normal connection attempt.

Agent Legit 22

July 16, 2015, 09:58:53 AM
Maybe, Or everyone wants to join at once.

joe411

July 16, 2015, 01:56:59 PM
Please upload the console.log file under "Additional Options" instead of pasting into your post.

Gytyyhgfffff

July 16, 2015, 02:50:31 PM
Quote from: Greek2me on July 16, 2015, 09:54:37 AM
No, that looks like a normal connection attempt.
"a normal connection attempt"

we're going to need a full console.log if we're going to figure anything out. if those connections go on for more than a thousand lines chances are it was some sort of connection-spam-exploit-attack-thing

Ipquarx

July 16, 2015, 05:09:15 PM
The problem is we don't know the timespan between the messages. There could be multiple minutes between the messages.

Also, a lot of those are local IPs, they wouldn't have any effect and/or don't come from outside.

Gytyyhgfffff

July 16, 2015, 05:59:58 PM
Quote from: Ipquarx on July 16, 2015, 05:09:15 PM
The problem is we don't know the timespan between the messages. There could be multiple minutes between the messages.

Also, a lot of those are local IPs, they wouldn't have any effect and/or don't come from outside.
doesn't auth checking usually happen for a set of clients at the same time
if you see in the logs, you can see multiple connection attempts between 3 auth checks, which probably means that the timespan between the connection attempts is pretty small

Goth77

July 18, 2015, 09:38:58 PM
Quote from: Greek2me on July 16, 2015, 09:54:37 AM
No, that looks like a normal connection attempt.

It looks like the server was probably over-loaded on the network side and went dead. The people who were already at the server were able to stay, and I bet got very laggy at that point for them.

I wouldn't blame this on any DDoS, unless you can pull up some log files from your router and prove that someone was spamming connections from the same IP (or couple of IP's) over and over again, within a 5-10 second period of time.

This looks exactly as Greek2Me is describing, and since most of those IP's are different (even some local IP connection attempts, which tells me you were trying to join your own server seemingly with no success) I would guess the server just went dead, and people could no longer join, but the people who were still AT the server were not kicked, but experienced some good lag.

Someone probably spammed with bots/events or something, or if the server has VCE you are potentially vulnerable to network-side lag-threats unless you use restricted events to prevent VCE abuse.

 
Quote from: -Paint- on July 16, 2015, 02:11:29 AM
Add-Ons/Weapon_DWeapons/basic.cs (476): Unable to find object: '' attempting to call function 'setControlCameraFov'
BackTrace: ->ProjectileData::onExplode->ProjectileData::radiusDamage->ShapeBase::Damage->[gc_MilGearPackage]Armor::Damage->[MagicStone]Armor::Damage->[MagicLightning]Armor::Damage->Armor::Damage->[VCE_Main]GameConnection::onDeath->[Slayer_Modules_TLT]GameConnection::onDeath->[VCE_Cash]GameConnection::onDeath->[MagicIce]GameConnection::onDeath->[gc_ScopesPackage]GameConnection::onDeath
Seems to be a conflict in the code with Slayer and Gravity Cats Military Gear
I don't think it would crash the server, but since it is a packaged client-side function, it could potentially break things unknowlingly such as the ability to join a server after someone died in-game.

Let Greek2Me take a look at DWeapons, Gravity Cats Military Gear, and the version of Slayer you are using. Provided he's willingly to take some time to help I am sure he can figure the problem; If not I guess I could help if you were to send all 3 zips and take a look for myself.

As I said before though, I highly doubt the add-on(s) in question have any likelyhood with the server going down, but you can never be too sure when dealing with important client-sided functions such as ::OnDeath

Kyuande

July 19, 2015, 07:33:46 AM
Quote from: Goth77 on July 18, 2015, 09:38:58 PM
Seems to be a conflict in the code with Slayer and Gravity Cats Military Gear
I don't think it would crash the server, but since it is a packaged client-side function,
Lol what

Goth77

July 19, 2015, 11:23:33 PM
Quote from: Kyuande on July 19, 2015, 07:33:46 AM
Lol what
GameConnection::onDeath(%this) <-- %this = client
^ The Client

phflack

July 19, 2015, 11:36:48 PM
Quote from: Goth77 on July 19, 2015, 11:23:33 PM
GameConnection::onDeath(%this) <-- %this = client
^ The Client
it's a server function on a client object
by your logic, it looks like every server, I repeat, SERVER command would be client sided
even though it's normally just about completely server sided, at most a GUI or keybind calling the command from the client
Pages: [1] 2
« previous next »