Hey I need to Patch / Hex out the old Verbyte of a program to the new verbyte, so i want to change the current verbyte from 201 aka 0xC9 to 203 aka 0xCB. Now im in hex editor, serched 16 unsigned byte and found one but that once changed to 203 doesnt work. i then found 241. 0xC9 - 201's under the unsigned 8 byte i beelive it was is there anyway to " cancle out some possibilitys to make it ezer to find which one is the main verbyte? " thanks.
nerf rogues.
Why not just recompile with the new value? It's generally unwise to go trying binary patches against old versions if you don't know what you're doing.
im patching a program that isnt mine to make it work so iw ont beable to "complie again"
Trial and error is probably the best way to do that, without disassembling. Note version code is typically stored in DWORD -- so searching as that, instead of a single byte would probably be faster and return less redundant results.
Enjoy.
Quote from: Spht on February 16, 2005, 10:18 PM
nerf rogues.
rofl I love the random reference to WoW. It really has eaten vL. :P
Quote from: KoRe on February 16, 2005, 10:26 PMim patching a program that isnt mine to make it work so iw ont beable to "complie again"
I expected that, but was giving you the benefit of the doubt. As I said originally, you're much better off waiting for it to be fixed if you don't know what you're doing. That you asked here implies you don't know what you're doing.
Quote from: Kp on February 17, 2005, 04:24 PM
Quote from: KoRe on February 16, 2005, 10:26 PMim patching a program that isnt mine to make it work so iw ont beable to "complie again"
I expected that, but was giving you the benefit of the doubt. As I said originally, you're much better off waiting for it to be fixed if you don't know what you're doing. That you asked here implies you don't know what you're doing.
There are some bot's that aren't supported any longer, what do you suggest to do about those? I guess you COULD write some extensive program that intercepts data & then would send the correct verbyte instead of the old one. Something along the lines of BGate or w/e?
Quote from: CrAz3D on February 17, 2005, 05:42 PM
Quote from: Kp on February 17, 2005, 04:24 PM
Quote from: KoRe on February 16, 2005, 10:26 PMim patching a program that isnt mine to make it work so iw ont beable to "complie again"
I expected that, but was giving you the benefit of the doubt. As I said originally, you're much better off waiting for it to be fixed if you don't know what you're doing. That you asked here implies you don't know what you're doing.
There are some bot's that aren't supported any longer, what do you suggest to do about those? I guess you COULD write some extensive program that intercepts data & then would send the correct verbyte instead of the old one. Something along the lines of BGate or w/e?
If it's only a version byte that needs to be updated, it could be modified realitively easily and it would get rid of the need for a client such as BGate.
Your best bet is to disassemble the program and find out the offset of the value you need to modify. This saves you the trouble of, as Spht said, trial and error.
If you want, you could send me (
[email protected]) the program and I could tell you what you need to modify.
Quote from: CrAz3D on February 17, 2005, 05:42 PMThere are some bot's that aren't supported any longer, what do you suggest to do about those?
Delete them. If they're unsupported, it's probably for good reason. :)
ChewBot isn't supported, but it's still a good bot :)
Quote from: rabbit on February 18, 2005, 10:21 AM
ChewBot isn't supported, but it's still a good bot :)
That's pretty much what I was reffering to.
I was pointing out a specific example to LoRd of a bot that isn't supported any longer not because of some "evildoing scheme" that'd been found out, but merely for time management issues.
Quote from: rabbit on February 19, 2005, 01:48 PM
I was pointing out a specific example to LoRd of a bot that isn't supported any longer not because of some "evildoing scheme" that'd been found out, but merely for time management issues.
Kp*
See if this bot has already been "hexed" by someone else to change the version byte. If it has, compare the previously-hexed version to the original (or an older hexed version) to see what was changed. The point(s) where the files differ should be where the version byte is stored.
Quote from: LoRd[nK] on February 19, 2005, 01:53 PM
Quote from: rabbit on February 19, 2005, 01:48 PM
I was pointing out a specific example to LoRd of a bot that isn't supported any longer not because of some "evildoing scheme" that'd been found out, but merely for time management issues.
Kp*
LoRd, Kp, you're both over my head -.-
Chewbot is great, and it is still fine. The creator may not update it, but hes got a hell of a fan base. Besides, it works with War2, who nees SC?
Quote from: TaGBaN on February 22, 2005, 06:09 AM
Chewbot is great, and it is still fine. The creator may not update it, but hes got a hell of a fan base. Besides, it works with War2, who nees SC?
People who don't have War2 keys.
ChewBot has already been hexed before to work on SC 1.09. I'm sure someone might do it again?
No one is going to keep doing it.
Why not just create a small utility that would allow a user to change it themselves, manually, or even better, use BNLS to obtain the new version byte and automatically patch it?
Edit:
IIRC, you don't need to modify Chewbacca Bot to update the version bytes. You'd just need to modify the configuration file.
I tried that, doesn't work *at all*.