PkHonor

Random goat wrote:that guy veggieburgah cause it i don't think it's a coincidence he told me spam ::fart 1ms and it nulls the server he specifically told me that... and he did that and we all crashed

Tell him to do it again.

I fucking love the help system on here. seriously good job.

Random goat wrote:that guy veggieburgah cause it i don't think it's a coincidence he told me spam ::fart 1ms and it nulls the server he specifically told me that... and he did that and we all crashed

The client doesn't have enough time to process and perform the command(s) when they're spammed 1Ms, the server simply ignores them..
It's the same with chat, you can spam chat as much as you want, only a certain amount of messages will go through in a certain amount of time.

You can try it if you'd like
Edit: For those that want to try it, open 2 clients, log in on both and get your 2 accounts into a private, spam the chat at 1Ms and look at the chatbox on the other client, you'll notice that most of the messages didn't go through.

What Veggieburgah is talking about is exactly true. If you spam ::fart it causes the null.

EDIT: It seems like it has actually been fixed, thanks

Kory pk wrote:What Veggieburgah is talking about is exactly true. If you spam ::fart it causes the null.

EDIT: It seems like it has actually been fixed, thanks

It never worked like that in the first place.

Obsidia wrote:

Kory pk wrote:What Veggieburgah is talking about is exactly true. If you spam ::fart it causes the null.

EDIT: It seems like it has actually been fixed, thanks

It never worked like that in the first place.

Erm... Idk what you think caused the server nulls. But I've actually witnessed it happen.

Kory pk wrote:

Obsidia wrote:

Kory pk wrote:What Veggieburgah is talking about is exactly true. If you spam ::fart it causes the null.

EDIT: It seems like it has actually been fixed, thanks

It never worked like that in the first place.

Erm... Idk what you think caused the server nulls. But I've actually witnessed it happen.

Well first of all, I've spammed several commands including "::fart" at 1 ms SO MANY TIMES in the past, nothing ever happened.

2. Spamming a command that sends a simple message and an performs an emote can't cause a null.

3. You witnessed it? What happened? You spammed the command and the server nulled? Have you taken it into consideration that could've been coincidence?

Obsidia wrote:Well first of all, I've spammed several commands including "::fart" at 1 ms SO MANY TIMES in the past, nothing ever happened.

2. Spamming a command that sends a simple message and an performs an emote can't cause a null.

3. You witnessed it? What happened? You spammed the command and the server nulled? Have you taken it into consideration that could've been coincidence?

That null that just happened 5 minutes ago, I recorded proof and it's already being forwarded to Mike. Hopefully he'll just add a cooldown to emotes, that'll solve it.

Well I'm excited to see if the new code is working as promised, PkHonor 24/7 aye.

Basically what Justin said, it's not ::fart that's directly causing it because the server will ignore messages that are being sent too frequently. I can't tell you how PkHonor is programmed in regards to commands & messages, but from my experience using PI clients & sources I have never effectively been able to do any type of lag or damage to a server with simple commands. There's an unrelated underlying cause to the nulls, it's a pure coincidence that when you spam ::fart that it's nulling the server.