issy123 / agario-protocol Goto Github PK

Packet 64 isn't used anymore. Seems to be all data is included in packet 255 though.

Does anyone know what the latest protocol is?

Message 05 is used to notify client/server about friends.

The client sends message 05 with ascii null terminated string, which lists facebook friend id of all friends separated by character '|'.

For example the string with facebook id list may looks like this: "110139034002111|104404922207222" (these are fake id just for example), where 110139034002111 and 104404922207222 are facebook friend id

When server receives that message it starts to notify if listed players are present on the server. Without it, the server sends just empty 05 message.

The server sends message 05 with ascii null terminated string, which lists facebook friend id of all ONLINE friends separated by character '|'.

with playerId you can find your friends on leaderboard and his cells

Sent from server after client connected to the room, maybe it contains server version.

Example data:

[241, 18, 118, 183, 49]

Does anybody know about this packet!?

how do you bypass anti bots on agario clone like senpa.io and some other's?

bots get packet from agario clone site when they connect
bots can spawn if bots return correct packet

but how do i do that

Basically the protocol is almost the same as previous.

The new client sends the following 2 messages to private server at connection begin:

FE 07 00 00 00  // protocol version 
FF 00 00 00 00  // just ignore it

Protocol 6, 7 change list:

1) Cell Update message 0x10

A little change in the structure of cell update message:

Structure of Eat Record:

Structure of Cell Update Record:

Structure of Remove Record:

The flags:

Message example:

10                                                 // Cell Update message code
02 00                                              // 2 eat records
B5 FF 55 AA E7 FF 55 AA                            // eat record #1
51 FF 55 AA 44 FF 55 AA                            // eat record #2
38 FF 55 AA 59 0B 00 00 7B 00 00 00 CF 00 00       // cell update record #1
51 FF 55 AA 1D 0E 00 00 F0 00 00 00 C5 00 00       // cell update record #2
CC FF 55 AA D3 12 00 00 C8 FE FF FF E4 00 00       // cell update record #3
B5 FF 55 AA D8 0C 00 00 94 FE FF FF 9E 01 00       // cell update record #4
00 00 00 00                                        // cell update record terminator
02 00                                              // 2 remove records
44 FF 55 AA                                        // remove record #1
E7 FF 55 AA                                        // remove record #2

The main difference here is that color and name fields of the cell now is optional and may not be included into message.
The second difference is position of the Flags field. Now it placed before the cell size field.
And third difference is that there is no other fields.
What optional field is included into message is controlled with flags.

This change in update cell message structure leads to problem with private servers with old protocol.
But difference is not significant and can be easily fixed.

2) String encoding

All string encoding were changed to UTF8. It still uses zero-terminated strings, but now strings encoded in UTF8 format. It affects Cell Update message, Leaderboard FFA message and Join command.

3) Clear Message 0x12.

Actually this message was used since protocol 5. But I found that ogar server still uses 0x14 (partial clear message). They both 1-byte length. But the new client uses 0x12. And it's important to send this message just when connection established and also on each join command.

Protocol 20 is just rolled out. Looks that there is no significant difference with protocol 19.

Discovered changes:

1. server version string is moved from Border Update message (0x40) to Cipher Key message (0xF1)

2. Replaced client side encryption key generator, now it depends on server host and server version.

Still under investigation, if you have any info about it, you're welcome.

Who knows dimensions of field are the same!?

I updated https://github.com/SNSA/agario-code to hook custom Websocket to Agar.io. It also allows you to debug pretty version of agario.core.js and of course you can easily put break points there.

