IS this project is Dead Now?

[SSDDX-Devs]

Hey Hello firebolt55439 and other members......
I want to say thanks to all of you for starting this project but now i want to ask you is this project is dead now?

[firebolt55439]

The client side code changes entirely every new version update (appears to be auto generated), as do all the numbers corresponding to tanks and such, not to mention that extension users now face potential bans. Taken together, it's a difficult road to reverse engineering reliably, but you are welcome to help out if you can.

…

On Mar 22, 2017, at 1:14 PM, shubham ***@***.***> wrote: Hey Hello firebolt55439 ...... I want to say thanks to you for starting this project but now i want to ask you is this project is dead now? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[SSDDX-Devs]

Thanks for the reply ! I'm also working on diep.io private server ....... I also tried to de-obfuscate d.js but it really hard they also updated many codes in their last updates now i am using agar.io server to edit it to make it diep.io server ....

[a74]

What if you use a VPN or something like that so you don't get banned?

[firebolt55439]

Unless you would keep changing VPN's after you get banned, the point is moot.

…

On May 9, 2017, at 6:05 PM, Vitali T ***@***.***> wrote: What if you use a VPN or something like that so you don't get banned? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[a74]

I mean something like Tor. I don't know much about this, so yeah.

[firebolt55439]

I'm not 100% sure how Tor works but I believe that the host site also has to be Tor-enabled. Not exactly sure if diep.io is Tor-enabled, but I doubt it would be unfortunately.

…

On May 9, 2017, at 6:32 PM, Vitali T ***@***.***> wrote: I mean something like Tor. I don't know much about this, so yeah. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[a74]

If you use a different IP every time you play (in any way), diep.io won't be able to recognize that you are the person using extensions, because it bases that off of IP. So, I thought Tor would be a way to do that, but not sure if Tor would work with websockets.

[firebolt55439]

Sounds like an idea worth exploring if it can put it into practice. That being said, the client-side Javascript that detects any extensions still needs to be bypassed somehow.

…

On Wed, May 10, 2017 at 11:32 AM, Vitali T ***@***.***> wrote: If you use a different IP every time you play (in any way), diep.io won't be able to recognize that you are the person using extensions, because it bases that off of IP. So, I thought Tor would be a way to do that, but not sure if Tor would work with websockets. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABO7p6IwSqyp0K7Va6E7mCKhj_hf88rlks5r4gKrgaJpZM4Mlwo_> .

-- -Sumer

[a74]

I think I found something. If you use F3 search on the raw prettified d.js, you can see a function called preventExtension. Unless you specifically renamed that, I don't know why exactly it's not obfuscated to a random variable name like XyZ, but you should check it out. https://raw.githubusercontent.com/firebolt55439/Diep.io-Protocol/master/obfuscated_js/prettified.d.js

After you modify it, just remember to use a different IP when testing so that you don't get banned.

[firebolt55439]

Ah in that case it's much easier. Just have to tamper with the client-side JS code to modify the preventExtension function to do nothing. Maybe modify its first line to just return?

…

On May 11, 2017, at 1:02 PM, Vitali T ***@***.***> wrote: I think I found something. If you use F3 search on the raw prettified d.js, you can see a function called preventExtension. Unless you specifically renamed that, I don't know why exactly it's not obfuscated to a random variable name like XyZ, but you should check it out. https://raw.githubusercontent.com/firebolt55439/Diep.io-Protocol/master/obfuscated_js/prettified.d.js After you modify it, just remember to use a different IP when testing so that you don't get banned. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[FlorianCassayre]

Hello there,
I got back to the project very recently and decided to start everything from scratch. This time I only worked on reading the packets (with Wireshark) because the synthetized source code is so bad that it's almost impossible to get something from it.
I managed to fully reverse engineer the game update packet (0x00) for most of the cases (there are multiple branches depending on some values in the packet). I also created a working fake client that connects to a server, sends the initial magic packets, and listens to the incoming traffic.
For the moment I'm a little busy but I will share the code (probably in another repository though because it is in another language) whenever I get a descent basis to work with.

[a74]

Wow, that's great. Does that means you can detect anything and send it packets to do something like turn or move?

[FlorianCassayre]

Yes, I can move the client around, fire and buy upgrades but not yet rotate its cannon (I still need to figure out how the heck he encodes the mouse coordinates, the format is very odd).
Also, it seems that everything that is drawn to the screen is server-sent (in some sort of 'basic' vector format), which doesn't help us in the work. Smart developer.

[a74]

Do you know how to access the minimap? I want to be able to detect the current position on it. By the way, any progress on the barrel rotation?

[FlorianCassayre]

The minimap is sent through packet 0x00 (like almost everything else), but where... I think the player coordinates are stored in the null id entity (more informations about the entity system when I publish the code).
For the barrel I got nothing more besides that:

• After the two bytes mapping the controls (plus the packet id), two varint can be read
• The first varint corresponds to the mouse x coordinate relatively to the map (in a format I can't understand), and the second is for the y coordinate