-
-
Notifications
You must be signed in to change notification settings - Fork 10
[BUG] Buddies can't be cheated in right. #1142
Comments
known bug, prodigy has done some patching, some things arent working |
It IS possible to cheat in ONE buddy with a specific setup, HOWEVER afterwards it won't work anymore. |
yaaa |
Yesterday I and my little brother found out clicking "close all popups" will bypass error 418 |
Well, yes. But that doesn't solve the fact that it doesn't save.
…On Tue, Oct 19, 2021 at 11:12 AM Undefineduser2 ***@***.***> wrote:
Yesterday I and my little brother found out clicking "close all popups"
will bypass error 418
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1142 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM623SKT65LNVDFWTW2AHE3UHWDGNANCNFSM5FUXCB3A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
you should create another issue for this |
HTTP Response 418? Isn't that the "I'm a teapot" troll error? |
yes i know |
This issue has not received any activity in a while and is considered stale. Has this issue been solved? If so, request for it to be closed. |
shut |
This is because of the toy code buddies |
HHHHHHHHHHHHHH |
Some things to note:
|
|
I think this issue should be closed.
|
again, fixed |
I got the 418 error for no reason and I did nothing wrong. |
They say it's an anticheat but I was not cheating in the first place |
hi |
9B3S same |
Description: Trying to cheat in buddies crashes the game with error 418.
Replication: Try to cheat in a buddy.
Images: (none)
Additional Errors: If you close the popup, trying to do anything else causes you to get inactivity kicked because of your session being invalidated.
The text was updated successfully, but these errors were encountered: