[DiscordArchive] You sure they're using a 3.3.5a 12340 build client?
[DiscordArchive] You sure they're using a 3.3.5a 12340 build client?
Original source
You sure they're using a 3.3.5a 12340 build client?
rektbyfaith
06-30-2022, 10:20 PM #1Archived author: HelloKitty • Posted: 2022-06-30T22:20:03.615000+00:00
Original source
You sure they're using a 3.3.5a 12340 build client?
Original source
Players began making tickets about the problem
rektbyfaith
06-30-2022, 10:20 PM #2Archived author: Deleted User • Posted: 2022-06-30T22:20:06.318000+00:00
Original source
Players began making tickets about the problem
Original source
Yes I'm sure
rektbyfaith
06-30-2022, 10:20 PM #3Archived author: Deleted User • Posted: 2022-06-30T22:20:10.311000+00:00
Original source
Yes I'm sure
Original source
I made them send me client diagnostics
rektbyfaith
06-30-2022, 10:20 PM #4Archived author: Deleted User • Posted: 2022-06-30T22:20:18.917000+00:00
Original source
I made them send me client diagnostics
Original source
Can you personally reproduce the issue with your own 3.3.5a 12340 client? Because this can only happen if Warden detects memory at that address is modified. If they can actually auth to the worldserver (required before Warden init) then their build number sent in session auth packet is 12340 soooo they likely modified their client imo.
rektbyfaith
06-30-2022, 10:21 PM #5Archived author: HelloKitty • Posted: 2022-06-30T22:21:36.862000+00:00
Original source
Can you personally reproduce the issue with your own 3.3.5a 12340 client? Because this can only happen if Warden detects memory at that address is modified. If they can actually auth to the worldserver (required before Warden init) then their build number sent in session auth packet is 12340 soooo they likely modified their client imo.
Original source
Yes I produced the same problem with my own client.
rektbyfaith
06-30-2022, 10:23 PM #6Archived author: Deleted User • Posted: 2022-06-30T22:23:10.305000+00:00
Original source
Yes I produced the same problem with my own client.
Original source
I even reinstalled the client
rektbyfaith
06-30-2022, 10:23 PM #7Archived author: Deleted User • Posted: 2022-06-30T22:23:19.788000+00:00
Original source
I even reinstalled the client
Original source
I appreciate that it will kick people with modified clients, but I strongly feel that this is something not quite right, we never had the issue before and so far 37 players have had this problem.
rektbyfaith
06-30-2022, 10:23 PM #8Archived author: Deleted User • Posted: 2022-06-30T22:23:52.987000+00:00
Original source
I appreciate that it will kick people with modified clients, but I strongly feel that this is something not quite right, we never had the issue before and so far 37 players have had this problem.
Original source
I started up a test server and reproduced it there too
rektbyfaith
06-30-2022, 10:24 PM #9Archived author: Deleted User • Posted: 2022-06-30T22:24:02.020000+00:00
Original source
I started up a test server and reproduced it there too
Original source
If you're sure your client is modified then maybe you accidentally changed Warden behavior. I'd recommend git checkout each recent commit until you find the last working version of your worldserver. You can also DM me your Wow.exe and I'll inspect it real quick to make sure that particular address isn't changed.
rektbyfaith
06-30-2022, 10:26 PM #10Archived author: HelloKitty • Posted: 2022-06-30T22:26:34.120000+00:00
Original source
If you're sure your client is modified then maybe you accidentally changed Warden behavior. I'd recommend git checkout each recent commit until you find the last working version of your worldserver. You can also DM me your Wow.exe and I'll inspect it real quick to make sure that particular address isn't changed.
1 Guest(s)
1 Guest(s)