What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

HB Update - Offset XML may be a solution?

What do you think about Offset XML's?

  • Like it! If possible, i would provide Offets too in future

    Votes: 0 0.0%
  • Don't think its needed at all

    Votes: 0 0.0%
  • What the ..?

    Votes: 0 0.0%

  • Total voters
    0
  • Poll closed .
Status
Not open for further replies.

Nemezhiz

New Member
Joined
Dec 9, 2012
Messages
14
Reaction score
0
Hi everyone

as many others too, I was monitoring the forum for an update status today. As a developer, i truly understand that it ain't possible to provide updates immediatly all the time.
So I did not want to start a Thread to complain about how long it takes to serve an update .. seems like there enough other threads to do this :p

As far as i know - the main problem with the current - and most other - WoW Patche(s) is, that the Offsets are changing. And so HB is not able to fetch the process successfully.
As i read in the forum, i used the beta and this seems to work fine (except the questing bot which is the one i need but thats another topic), so it seems to be only about
updating the Offsets.

When this is the case, my question is: Why not putting the Offsets in XML File like PQR does, so create a folder "Offsets" where you place XML Files named by WoW Revision,
and there you place the Offsets in like for example

Code:
<?xml version="1.0" encoding="UTF-8"?> 
<Offsets> 
    <CurrentWoWVersion>16769</CurrentWoWVersion> 
    <WoWVersionOffset>0xC70E8F</WoWVersionOffset> 
    <PlayerName>0xEAEAA8</PlayerName> 
    <PlayerClass>0xEAEC25</PlayerClass> 
    <GetCurrentKeyBoardFocus>0xB9CEB4</GetCurrentKeyBoardFocus> 
    <GameState>0xD50F26</GameState> 
    <Lua_DoStringAddress>0x75c40</Lua_DoStringAddress> 
    <Lua_GetLocalizedTextAddress>0x4e4540</Lua_GetLocalizedTextAddress>
    <CVarBaseMgr>0xAD9BF0</CVarBaseMgr> 
    <CVarArraySize>0x400</CVarArraySize> 
    <ObjMgr>0xEAEA68</ObjMgr> 
    <CurMgr>0x462C</CurMgr> 
    <LocalGUID>0xD0</LocalGUID> 
    <FirstObject>0xCC</FirstObject> 
    <NextObject>0x3C</NextObject> 
    <Descriptors>0x8</Descriptors> 
    <Obj_TypeOffset>0x10</Obj_TypeOffset> 
    <Obj_X>0x800</Obj_X> 
    <Obj_TargetGUID>0x13</Obj_TargetGUID> 
    <ClickTerrain>0</ClickTerrain> 
</Offsets>

(Source/Copyright PQR Offsets_16769.xml)

The benefit of this solution would be - that the offsets are available for everyone, and so motivated and skilled devs out there (and i'm sure there are a lot of them) could change the offsets after a WoW
Patch. So this would result in
- faster delivery of HB patch so it works again after WoW Patch
- less work for Bossland / HB Core devs ..as others can change/upload Offsets too
- support for multiple WoW Versions / Offets (!)

Saying this in the knowledge of that the source of HB itself must be keeped inhouse .. but i think making the offets public shall not be a problem at all in this view.

Would look forward to see some discussion about this, or maybe even a answer / statement of one of the devs :)

Thanks for your time.
 
Last edited:
Honestly ? I think guys like Apoc can make a script that extract all the offsets from WoW in... what... 2 minutes (and btw anyone can copy/pasta the offsets from OC).

In my opinion, the Buddy Team are looking for a new way that Blizzard can trap HB users. It's not a problem related to the offsets at all.
We had a perfect example earlier in the day with their Tripwire alert.

Bossland work hard for our protection and I really like this way. Delivery offsets by third-party devs can be dangerous too (imagine giving voluntary an offset pointing on an address scanned by the Warden would be disastrous).
 
Honestly ? I think guys like Apoc can make a script that extract all the offsets from WoW in... what... 2 minutes (and btw anyone can copy/pasta the offsets from OC).
Thats what i'm talking about. But most people are not able to use those offsets then ( it ain't possible to change HB offsets atm at all or am I wrong?). So why not providing them seperatly in forum - for use of own risk of course. Thought i did not need to say that :D
Its not about implenenting those offsets into the main build - its about giving people the opportunity to change them on own risk ..
In my opinion, the Buddy Team are looking for a new way that Blizzard can trap HB users. It's not a problem related to the offsets at all.
We had a perfect example earlier in the day with their Tripwire alert.

Bossland work hard for our protection and I really like this way.
Which was a false alarm but yes - i'm with you. I also think its good they wait with the official stable update. No Question.
 
No, no and no.
If it was only the offsets then the update would be instantly after every patch.
HB core team allways makes sure that the bot is safe and secure before they release a update, if you don't want to be 100% safe then use the Beta, those offsets where updated what... 5 mins after US patch ?
 
No, no and no.
If it was only the offsets then the update would be instantly after every patch.
HB core team allways makes sure that the bot is safe and secure before they release a update, if you don't want to be 100% safe then use the Beta, those offsets where updated what... 5 mins after US patch ?

Well again - its not about providing modded Offsets in Patches :) Only about moving them into an XML ( if they are already, if a dev could tell me where i could change them? Could'nt find so i guess
their in the binary .. ) so people can change them.

As you say - you can use it on your own risk then. But changed offets in stable is not the same as using the beta, as this is always unstable ( what is the normal and meaning state of a beta ^^ ) and thats
why i'm asking for this possibility =)

No one is forced to used them at all then .. in stable version, the "official" offsets would be in XML ..same as in binary now - so no change for any user at all if you don't change on your own ;)

And note the fact, that multiple WoW Versions would be supported then .. which could be a very interesting aspect for a lot of people (keyword private servers)
 
The main problem is most users will try to use them without understanding what they represent (as you can see on the forum atm, there are lots of people that are impatient).
When the Tripwire won't be a false-positive and the half of the users will be banned, it will be too late.

And after, what about the reputation of HonorBuddy ? You can of course explain the offsets was unofficial, but the main feeling about the bot is that 50% of the botters were banned.
Also, I think your poll is a bit useless, because people will vote to have a fonctional bot as soon as possible, without understand what is involved. This discussion is more between you and the core dev. Not with the public.
In the current implementation of HB, it would be very hard to set your offsets.
 
Last edited:
The main problem is most users will try to use them without understanding what they represent (as you can see on the forum atm, there are lots of people that are impatient).
When the Tripwire won't be a false-positive and the half of the users will be banned, it will be too late.

And after, what about the reputation of HonorBuddy ? You can of course explain the offsets was unofficial, but the main feeling about the bot is that 50% of the botters were banned.
...

I totally understand what you mean - but the same problem is with profiles - which actually are open. (e.G jadeforest gb2 ban wave because of 1 profile)

And yeah - this thread may not be relevant for "standard users" - more for advanced users which e.G use bot for some tests or earning money, or making profiles, or whatever ..
 
Last edited:
Status
Not open for further replies.
Back
Top