search

jamestiotio / CITM

Battle Cats MITM Mailbox Hack
MIT License
20 stars 6 forks source link

Can't make Accept working #2

Closed qdev89 closed 4 years ago

qdev89 commented 4 years ago

hi @jamestiotio I followed your instruction but stuck on last step where we have to set Header Response to this image image

It returns to 200 OK as you can see but on the game client, it's still throwing this error message

I'm pretty sure header repsone is matched with GET that I made with Content-Length: 337(337 is exact number bytes I sent on GET) image

My item to claim: [ { "id":1, "accountId":"50b8832e0", "title":"Items", "body":"", "clientVersion":90100, "country":"en", "accepted":null, "created":1578117644, "items":[ { "itemId":5, "itemCategory":1, "amount":100, "title":"Bird Cat" } ] } ]

Please help me if I'm doing wrong. Thanks and best regards.

jamestiotio commented 4 years ago

Hi @quocfreelancer, you would need to do it quickly as well since there is an inherent timeout. If you take too much time, it will still return a 200 in Fiddler but Battle Cats will throw that error.

You can try copying the header from the HexView tab, if that helps.

Your item list looks fine.

Also, I suggest that you hide your accountId. Cheers!

SuperHKA commented 4 years ago

Hi @jamestiotio is this patched or not ?

jamestiotio commented 4 years ago

Hi @AndreReboulet, are you referring to the inherent timeout highlighted in this issue or to the overall hack?

If you are referring to the inherent timeout, there is no way to bypass or "patch" that timeout since it is built-in into the whole Battle Cats application code (and might also be in its server code as well).

If you are referring to the overall hack, it is still working as of today (I just checked). I have updated the appropriate JSON lines and added new cats to the Cat List to accommodate version 9.4.0 of Battle Cats in the commit beb63f578e25e488686bd42fe4ed35f5cdcca16d. Do observe the clientVersion pattern carefully and feel free to PR occasional updates to the Cat List since I would not be able to update this repo on a very frequent basis. Please also do open a new issue next time if you are highlighting a separate topic.

Otherwise, I will be closing this issue. Feel free to re-open if my previous reply was unsatisfactory.