[DiscordArchive] btw, are opcodes for classic clients the same as their original counterpar at the latest build of th
[DiscordArchive] btw, are opcodes for classic clients the same as their original counterpar at the latest build of th
Original source
btw, are opcodes for classic clients the same as their original counterpar at the latest build of their expansionn?
rektbyfaith
06-29-2025, 05:42 PM #1Archived author: Telegrill • Posted: 2025-06-29T17:42:49.150000+00:00
Original source
btw, are opcodes for classic clients the same as their original counterpar at the latest build of their expansionn?
Original source
sadly no
rektbyfaith
06-29-2025, 05:43 PM #2Archived author: Northstrider • Posted: 2025-06-29T17:43:03.849000+00:00
Original source
sadly no
Original source
cause i remember MoP being a complete disaster when it came to build updates, opcodes were changing from build to build
rektbyfaith
06-29-2025, 05:43 PM #3Archived author: Telegrill • Posted: 2025-06-29T17:43:49.815000+00:00
Original source
cause i remember MoP being a complete disaster when it came to build updates, opcodes were changing from build to build
Original source
Sure, look the first message i used WPP TC last commit (just added the log) and used Ymir to confirm that also a TC issue
rektbyfaith
06-29-2025, 05:43 PM #4Archived author: Hayden • Posted: 2025-06-29T17:43:52.574000+00:00
Original source
Sure, look the first message i used WPP TC last commit (just added the log) and used Ymir to confirm that also a TC issue
Original source
(at least for PTR builds)
rektbyfaith
06-29-2025, 05:44 PM #5Archived author: Telegrill • Posted: 2025-06-29T17:44:26.882000+00:00
Original source
(at least for PTR builds)
Original source
pretty much usual thing, thats why we only touch builds where they aren't changing much anymore
rektbyfaith
06-29-2025, 06:02 PM #6Archived author: ModoX • Posted: 2025-06-29T18:02:22.140000+00:00
Original source
pretty much usual thing, thats why we only touch builds where they aren't changing much anymore
Original source
i have no idea who is wrong, wpp? tc? both?
and i dont see where it would be wrong looking at client parser
feel free to point out the mistake and ill fix it
rektbyfaith
06-29-2025, 07:10 PM #7Archived author: Tea • Posted: 2025-06-29T19:10:25.363000+00:00
Original source
i have no idea who is wrong, wpp? tc? both?
and i dont see where it would be wrong looking at client parser
feel free to point out the mistake and ill fix it
Original source
i can give an example for 10.2.7 if you want, that can help you? i know that mean launching old idb <
adge:874077934862884914> without that flushbit that did exactly what happened with WPP (and core side ofc client crash in some case of update)
shelby said he literally saw the flushbit isn't a call it's inline (i have no idea what i'm saying)
rektbyfaith
06-29-2025, 10:04 PM #8Archived author: Hayden • Posted: 2025-06-29T22:04:41.042000+00:00
Original source
i can give an example for 10.2.7 if you want, that can help you? i know that mean launching old idb <adge:874077934862884914>
without that flushbit that did exactly what happened with WPP (and core side ofc client crash in some case of update)
shelby said he literally saw the flushbit isn't a call it's inline (i have no idea what i'm saying)
Original source
there is no "flush" on reading in client
rektbyfaith
06-29-2025, 10:05 PM #9Archived author: Tea • Posted: 2025-06-29T22:05:45.368000+00:00
Original source
there is no "flush" on reading in client
Original source
its all inline
rektbyfaith
06-29-2025, 10:05 PM #10Archived author: Tea • Posted: 2025-06-29T22:05:48.399000+00:00
Original source
its all inline
1 Guest(s)
1 Guest(s)