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

release posts

xxxstar123 said:
Sorry to say that I don't agree with you I was and still give my full support for Buddy team they are the best, but the game we play blizz keep changing things so they could stop this team and their bot but still buddy team always show quilt y on this bot they have a big challenge against blizz then their team, we should show our support for the buddy team and stop throwing talks there and here ...
Click to expand...


You haven't ben around long enough to form an opinion, HB was great, it isn't now. Blizz have nothing to do with dying and not rezzing, blizz have nothing to do with walking into walls constantly, blizz have nothing to do with releases released and not working on half the users machines, blizz has nothing to do with releases released and core files missing, blizz have nothing to do with with all the bugs in HB, its the dev team who are sloppy in their methods and release poorly coded product. it never used to be that way, any bugs were always squashed quickly. We currently see old bugs of years gone by introduced, that's not acceptable. I don't need to be a fan boy and lick any devs ass, the product is nowhere near as well written as it used to be, it needs to get back to where it was, the team working on it now is not as good or thorough as the team of the past, Bossland needs to man up ad take back his baby and get the ship back on track.

G
 
I agree with with you theatris, next thing we are going to hear is this is the wrong section, and this thread is locked. Or better yet I can get told to use the search function to fine better devs. haha Please come back and fully take over Bossland!
 
Getting spammed with errors.
Code: 
System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed
Restart fixed but here is a log.
 

Attachments

theatristformallyknownasG said:
You haven't ben around long enough to form an opinion, HB was great, it isn't now. Blizz have nothing to do with dying and not rezzing, blizz have nothing to do with walking into walls constantly, blizz have nothing to do with releases released and not working on half the users machines, blizz has nothing to do with releases released and core files missing, blizz have nothing to do with with all the bugs in HB, its the dev team who are sloppy in their methods and release poorly coded product. it never used to be that way, any bugs were always squashed quickly. We currently see old bugs of years gone by introduced, that's not acceptable. I don't need to be a fan boy and lick any devs ass, the product is nowhere near as well written as it used to be, it needs to get back to where it was, the team working on it now is not as good or thorough as the team of the past, Bossland needs to man up ad take back his baby and get the ship back on track.

G
Click to expand...

Uh oh, someone said what we are all thinking... incoming thread lock possibly removed post!
 
Post by G, well just because it was well said


quote_icon.png
Originally Posted by theatristformallyknownasG
It's been bordering on useless for the last 10 releases, nothing gets fixed, more features get added we don't need, but we still do not have a stable bot we can run. The current team working on it clearly have no direction and clearly do not check their own work, they need to be replaced with a team that knows what it is doing. If the current team was under my direction on a project they would be sacked, they simply aren't good enough. The board administrators on here will say post a log or check your settings, HB is clearly bad when long term users who can usually make most things work are posting on here and complaining about it.

Since D3 will have no AH soon so botting it is now useless some of those team members might come across and rescue HB, lets hope so, it is truly a pathetic shell of what it used to be.

G
 
Spot on G - this bot is just getting worse and worse. I guess that's what happens when there is no real competition in the market.
 
Odd, even with a fresh install It would not load correctly, only Dungeonbuddy, and BGbuddy were available as bot bases, when I reverted back to 8.0, no issues.
 
Guys, is there any statement on Dungeonbuddy? When can we expect DB to be fixed? Since they say it's not a DB but a HB Core issue in the DB Thread I'm posting this here...

DB is really a bad, dangerous mess at the moment. With either permanently running to the entrance, or standing around doing nothing it's predestined to get reported/banned, it's really dangerous to use this bot at the moment. There are so many people complaining about his.... can you please give us an answer when a fix can be expected?
 
Sjoo said:
DB is really a bad, dangerous mess at the moment. With either permanently running to the entrance, or standing around doing nothing it's predestined to get reported/banned, it's really dangerous to use this bot at the moment.
Click to expand...
^ this.

I would NOT suggest using DB until it is fixed. You're better off using LazyRaider or Tyrael since you'd have to babysit DB if you only turned it on for boss encounters.
 
