[help] message handler lag

darkblades · 2016-03-08 22:05:10

sometimes in my bot game, it doesnt register "m",'b","say" etc and sometimes don't work at all and starts being delayed by XXXXms. How to deal with this.

Xfrogman43 · 2016-03-08 23:51:44

Can you show us the error? And maybe the code you used?

darkblades · 2016-03-09 00:50:50

this happens. i have alot of code in case m and case b so i have to compress it to this a pseudo code

case "m":
-Gets users response from pressing <- -> /|\ \|/
-for each loop to check if user is near the person within a range
-for each loop to check if the block is not between the user and the person
-decrease "variable" by X
-player pressed \|/
-check bid
-set "itemFound" to block id

case "b":
-set array of block x y block id to 0
-remove all block properties
-sets block timers such as lifespan to 0

hummerz5 · 2016-03-09 05:35:13

Well, thanks, but I'm guessing your pseudocode will not help.

lrussell, Xfrogman43, kubapolish, Swarth100

Tomahawk · 2016-03-10 17:15:41

darkblades wrote:

and starts being delayed by XXXXms

It looks like you're doing quite a lot of processing in "m". If you're dealing with the packets slower than they're arriving, you'll get a buildup of messages and therefore lag. If you build up enough lag, the bot will also disconnect (see this post).

To decrease the lag, you have to make the code quicker/shorter, or find a different way to do it.

God help anyone who recommends threading/multithreading. That's not the problem here.

Koya · 2016-03-12 09:32:41

Tomahawk wrote:

God help anyone who recommends threading/multithreading.

Well it stops messages building up.

Tomahawk · 2016-03-12 14:05:54

Koya wrote:

Well it stops messages building up.

It's not parallel processing, so there won't be any real decrease in the time taken to process a packet. You won't get buildup of messages in PlayerIO's internal buffer; you'll slowly increase the number of active threads instead, which might be worse. It'll still lag.

den3107 · 2016-03-12 18:33:43

Tomahawk wrote:

Koya wrote:
Well it stops messages building up.
It's not parallel processing, so there won't be any real decrease in the time taken to process a packet. You won't get buildup of messages in PlayerIO's internal buffer; you'll slowly increase the number of active threads instead, which might be worse. It'll still lag.

The processing of the message is what's taking long.
Putting that process in a seperate thread will effectively shorten that delay (as you only have to make a thread instead of do the entire process).
Now the downside is that you're still processing one message when the next one comes in and starts processing simultaneously.
So in this case I indeed wouldn't recommend multithreading. But I'm far too inexperienced to really make a solid standing here.

Official Everybody Edits Forums

#1 2016-03-08 22:05:10

[help] message handler lag

#2 2016-03-08 23:51:44

Re: [help] message handler lag

#3 2016-03-09 00:50:50

Re: [help] message handler lag

#4 2016-03-09 05:35:13

Re: [help] message handler lag

#5 2016-03-10 17:15:41, last edited by Tomahawk (2016-03-10 17:25:37)

Re: [help] message handler lag

#6 2016-03-12 09:32:41

Re: [help] message handler lag

#7 2016-03-12 14:05:54

Re: [help] message handler lag

#8 2016-03-12 18:33:43

Re: [help] message handler lag

Board footer