[PAID] [Fly][N-QB] Aeonaxx Farm[Maffyx]

Ended up getting the mount, had to ask blizz to recover it for me and they did

 

Congrats! If you don't mind me asking, what was the original problem, may be able to fix it with a log? Thanks!

 

When camping on one spot my bot logs out after 30 min, anyone know what the problem might be? My 'Logout for Inactivity' is turned off.

 

I might be able to figure it out if you post a log. Something may have been fixed/changed in the HB code since this release.

 

A log from a day I tried to camp in one spot.

 

First thing I see in the log is an error which seems to be coming from HBRelog, so you may want to look into this.

[HIDE][04:23:26.556 N] System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/HBRelog/Server that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/HBRelog/Server' could not be found on your local machine. --- End of inner exception stack trace ---


Server stack trace:
at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri, IPipeTransportFactorySettings transportFactorySettings)
at System.ServiceModel.Channels.NamedPipeConnectionPoolRegistry.NamedPipeConnectionPool.GetPoolKey(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.CommunicationPool`2.TakeConnection(EndpointAddress address, Uri via, TimeSpan timeout, TKey& key)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)


Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at HighVoltz.HBRelog.Remoting.IRemotingApi.Init(Int32 hbProcID)
at HighVoltz.HBRelogHelper.ServiceProxy.Init(Int32 hbProcID) in D:\Honorbuddy\Plugins\HBRelogHelper\HBRelogHelper.cs:line 127
at HighVoltz.HBRelogHelper.HBRelogHelper..ctor() in D:\Honorbuddy\Plugins\HBRelogHelper\HBRelogHelper.cs:line 331[/HIDE]


You also have this enabled: LogMeOut!

Which is what logged you out

[HIDE][15:09:34.095 N] [LogMeOut!]: Starting logout process...[15:09:34.095 N] [LogMeOut!]: Reason : Logout time reached
[15:09:34.099 N] [LogMeOut!]: Log out in 20 secondes...
[15:09:34.099 N] [LogMeOut!]: Goodbye
[15:09:34.100 N] [LogMeOut!]: Remaining time before log out : 00h-45m-56s[/HIDE]

Disable or modify that and it should be fine!

 

I buy now.. ill be back later with resulted of camping...

 

Good luck!

 

i got the mount because i was there.
The bot was flying high, it didnt loot it and i did it manually.
The corpse was land on good place, very easy to loot.

 

That's really interesting, could you post a full unedited log? There's a few key things I need to look at to figure out what's going on. Glad you were there though.

 

Full log here.

 

Hey sorry for the late reply, holiday tied me up. So from what I gather is that it seems like the bot just glitched out and couldn't figure out where your character was.

Code:

[12:03:37.222 D] Changed POI to: Type: Loot, Name: Aeonaxx, NavType: Run[12:03:37.288 D] Clearing POI - Reason Already looted
[12:03:37.355 D] Changed POI to: Type: Loot, Name: Aeonaxx, NavType: Run
[12:03:37.488 N] Can't generate a path to the lootable. Blacklisting it for 15 minutes.
[12:03:37.488 V] Blacklisting 5C08 for 00:15:00 [Type: Loot, Node, Skin] - Reason: Couldn't generate a path to the target.
[12:03:37.488 D] Clearing POI - Reason Can't generate a path to lootable
[12:03:37.930 N] Mounting: Ironbound Wraithcharger
[12:03:42.206 N] (Singular) [WoWRedError] Can't do that while moving
[12:03:42.206 N] (Singular) [WoWRedError] Can't do that while moving
[12:03:44.342 N] (Singular) [WoWRedError] Can't do that while moving
[12:03:44.418 V] Loading Deephome_32_29
[12:03:44.502 V] Loading Deephome_29_30
[12:03:44.560 V] Loading Deephome_30_29
[12:03:44.576 D] Could not generate path from {838.6249, 850.1712, -22.59807} to {796.8964, 831.7652, 49.97459} on map Deephome (time used: 0 milliseconds) @ FindStartPoly

Seems like it may be a mesh issue? Everything else seemed to be working as intended, probably a fluke. But glad you managed to get it!

 

To those who have used this profile: Camp 1 spot or patrol? Which is more effective?

 

In my initial testing rounds, patrol was the most successful with 3 kills/ loots.

 

In what kind of time frame?

 

I tested it for 1-2 days. I also used a realm hopping addon and manually jumped between servers.

 

Surprised youre still selling this, I caught Aeonaxx twice with patrol but he doesn't loot him. Never got the mount. Would have been better farming him myself.
You should fix this common problem people are having. How do I refund this?

 

Sorry you're having issues. I need logs to be able to help you in order to fix things, otherwise to me it works fine. I'll do some testing on it to see what's happening. As for refunds you have to do that through the buddy store.

 

[TABLE]
[TR]
[TD]1.8.9[/TD]
[TD]Release[/TD]
[TD]Updated for Legion/HB3

• Upped max level to 111
• Removed loot hook until further testing
• Re-added Loot-A-Rang support
• Re-enabled anti-afk

Potential legion bonus updates: It seems like Aeonaxx is group lootable now.

Known Issues:

• Flightor still needs to be optimized, you may get a few errors but those should be ignored.

[/TD]
[TD]9/12/2016 11:23:34 PM[/TD]
[TD="bgcolor: #CCFFFF"]Waiting for Code Approval[/TD]
[/TR]
[/TABLE]

 

[TABLE]
[TR]
[TD]1.8.9[/TD]
[TD]Release[/TD]
[TD]Updated for Legion/HB3

• Upped max level to 111
• Removed loot hook until further testing
• Re-added Loot-A-Rang support
• Re-enabled anti-afk

Potential legion bonus updates: It seems like Aeonaxx is group lootable now.

Known Issues:

• Flightor still needs to be optimized, you may get a few errors but those should be ignored.

[/TD]
[TD]9/12/2016 11:23:34 PM[/TD]
[TD="bgcolor: green"]Approved[/TD]
[TD]9/14/2016 12:06:18 AM[/TD]
[/TR]
[/TABLE]