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

wtf.. session invalid

Status
Not open for further replies.
A

a10xr

New Member
Joined
Aug 6, 2012
Messages
49
Reaction score
0
Has been happening to all 3 bots for the last 2 days. Bot only runs for 2 hours max and then crashes. What is going on?

Log 1:
[08:20:24.713 N] ========== Grid segmentation resetting!!! ============
[08:20:24.713 D] QuestOrderManager.OnBotStop(). Resetting caches.
[08:20:24.713 D] Resetting current behavior.
[08:20:24.714 D] Calling OnDone() on current behavior. UseTownPortalTag: IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.PrioritySelector,
[08:20:24.714 D] QuestOrderManager.OnBotStop(). Resetting caches.
[08:20:24.714 D] Resetting current behavior.
[08:20:24.714 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Banannaphone_Mine.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[08:20:24.714 D] QuestOrderManager.OnBotStop(). Resetting caches.
[08:20:24.714 D] Resetting current behavior.
[08:20:24.714 D] Calling OnDone() on current behavior. MoveToTag: X: 2021.518, Y: 1052.173, Z: 171.3882, PathPrecision: 1, Position: <2021.518, 1052.173, 171.3882>, UnsafeRandomDistance: 0, Name: 1, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.PrioritySelector,
[08:20:24.714 N] Session is invalid!
[08:20:24.720 N] Bot Thread Ended. Was this requested?


Log 2:
[07:23:56.478 D] Resetting current behavior.
[07:23:56.478 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_Rakki.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[07:23:56.478 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:23:56.478 D] Resetting current behavior.
[07:23:56.478 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_DamnedTower.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[07:23:56.478 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:23:56.479 D] Resetting current behavior.
[07:23:56.479 D] Calling OnDone() on current behavior. MoveToTag: X: 1214.136, Y: 1061.833, Z: -19.9, PathPrecision: 10, Position: <1214.136, 1061.833, -19.9>, UnsafeRandomDistance: 0, Name: null, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.PrioritySelector,
[07:23:56.479 N] Session is invalid!
[07:23:56.488 N] Bot Thread Ended. Was this requested?

Log 3:
[06:50:26.024 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_Stonefort.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[06:50:26.024 D] QuestOrderManager.OnBotStop(). Resetting caches.
[06:50:26.024 D] Resetting current behavior.
[06:50:26.024 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_Battlefields.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[06:50:26.024 D] QuestOrderManager.OnBotStop(). Resetting caches.
[06:50:26.024 D] Resetting current behavior.
[06:50:26.024 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_FieldsofSlaughter.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[06:50:26.024 D] QuestOrderManager.OnBotStop(). Resetting caches.
[06:50:26.024 D] Resetting current behavior.
[06:50:26.025 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_Rakki.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[06:50:26.025 D] QuestOrderManager.OnBotStop(). Resetting caches.
[06:50:26.025 D] Resetting current behavior.
[06:50:26.025 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_DamnedTower.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[06:50:26.025 D] QuestOrderManager.OnBotStop(). Resetting caches.
[06:50:26.025 D] Resetting current behavior.
[06:50:26.025 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_CursedTower.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[06:50:26.025 D] QuestOrderManager.OnBotStop(). Resetting caches.
[06:50:26.025 D] Resetting current behavior.
[06:50:26.025 D] Calling OnDone() on current behavior. ContinueTag: IsDone: False, ProfileName: Silhouettes_CoreOnly.xml, ProfileNameB: null, QuestId: 0, StepId: 0, QuestName: Quest Id: 0, IsDoneCache: False, Behavior: Zeta.TreeSharp.Action,
[06:50:26.025 D] QuestOrderManager.OnBotStop(). Resetting caches.
[06:50:26.025 D] Resetting current behavior.
[06:50:26.025 D] Calling OnDone() on current behavior. MoveToTag: X: 885.3837, Y: 717.8165, Z: 0.1000153, PathPrecision: 10, Position: <885.3837, 717.8165, 0.1000153>, UnsafeRandomDistance: 0, Name: null, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.PrioritySelector,
[06:50:26.025 N] Session is invalid!
[06:50:26.033 N] Bot Thread Ended. Was this requested?
 
I'm going to go out on a limb here - But I'm 90% sure its a system in place to protect the server due to the increased traffic (MoP). Also it is important to note there are many people who recently re-joined the community or became active - I think these persons have been given precedence. I mean; MoP is new - the profiles are newly updated - I doubt the pathing is perfected in the least bit - They really need a lot of bandwidth. As has been hinted; the problem should subside as soon as traffic returns to normal - or when we have less people trying to use buddybots at the same time. In 2 weeks time - enough people will have either been banned (Makes good business sense - don't feel offended) or have had their botting habits return to normal values. The influx of traffic as we have been told will eventually subside and that is when you can go about your normal business.

It's rather greedy to hog the bandwidth of the single server what with MoP being introduced as the latest wow expansion just the other day. We Have had plenty of good botting sessions without much interruption - let some other people have a chance. Adding a new server is not a good business choice as mentioned - the trend will soon change and that extra hardware will be worthless. Just take a week vacation from botting.
 
Cyonsiaros said:
I'm going to go out on a limb here - But I'm 90% sure its a system in place to protect the server due to the increased traffic (MoP). Also it is important to note there are many people who recently re-joined the community or became active - I think these persons have been given precedence. I mean; MoP is new - the profiles are newly updated - I doubt the pathing is perfected in the least bit - They really need a lot of bandwidth. As has been hinted; the problem should subside as soon as traffic returns to normal - or when we have less people trying to use buddybots at the same time. In 2 weeks time - enough people will have either been banned (Makes good business sense - don't feel offended) or have had their botting habits return to normal values. The influx of traffic as we have been told will eventually subside and that is when you can go about your normal business.

It's rather greedy to hog the bandwidth of the single server what with MoP being introduced as the latest wow expansion just the other day. We Have had plenty of good botting sessions without much interruption - let some other people have a chance. Adding a new server is not a good business choice as mentioned - the trend will soon change and that extra hardware will be worthless. Just take a week vacation from botting.
Click to expand...
This is a joke right?
 
Let's pretend it's half true and guess which half is true that is funner! you may end the thread sorry!
 
Are there any .bat files that can work around this problem when it happens? I've been poking around the plugin section and have seen some .bat files for restarting DB and Diablo, but I haven't seen one specifically for this problem.
 
Status
Not open for further replies.
Back
Top