Protocol documentation

Thanel · 2016-02-16 21:38:12

Edit: the new unofficial documentation is found here. (Credits: capasha)

Here you can find the detailed documentation for the Everybody Edits game protocol.
I'll be keeping it up to date with each version and you'll be able to directly see commits or releases to find what changed.

SirJosh3917, Hexagon, Falk, CatoniC, !nb4, Swarth100, AlphaJon, IWillStalkYou, Awesomenessgood, MartenM, Jesse, Zumza, coinage, Xfrogman43, Koya, N1KF, kubapolish, Priddle, 912468, Processor, capasha, xJeex, XxAtillaxX, Latif, Kikikan, Goldy301, Kingfdamt6579, Anch, DarkDragon4900, The Living SticK, jonhvictor2004sonic, Crospy1, Tomahawk, F4ncy, 1448, Gosha, Krosis, rold1212, wiktorian, nielsd, cercul1, skull111 forum

den3107 · 2016-02-16 23:44:56

Even though it's a shame it only came out this late, I'm still glad to finally see it, looks like a charm too.

Hexagon · 2016-02-16 23:46:53

It's really nice that it's on GitHub because then you can do a diff between the commits and see what new events were added in between versions.

Xfrogman43, AlphaJon, Koya, Priddle, coinage, Jesse, F4ncy

Tomahawk · 2016-02-29 00:08:04

"m" is currently incorrect;

You've missed out "int Player Id" at index 0, and (at least in the message received by a bot) there's no Tick Id at what is currently index 11.

Kaslai · 2016-02-29 00:18:27

So you mean I can have my bots just scrape this data for things like which part of init is world width and height, and thereby be very future-proof? Woah man. Woah.

hummerz5 · 2016-02-29 00:52:14

^ Huh. iirc I didn't make that suggestion. Darn.

but yeah, maybe, instead of "scraping" we actually set up something less sketchy?

then we don't have to worry. instead of bots breaking down, they could have a better response to when certain parts of EE's messages are discontinued or added to. I mean, we could guess which one's the world height/width, but not particularly reliably lol

Xfrogman43 · 2016-03-28 21:59:05

Please change this.

1) Why is layer not 0?
2) Why is "morph" not just blockID? I thought it was the argument for rotation
3) Why can't this just be in "b" with an argument of "rotation"

x,y,morph,layer

Thanel · 2016-03-29 12:59:30

Thanks, fixed: https://github.com/Tunous/EverybodyEdit … d5bc6c003e

Xfrogman43

den3107 · 2016-06-11 12:18:02

Found an error thanks to this thread by koozing.
http://prntscr.com/bf1c4u
Screenshot above shows id's for tele message are 0-1-0-1-2-3, obviously this should be 0-1-2-3-4-5.

Thanel · 2016-06-11 15:26:11

den3107 wrote:

Found an error thanks to this thread by koozing.
http://prntscr.com/bf1c4u
Screenshot above shows id's for tele message are 0-1-0-1-2-3, obviously this should be 0-1-2-3-4-5.

I've changed the format a bit to make it clear that these properties have dynamic ids.

den3107 · 2016-07-05 18:41:32

I got 2 questions and would be happy if you could answer them:

▼question 1

▼question 2

Thanel · 2016-07-05 19:15:52

den3107 wrote:

I assume the parameter names (and descriptions, though not interested in those) are "official"?
The reason I'm asking is because I'm wanting to make a library that would make bots resilient to protocol changes by using the github repo (programmers will use names/enum values to retrieve data from received messages).

The names are mostly from the code of unity ee. They were selected to be as descriptive about their meaning for readers as possible. I assume you can call them official. I'm open to changing them if something is not understandable.

den3107 wrote:

Are there any plans to include the following things to the models section (probably forgetting a couple things)?
1) Blocks names, IDs, morphability and amount of morphs, minimap color;
2) Smileys names (already present in shop.md) and IDs;
3) Aura color names and IDs;
4) Aura style (already present in shop.md) and IDs.
P.S. Obviously I can understand blocks (and smileys too) will be quite a chore, but maybe if somebody got a list somewhere (or could even use botbits source) to extract and format is from there automatically using a couple regex' (could help if you have no regex experience) and a custom program obviously.

There are no plans on adding these things to the protocol. Shop.md is included as it was provided by community. If you want and have time to create and share additional data that might be useful for others then I'll definitely add it, but won't promise on keeping updated. The only part of the repository that I'm going to be making sure to have always up to date is the protocol itself.

Although considering that now the whole data is saved in a much better way, I might decide to share it directly from unity ee. I would just have to add small exporting method to my Item Manager to save it with small changes from the default one:

▼Hidden text

It includes both packages, blocks, smileys, aura colors and shapes. But that's a low priority now. I might look into it once the unity version is ready.

You can also check this for minimap colors and images: https://github.com/EEJesse/EEBlocks. Note that it's not something that I'm updating myself so it might be outdated.

Hexagon

den3107 · 2016-07-05 19:36:03

I (and I think a big portion of the bot community) would indeed be very thankful if you could publish that spoiler (though obviously a different format (JSON?) would be desirable, though not required) with every EE update.