Note that whenever the script is outdate, Agar.io will ask to redownload the script. To have latest version of the agario.core.js script, run: gulp update (and don't forget to send a PR to update it).

Packet 112 is sent from server to client, example data:

[112, 49, 55, 55, 55, 52, 49, 52, 52, 57, 56, 51, 53, 57, 51, 55, 50, 55, 57, 54, 55]

Client musts send back packet 112 to complete authentication (without this client cannot spawn), example data:

[113, 124, 3, -106, 47, -90, 92, 16, 78, 119, 97, 73, -13, 9, 75, 104, 100, -8, -75, -27, 123]

Note that packet 113 is calculated from packet 112, if client sends wrong data for packet 113, the server will close the socket by sending back packet 128, see #4

The algorithm is quite complicated, I tried debugging but didn't get much.

These messages was added in protocol 18, but there is still no description, so I just write it here.

Message { 0x72 } is sent from server the the client in response to spectate command. This message leads to show the message "Spectate mode is full".

Message { 0x71, 0x02 } is sent from server to the client after long timeout with no gameplay. The server will disconnect the client just after this message.

Message { 0x71, 0x01 } leads client to disconnect, find new server, connect to it and automatically join the game. I don't have what is the reason for that, but it works in such way ;)

Since 2018/20/12, a new protocol 19 is rolled out. The difference is just in cipher key.
Also added a new message 0x45 - Minimap

sv_protocol 19
sv_secret 0x0000765D
sv_versionClient "3.3.1"
sv_versionProto "12.0.1"

You do not get packet 18 when connecting to an agar server anymore.

May be it will be interesting for someone.
Here is the latest protocol 15:

1) Cell Update message 0x10

A little change in the structure of cell update message:

Structure of Eat Record:

Structure of Cell Update Record:

Structure of Remove Record:

The Flags:

The Extended Flags:

If someone knows some more details, please let me know,
I will update the table.

2) Leaderboard FFA message 0x35

3) Leaderboard FFA teams message 0x36

The structure of FFA Record is the following:

RecordFlags description:

That's it :)
Please let me know if you know more details.

History:
26.05.2018: updated description for Extended flags and leaderboard RecordFlags description

I found very interesting proto-message: agario_proto_User_$skins_$create_$request
But unfortunately there are no usage for this message in the web client.

    agario_proto_User_$skins_$create_$request.prototype = $extend(protohx_Message.prototype, {
        content: null,
        meta: null
    }

It has two string fields: content and meta.
But it's not so clear what content and format is expected for these fields?

Let's look how agario downloading custom skins. For example, here is a data of custom skin:

• https://configs.agario.miniclippt.com/live/custom_skins/skin_custom_a584e270-ae75-4860-b2ae-6425c834d151_38cc8bae-d0ac-453e-98c8-d121bd608c7f.meta
• https://configs.agario.miniclippt.com/live/custom_skins/skin_custom_a584e270-ae75-4860-b2ae-6425c834d151_38cc8bae-d0ac-453e-98c8-d121bd608c7f.png

At a glance, it looks that the meta field should contains meta xml file the same as downloaded from agario server. But what about content field?

Any idea on how to place my custom skin from PNG file into these two string fields? (content and meta)
😊

Can you share us on how you do reverse engineering to get these protocol specification? For example, which tools do you use? This is important because other (many) people can help maintaining the specficiation.

Where are all the problems from?
Why can't it work as well as before?

thank you

World update

• Sent from server to client
• Example data: [128]

This packet asks client to reload agario.core.js, maybe due to outdate version of agario.core.js.

The new protocol 8 is released.

sv_protocol 18
sv_secret 0x00007539
sv_versionClient 3.0.9
sv_versionProto 9.0.2
Server 20.0.3

Almost all is the same, but there are some new messages were introduced.
Primarily related to the new BattleRoyale game mode.
Here it is:

F2 - SERVER TIME

B0 - BATTLE TIMER

B1 - BATTLE START

B2 - BATTLE AREA

B3 - BATTLE EVENT

B4 - BATTLE RESULT

If you have any info about these messages, please let me know

I got another auth tokens

new Int8Array([-2,6,0,0,0]);
new Int8Array([-1,-59,42,64,54]);

Can be the second frame different!?

Send to eject mass

Send to split

Receive: contain view update

idk whats new but its a thing
SERVER SECRET IS 30503