• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Problem when after trying to recover from death

    Discussion in 'Rebornbuddy Support' started by mistahmikey, Nov 4, 2015.

    1. mistahmikey

      mistahmikey New Member

      Joined:
      Jun 29, 2015
      Messages:
      161
      Likes Received:
      3
      Trophy Points:
      0
      Problem when trying to recover from death

      I am using a farming orderbot script that occasionally runs afoul of Dalvag's Final Flame so I wind up getting killed. The toon revives to its home point, then transports back to the zone where the death occurred. At this point, when it tries to resume the script by traveling back to the grind area, I am consistently getting this:

      Code:
      [11:37:18.595 V] [Poi.Clear] Reason: Invalid Combat Poi
      [11:37:18.627 D] [POI Set] Type: Death, ObjectId: 105401B4, Location: <-198.8122, 82.4078, -290.8023>
      [11:37:27.989 N] [FlightMover] Set default value for flying to false until we can determine if we can fly in this zone.
      [11:37:34.323 V] [Poi.Clear] Reason: We live!, now to get back to where we were. Using return strategy -> Default: Death Location: <-198.8122, 82.4078, -290.8023>, AetheryteId: 21
      [11:37:34.326 D] Teleporting to Camp Bluefog
      [11:37:41.483 N] [FlightMover] Set default value for flying to false until we can determine if we can fly in this zone.
      [11:37:44.413 D] System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 000000A0, Size: 12
         at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
         at GreyMagic.MemoryBase.Read[T](IntPtr addr)
         at ff14bot.Objects.GameObject.get_Location()
         at ff14bot.Helpers.Poi..ctor(GameObject obj, PoiType type)
         at ff14bot.Behavior.BrainBehavior.<>c.(Object )
         at TreeSharp.Action.RunAction(Object context)
         at TreeSharp.Action.<Execute>d__13.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at TreeSharp.Decorator.<Execute>d__12.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at TreeSharp.PrioritySelector.<Execute>d__2.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at ff14bot.Behavior.HookExecutor.Run(Object context)
         at TreeSharp.Action.RunAction(Object context)
         at TreeSharp.Action.<Execute>d__13.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at TreeSharp.PrioritySelector.<Execute>d__2.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at TreeSharp.PrioritySelector.<Execute>d__2.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at ff14bot.Behavior.HookExecutor.Run(Object context)
         at TreeSharp.Action.RunAction(Object context)
         at TreeSharp.Action.<Execute>d__13.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at TreeSharp.Decorator.<Execute>d__12.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at TreeSharp.PrioritySelector.<Execute>d__2.MoveNext()
         at TreeSharp.Composite.Tick(Object context)
         at ff14bot.TreeRoot.()
      [11:37:44.424 D] DoAction Mount 1 0xE0000000
      
      After this error, the bot no longer navigates properly, and just runs straight off into whatever is in front of it.
       
      Last edited: Nov 4, 2015
    2. ExMatt

      ExMatt Active Member

      Joined:
      Jul 5, 2015
      Messages:
      1,030
      Likes Received:
      14
      Trophy Points:
      38
      When using EnableFlight, I had to create my own death handling since RB doesn't handle all the cases that were required, (Dravanian Hinterlands, or if you are using return to location option in EnableFlight settings). I also see this error when returning from death sometimes, (I think it has something to do with the death handling in RB being changed and I just haven't had a chance to see how to make my code work without the error). For me, it never causes an issue in fatebot, so i'm surprised that you are seeing the navigation issue.
       

    Share This Page