off-topic: I assume there still isn't any rough ETA for the Unity port? Like end summer vacation, end 2016, middle 2017?

MartenM

Tomahawk · 2016-07-13 17:49:41

EE version is 212 atm. Keep up.

Thanel · 2016-07-13 18:34:03

Tomahawk wrote:

EE version is 212 atm. Keep up.

Oops didn't even notice that.

den3107 wrote:

I assume there still isn't any rough ETA for the Unity port? Like end summer vacation, end 2016, middle 2017?

There is no ETA.

SirJosh3917 · 2016-08-13 23:35:33

Thanel

Thanel · 2016-08-13 23:41:23

Thanks, fixed.

Latif

Tomahawk · 2016-08-30 17:39:18

Thanel, have you considered going into more detail about the block data in "init"? It might be the most difficult thing to use, but your documentation should aim to list and explain all of the data a bot can receive.

I'd explain the order of the block data and how the byte arrays worked. I.E. [ID, X array, Y array, extra params], repeated for each block ID. You wouldn't need to explain how to deserialise the arrays, but only that each coord comes in two parts of 8 bits which must be combined to get its value.

EDIT: Forgot the layer.

Thanel, Xfrogman43

Thanel · 2016-08-30 19:57:25

Hmm I didn't consider that. It sounds like a good idea.

I created issue here to track this. I'll try to come up with some ideas and share them when I get time.

Srna · 2016-09-07 16:17:14

"Payer"

Thanel

Koya · 2016-09-07 20:05:20

Srna wrote:

http://i.imgur.com/98XaqWy.png
"Payer"

Wait, quick chat is free?

Jesse

MartenM · 2016-09-07 20:12:47

Koya wrote:

Srna wrote:
http://i.imgur.com/98XaqWy.png
"Payer"
Wait, quick chat is free?

Everytime you use quick chat you pay 1 Euro. Did you not know that?

Koya, Swarth100

Swarth100 · 2016-09-07 21:09:57

MartenM wrote:

Koya wrote:
Srna wrote:
http://i.imgur.com/98XaqWy.png
"Payer"
Wait, quick chat is free?
Everytime you use quick chat you pay 1 Euro. Did you not know that?

Tbh it used to be 1 cent

den3107 · 2016-09-07 22:06:25

Swarth100 wrote:

Tbh it used to be 1 cent

For chat, not quick chat

Srna wrote:

http://i.imgur.com/98XaqWy.png
"Payer"

I suggest that for such small, but obviously wrong things, you just suggest a push through git. It's git with a reason.

Jesse

Koya · 2016-09-08 06:48:16

den3107 wrote:

Srna wrote:
http://i.imgur.com/98XaqWy.png
"Payer"
I suggest that for such small, but obviously wrong things, you just suggest a push through git. It's git with a reason.

Not everyone knows how to use github.

Also, suggested a push to correct some mistakes 11 days ago and it hasn't been merged.

MartenM

Official Everybody Edits Forums

#1 2016-02-16 21:38:12, last edited by hummerz5 (2018-09-04 14:15:43)

Protocol documentation

#2 2016-02-16 23:44:56

Re: Protocol documentation

#3 2016-02-16 23:46:53

Re: Protocol documentation

#4 2016-02-29 00:08:04, last edited by Tomahawk (2016-02-29 00:09:54)

Re: Protocol documentation

#5 2016-02-29 00:18:27

Re: Protocol documentation

#6 2016-02-29 00:52:14

Re: Protocol documentation

#7 2016-03-28 21:59:05, last edited by Xfrogman43 (2016-03-28 21:59:56)

Re: Protocol documentation

#8 2016-03-29 12:59:30

Re: Protocol documentation

#9 2016-06-11 12:18:02

Re: Protocol documentation

#10 2016-06-11 15:26:11

Re: Protocol documentation

#11 2016-07-05 18:41:32, last edited by den3107 (2016-07-05 18:42:56)

Re: Protocol documentation

#12 2016-07-05 19:15:52, last edited by Thanel (2016-07-05 19:18:04)

Re: Protocol documentation

#13 2016-07-05 19:36:03

Re: Protocol documentation

#14 2016-07-13 17:49:41

Re: Protocol documentation

#15 2016-07-13 18:34:03

Re: Protocol documentation

#16 2016-08-13 23:35:33

Re: Protocol documentation

#17 2016-08-13 23:41:23

Re: Protocol documentation

#18 2016-08-30 17:39:18, last edited by Tomahawk (2016-08-31 17:57:35)

Re: Protocol documentation

#19 2016-08-30 19:57:25

Re: Protocol documentation

#20 2016-09-07 16:17:14

Re: Protocol documentation

#21 2016-09-07 20:05:20

Re: Protocol documentation

#22 2016-09-07 20:12:47

Re: Protocol documentation

#23 2016-09-07 21:09:57

Re: Protocol documentation

#24 2016-09-07 22:06:25, last edited by den3107 (2016-09-07 22:06:39)

Re: Protocol documentation

#25 2016-09-08 06:48:16

Re: Protocol documentation

Board footer