search

ClitherProject / Slither.io-Protocol

The Documented Slither.io Protocol
151 stars 37 forks source link

Update to protocol 12 #89

Closed Mat2095 closed 5 years ago

Mat2095 commented 5 years ago

Current protocol is 12, the documentation should be adjusted to that. However, protocol 11 is working with the current live servers.

Mat2095 commented 5 years ago

Hm, it seems like the current official client only supports protocol 11, however it is possible to request protocol 12, so the official server supports version 12. But since there is no client, reverse-engineering version 12 would be quite hard and not yet necessary.

Mat2095 commented 5 years ago

There are some recent update-notes on android:

argmanda commented 5 years ago

tengo los bots pero no me siguen solo van asia la derecha alguna solucion a eso

Mat2095 commented 5 years ago

@argmanda Please write in English.

argmanda commented 5 years ago

Mat2095 sorry and fix the bots work fine .. thanks anyway https://imgur.com/bVaiVrG

Mat2095 commented 5 years ago

I think the mystery is partially solved. If you enter the username "bonkers", a button appears which lets you enter a 12-digit code. That code is checked on the server; if valid, cosmetics will be unlocked. The check can be bypassed, revealing all 32 cosmetics. ClipboarderTemp-14e99e4 The chosen cosmetic is only visible locally, but not for other players. All that is done with the existing protocol version. Only two packet-types were added, for validating the code.

Mat2095 commented 5 years ago

@sebakof I modified the sourcecode using the chrome-extensioin "Resource Override".

  1. There is an assignment want_open_cosmetics = !1 that I changed to want_open_cosmetics = true. Then the cosmetics will be shown if you click the cancel-button on the enter-code-page.

  2. There is a function recalculateActivatedCosmetics where I changed actco.push(0); to actco.push(1);, which will just enable all cosmetics.

Mat2095 commented 5 years ago

actco=Array(32).fill(1)