Do DE users get a discount for their 30% DE Version?
 
Installer NOT working?

23A4:14FC][2013-10-01T12:27:28]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\Roque\Downloads\Honorbuddy Installer v2.5.8113.696 (2).exe, cmdline: ''
[23A4:14FC][2013-10-01T12:27:28]i000: Initializing string variable 'InstallFolder' to value '[PersonalFolder]Honorbuddy'
[23A4:14FC][2013-10-01T12:27:28]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Roque\AppData\Local\Temp\Honorbuddy_20131001122728.log'
[23A4:14FC][2013-10-01T12:27:28]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Roque\Downloads\Honorbuddy Installer v2.5.8113.696 (2).exe'
[23A4:14FC][2013-10-01T12:27:28]i000: Setting string variable 'WixBundleName' to value 'Honorbuddy'
[23A4:14FC][2013-10-01T12:27:28]i100: Detect begin, 3 packages
[23A4:14FC][2013-10-01T12:27:28]i000: Setting version variable 'MFC110_Version_x86' to value '11.0.60610.1'
[23A4:14FC][2013-10-01T12:27:28]i000: Setting string variable 'NETFRAMEWORK40' to value '1'
[23A4:14FC][2013-10-01T12:27:28]i102: Detected related bundle: {b2de96db-47dc-4c1f-aa60-04af33ebce2d}, type: Upgrade, scope: PerUser, version: 2.5.7857.658, operation: MajorUpgrade
[23A4:14FC][2013-10-01T12:27:28]i052: Condition 'NETFRAMEWORK40' evaluates to true.
[23A4:14FC][2013-10-01T12:27:28]i103: Detected related package: {6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}, scope: PerUser, version: 2.5.7857.658, language: 1033 operation: MinorUpdate
[23A4:14FC][2013-10-01T12:27:28]i101: Detected package: NetFx40Web, state: Present, cached: Complete
[23A4:14FC][2013-10-01T12:27:28]i101: Detected package: vcredist_x86, state: Absent, cached: None
[23A4:14FC][2013-10-01T12:27:28]i101: Detected package: Honorbuddy, state: Present, cached: None
[23A4:14FC][2013-10-01T12:27:28]i199: Detect complete, result: 0x0
[23A4:1B20][2013-10-01T12:28:05]i000: Setting string variable 'InstallFolder' to value 'C:\Users\Roque\Desktop\HB 696'
[23A4:14FC][2013-10-01T12:28:05]i200: Plan begin, 3 packages, action: Install
[23A4:14FC][2013-10-01T12:28:05]w321: Skipping dependency registration on package with no dependency providers: NetFx40Web
[23A4:14FC][2013-10-01T12:28:05]i052: Condition '(NOT MFC110_Version_x86 >= v11.0.60610.1) OR NOT MFC110_Version_x86' evaluates to false.
[23A4:14FC][2013-10-01T12:28:05]w321: Skipping dependency registration on package with no dependency providers: vcredist_x86
[23A4:14FC][2013-10-01T12:28:05]i000: Setting string variable 'WixBundleLog_Honorbuddy' to value 'C:\Users\Roque\AppData\Local\Temp\Honorbuddy_20131001122728_0_Honorbuddy.log'
[23A4:14FC][2013-10-01T12:28:05]i201: Planned package: NetFx40Web, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[23A4:14FC][2013-10-01T12:28:05]i201: Planned package: vcredist_x86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[23A4:14FC][2013-10-01T12:28:05]i201: Planned package: Honorbuddy, state: Present, default requested: Present, ba requested: Present, execute: MinorUpgrade, rollback: None, cache: Yes, uncache: No, dependency: Register
[23A4:14FC][2013-10-01T12:28:05]i207: Planned related bundle: {b2de96db-47dc-4c1f-aa60-04af33ebce2d}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None
[23A4:14FC][2013-10-01T12:28:05]i299: Plan complete, result: 0x0
[23A4:14FC][2013-10-01T12:28:05]i300: Apply begin
[23A4:14FC][2013-10-01T12:28:06]i000: Caching bundle from: 'C:\Users\Roque\AppData\Local\Temp\{416df253-8281-4291-8e7d-e67931729383}\.be\Honorbuddy Installer v2.5.8113.696.exe' to: 'C:\Users\Roque\AppData\Local\Package Cache\{416df253-8281-4291-8e7d-e67931729383}\Honorbuddy Installer v2.5.8113.696.exe'
[23A4:14FC][2013-10-01T12:28:06]i320: Registering bundle dependency provider: {416df253-8281-4291-8e7d-e67931729383}, version: 2.5.8113.696
[23A4:22D4][2013-10-01T12:28:06]i305: Verified acquired payload: Honorbuddy at path: C:\Users\Roque\AppData\Local\Package Cache\.unverified\Honorbuddy, moving to: C:\Users\Roque\AppData\Local\Package Cache\{6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}v2.5.8113.696\Honorbuddy.msi.
[23A4:14FC][2013-10-01T12:28:06]i323: Registering package dependency provider: {6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}, version: 2.5.8113.696, package: Honorbuddy
[23A4:14FC][2013-10-01T12:28:06]i301: Applying execute package: Honorbuddy, action: MinorUpgrade, path: C:\Users\Roque\AppData\Local\Package Cache\{6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}v2.5.8113.696\Honorbuddy.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" INSTALLLOCATION="C:\Users\Roque\Desktop\HB 696"'
[23A4:14FC][2013-10-01T12:28:07]e000: Error 0x80070659: Failed to perform minor upgrade of MSI package.
[23A4:14FC][2013-10-01T12:28:07]e000: Error 0x80070659: Failed to configure per-user MSI package.
[23A4:14FC][2013-10-01T12:28:07]i319: Applied execute package: Honorbuddy, result: 0x80070659, restart: None
[23A4:14FC][2013-10-01T12:28:07]e000: Error 0x80070659: Failed to execute MSI package.
[23A4:14FC][2013-10-01T12:28:07]i329: Removed package dependency provider: {6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}, package: Honorbuddy
[23A4:14FC][2013-10-01T12:28:07]i351: Removing cached package: Honorbuddy, from path: C:\Users\Roque\AppData\Local\Package Cache\{6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}v2.5.8113.696\
[23A4:14FC][2013-10-01T12:28:07]i330: Removed bundle dependency provider: {416df253-8281-4291-8e7d-e67931729383}
[23A4:14FC][2013-10-01T12:28:07]i352: Removing cached bundle: {416df253-8281-4291-8e7d-e67931729383}, from path: C:\Users\Roque\AppData\Local\Package Cache\{416df253-8281-4291-8e7d-e67931729383}\
[23A4:14FC][2013-10-01T12:28:07]i399: Apply complete, result: 0x80070659, restart: None, ba requested restart: No
 
Hello everybody,

I'm having a problem on logging to HB. Getting an error. Is there a problem about it?

Thanks in advance.

Edit: Nevermind, it worked out somehow :)
 
New DE version - same stucking problems underwater mount/dismount loop.

Greetings
 
xtreme3881 said:
Post by G, well just because it was well said


quote_icon.png
Originally Posted by theatristformallyknownasG
It's been bordering on useless for the last 10 releases, nothing gets fixed, more features get added we don't need, but we still do not have a stable bot we can run. The current team working on it clearly have no direction and clearly do not check their own work, they need to be replaced with a team that knows what it is doing. If the current team was under my direction on a project they would be sacked, they simply aren't good enough. The board administrators on here will say post a log or check your settings, HB is clearly bad when long term users who can usually make most things work are posting on here and complaining about it.

Since D3 will have no AH soon so botting it is now useless some of those team members might come across and rescue HB, lets hope so, it is truly a pathetic shell of what it used to be.

G
Click to expand...


i've had no issues with it.
 
I do agree that this is a great bot but it's few releases so far have degraded the bots reliability, as I am now forced to make my own stuck detector to get around objects and other game models.
 
You must log in or register to reply here.
Back
Top