[DiscordArchive] <@456226577798135808>do you know how to patch the diff in a core?
[DiscordArchive] <@456226577798135808>do you know how to patch the diff in a core?
Original source
<@456226577798135808>do you know how to patch the diff in a core?
rektbyfaith
06-30-2022, 09:36 PM #1Archived author: Krutok • Posted: 2022-06-30T21:36:35.762000+00:00
Original source
<@456226577798135808>do you know how to patch the diff in a core?
Original source
No...
rektbyfaith
06-30-2022, 09:44 PM #2Archived author: Deleted User • Posted: 2022-06-30T21:44:46.897000+00:00
Original source
No...
Original source
To add to what I said earlier, I just enabled warden logging and found this:
```[Player: Hallowed GUID Full: 0x0000000000000001 Type: Player Low: 1, Account: 2] failed Warden check 342 (MEM_CHECK). Action: Kick```
rektbyfaith
06-30-2022, 09:45 PM #3Archived author: Deleted User • Posted: 2022-06-30T21:45:17.092000+00:00
Original source
To add to what I said earlier, I just enabled warden logging and found this:
```[Player: Hallowed GUID Full: 0x0000000000000001 Type: Player Low: 1, Account: 2] failed Warden check 342 (MEM_CHECK). Action: Kick```
Original source
Assuming our Warden checks are the same then it seems you got kicked because your client failed a MEM_CHECK at offset 0x465685. Warden check specifies the instructions/operands: 0x89 0x86 0x10 0x0F 0x00 must be present at that address
![[Image: unknown.png?ex=690c757e&is=690b23fe&hm=b...31c33a4ca&]](https://cdn.discordapp.com/attachments/376457042392514560/992191929586569326/unknown.png?ex=690c757e&is=690b23fe&hm=bcd862c9f45b7527b14903c95c6a81d4452e509a2d2b7abe155ceaf31c33a4ca&)
rektbyfaith
06-30-2022, 10:16 PM #4Archived author: HelloKitty • Posted: 2022-06-30T22:16:30.217000+00:00
Original source
Assuming our Warden checks are the same then it seems you got kicked because your client failed a MEM_CHECK at offset 0x465685. Warden check specifies the instructions/operands: 0x89 0x86 0x10 0x0F 0x00 must be present at that address
Original source
Your 3.3.5 client is probably modified or you're injecting something into it that's patching at that address at runtime.
rektbyfaith
06-30-2022, 10:17 PM #5Archived author: HelloKitty • Posted: 2022-06-30T22:17:07.539000+00:00
Original source
Your 3.3.5 client is probably modified or you're injecting something into it that's patching at that address at runtime.
Original source
![[Image: unknown.png?ex=690c75bd&is=690b243d&hm=d...661eaa0ee&]](https://cdn.discordapp.com/attachments/376457042392514560/992192195044061184/unknown.png?ex=690c75bd&is=690b243d&hm=d4ffb9c7f806b10c3e94477c78ba161a4566b6a92db502fb5ac54a2661eaa0ee&)
rektbyfaith
06-30-2022, 10:17 PM #6Archived author: HelloKitty • Posted: 2022-06-30T22:17:33.381000+00:00
Original source
Original source
Not modified at all. I installed this client from the retail CDs
rektbyfaith
06-30-2022, 10:19 PM #7Archived author: Deleted User • Posted: 2022-06-30T22:19:24.076000+00:00
Original source
Not modified at all. I installed this client from the retail CDs
Original source
I'm not the only one experiencing this issue
rektbyfaith
06-30-2022, 10:19 PM #8Archived author: Deleted User • Posted: 2022-06-30T22:19:30.984000+00:00
Original source
I'm not the only one experiencing this issue
1 Guest(s)
1 Guest(s)