Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
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.
Offline
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
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.
Offline
"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.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
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.
Offline
^ 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
Offline
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
thanks zoey aaaaaaaaaaaand thanks latif for the avatar
Offline
Thanks, fixed: https://github.com/Tunous/EverybodyEdit … d5bc6c003e
Offline
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.
Offline
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.
Offline
I got 2 questions and would be happy if you could answer them:
Offline
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.
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:
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.
Offline
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?
Offline
EE version is 212 atm. Keep up.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
EE version is 212 atm. Keep up.
Oops didn't even notice that.
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.
Offline
Offline
Thanks, fixed.
Offline
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.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
"Payer"
Offline
Wait, quick chat is free?
Thank you eleizibeth ^
I stack my signatures rather than delete them so I don't lose them
Offline
Srna wrote:Wait, quick chat is free?
Everytime you use quick chat you pay 1 Euro. Did you not know that?
Offline
Koya wrote:Srna wrote: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
Offline
Tbh it used to be 1 cent
For chat, not quick chat
I suggest that for such small, but obviously wrong things, you just suggest a push through git. It's git with a reason.
Offline
Srna wrote: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.
Thank you eleizibeth ^
I stack my signatures rather than delete them so I don't lose them
Offline
[ Started around 1725752528.1215 - Generated in 0.109 seconds, 10 queries executed - Memory usage: 1.91 MiB (Peak: 2.21 MiB) ]