So about the latest update...

den3107 · 2017-03-17 15:31:28

As most of you probably already read:

Changelog wrote:

– Removed message limit for world owners (useful for bots, I guess).

Great news! Right?

Well, in my opinion, yeah.
But you can't just remove all "Thread.Sleep"s (or whatever you use).

While for chat the minimal delay seems to still be in effect (not that big of a problem...), however for building...
I'd say: try it out, but then I'd technically be encouraging you to DDoS EE, so I'm not going to say anything
So as I said: don't just remove your delay method yet. If you do, you will be kicked from your world after a couple dozen blocks (just you, not other players).
HOWEVER... Putting in a Thread.Sleep(1); is already good enough for the servers. Then again, this doesn't guarantee to wait exactly 1ms, but probably a bit longer.
HOWEVER (again)... This is still WAY better than the 10ms delay we were limited by before.

With this update it would, for example, be possible to make a (decently working) public animator bot, like requested a little while ago!

Still have to figure out myself why exactly I wrote this post... But hey, man's gotta do something when he's bored, eh?

SmittyW · 2017-03-17 15:38:53

I can send approximately 11,250 blocks (or 150 x 75) with 1ms delay before getting disconnected. Huge improvement.

Why didn't they do this before? What issues will this cause? I recall Cjmaeder adding a "fill" message before but removed it...

LukeM · 2017-03-17 16:03:07

Just to let you know, having Thread.Sleep(1) is almost exactly the same as having Thread.Sleep(10), they both sleep for around 15-20ms
If you want to place blocks faster (using thread.sleep) then you will need to place multiple per sleep

Gosha · 2017-03-17 16:04:09

SmittyW wrote:

Why didn't they do this before?

because Nou was leader

Latif · 2017-03-17 16:09:20

Gosha wrote:

SmittyW wrote:
Why didn't they do this before?
because Nou was leader

Is that serious??

LukeM · 2017-03-17 16:48:14

Latif wrote:

Gosha wrote:
SmittyW wrote:
Why didn't they do this before?
because Nou was leader
Is that serious??

The reason nou didnt want it is because blocks cause lag...

Also: Ive been testing it, and managed about 2000 blocks per second, any more than that and it disconnects most people from the world

Latif · 2017-03-17 20:03:50

destroyer123 wrote:

Latif wrote:
Gosha wrote:
SmittyW wrote:
Why didn't they do this before?
because Nou was leader
Is that serious??
The reason nou didnt want it is because blocks cause lag...
Also: Ive been testing it, and managed about 2000 blocks per second, any more than that and it disconnects most people from the world

That's nice. I think it should stay owner-only so it's your own risk if people lose connection because of your bot.

Gosha · 2017-03-17 20:10:20

Latif wrote:

That's nice. I think it should stay owner-only so it's your own risk if people lose connection because of your bot.

it is already onwer-only

Zumza · 2017-03-17 20:51:10

After my statistics, the block placing is ~70% faster than in September 2015(last time I recorded).
However I can't credit EE for all this difference. My ISP most likely made road upgrades to their equipment, PlayerIO servers aren't longer under Yahoo, less players are online in this game etc.

Latif

Latif · 2017-03-17 22:01:21

Gosha wrote:

Latif wrote:
That's nice. I think it should stay owner-only so it's your own risk if people lose connection because of your bot.
it is already onwer-only

Oh I think you misunderstand me. I already know it's owner-only, I just don't want it to get changed.

Gosha

den3107 · 2017-03-18 01:40:48

Latif wrote:

I think it should stay owner-only so it's your own risk if people lose connection because of your bot.

Others actually wouldn't generally get kicked out, only the person (owner) spamming blocks, unless the other players would have trouble processing data and their EE simply crashes.

destroyer123 wrote:

Also: Ive been testing it, and managed about 2000 blocks per second, any more than that and it disconnects most people from the world

It works kinda strange, it seems like the server itself auto-kicks you when you send blocks too quickly.
eg: When I place 25 blocks without delay. I'm kicked. If I player 25x25 blocks without delay, I also get kicked. However in both situations all blocks ARE placed.
So it seems like it kicks you after x blocks with too little delay, but as you have already sent all the placement requests to the server before you receive the message that you're kicked out, the server still actually does process all those messages.

Haven't really tried out what value x actually is (if it's even a static number).

Tomahawk · 2017-03-18 01:44:31

den3107 wrote:

It works kinda strange, it seems like the server itself auto-kicks you when you send blocks too quickly.eg: When I place 25 blocks without delay. I'm kicked. If I player 25x25 blocks without delay, I also get kicked. However in both situations all blocks ARE placed.So it seems like it kicks you after x blocks with too little delay, but as you have already sent all the placement requests to the server before you receive the message that you're kicked out, the server still actually does process all those messages.Haven't really tried out what value x actually is (if it's even a static number).

I think it's entirely your connection. I can place 200 without delay.

Sometimes both the bot and I disconnect, sometimes only I disconnect, and sometimes only the bot disconnects. Seems kinda random.

Official Everybody Edits Forums

#1 2017-03-17 15:31:28

So about the latest update...

#2 2017-03-17 15:38:53

Re: So about the latest update...

#3 2017-03-17 16:03:07

Re: So about the latest update...

#4 2017-03-17 16:04:09

Re: So about the latest update...

#5 2017-03-17 16:09:20

Re: So about the latest update...

#6 2017-03-17 16:48:14, last edited by LukeM (2017-03-17 16:48:35)

Re: So about the latest update...

#7 2017-03-17 20:03:50

Re: So about the latest update...

#8 2017-03-17 20:10:20

Re: So about the latest update...

#9 2017-03-17 20:51:10, last edited by Zumza (2017-03-17 20:56:06)

Re: So about the latest update...

#10 2017-03-17 22:01:21

Re: So about the latest update...

#11 2017-03-18 01:40:48

Re: So about the latest update...

#12 2017-03-18 01:44:31

Re: So about the latest update...

Board footer