Discussion in 'EVEBot' started by SouperGuy, Jul 20, 2008.

  1. SouperGuy

    SouperGuy Active Member

    Messages:
    7
    If EVEBot v724 is not able to do kill missions at this time, pls let me know and stop reading now :) else, continue:

    This stuff is pretty kewl, lots of potential. To my knowledge everything is setup correctly. I get the following though, 2 different agents so far (locations omitted to protect the not-so-innocent):

    13:10:15: Preparing for warp
    13:10:15: DEBUG: To: 3000___6 At: 3000___8
    13:10:15: Setting autopilot from :) to :)
    13:10:15: Activating autopilot and waiting until arrival...
    13:11:04: 2) Warping to bookmark Encounter (Deadspace) - :) (Attempt #1)
    13:11:08: Warping...
    13:11:08: Reloading Weapons...
    13:11:46: Dropped out of warp
    13:11:53: obj_Missions: DEBUG: Executioner (589)
    13:11:53: obj_Missions: WARNING! Unknown Ship Type.
    13:11:53: obj_Missions: Paused Script. Complete mission manually and then run
    the script.

    Thanks
  2. GliderPro

    GliderPro Active Member

    Messages:
    184
    The only mission types supported at the moment are courier missions. EveBot will try to do kill missions if you use a Kestrel but you will most likely lose it.
  3. SouperGuy

    SouperGuy Active Member

    Messages:
    7
    Damn, thanks for the fast reply m8. Yes, I see that now in C:\Program Files\InnerSpace\Scripts\EVEbot\core\obj_Missions.iss
  4. SouperGuy

    SouperGuy Active Member

    Messages:
    7
    Courier

    Ok, trying the courier missions.

    Finds the agent ok (incl. getting to the correct station, docking, getting/accepting mission), goes to the objective, picks up cargo, returns to agent home base system. But after in the home base system. it doesn't dock, then heads back to the objective system :

    : ERROR: obj_Cargo.TransferItemToHangar: Must be docked!
    : obj_Missions: MoveToPickup
    : obj_Agents: DEBUG: stationName = NULL
    : obj_Agents: rVal = Y VI - Moon 2 - FedMart Warehouse
    : obj_Agents: DEBUG: mbIterator.Value.LocationType = objective.sourc
    : Preparing for warp
    : DEBUG: To: 3000xxx1 At: 3000xxx8
    : Setting autopilot from X to Y
    : Activating autopilot and waiting until arrival...

    Thanks for your time,

    Dave
  5. Sadoru

    Sadoru Active Member

    Messages:
    10
    The problem with not docking is (at least for me) only happening if your destination system or the last system before that has lag on jump in/out. Tried to mess with obj_autopilot.iss (increasing wait time) but that didn't work out.

    Otherwise it works fine for me for hi-sec systems (if you tick 'avoid lowsec' the bot won't change agents if he gets a lowsec mission and last decline is <4h).
  6. GliderPro

    GliderPro Active Member

    Messages:
    184
    Looks like some kind of desync or lag. At first I thought it might be cache related but Cyber fixed it a couple revs ago.
  7. SouperGuy

    SouperGuy Active Member

    Messages:
    7
    : ERROR: obj_Cargo.TransferItemToHangar: Must be docked!

    Ya consistent for me, get this when enters destination system (with objective cargo in hold). Doesn't warp to station, then just autopilots to the source system again, rinse, repeat.
  8. SouperGuy

    SouperGuy Active Member

    Messages:
    7
    EVEBot current version 729

    So if I'm using SVN correctly EVEBot is @ 729 ya? Just checking because the in game UI display 724 (I'm assuming that only changes with a major new release?).

    Thanks,
    Courier missions still broken, trying to troubleshoot myself, climbing the learning curve.

    P.S. what development environment do you guys use (if any) for the Lavish script?
  9. Chrom

    Chrom Active Member

    Messages:
    9
    BTW, not really exclusive missioner... would you please add "lost ship" check to all sub-scripts (Ratter, Miner, Mission)? Else it looks quite silly when pod constantly trying to run L4 mission or warp from belt to belt...

    Best move is just log off client when "lost ship" is detected. Slightly more advanced alternative - jump through any gate and log off.
  10. Hinge

    Hinge Active Member

    Messages:
    28
    I have had the same results. Missioner seems to get stuck in a loop warping between source and destination systems.
  11. Charles2584

    Charles2584 Well-Known Member

    Messages:
    18
    Yeah basically a pause needs to be put in for detecting when you are at the end of your autopilot and when it tries to dock.

    I'm not a big fan of EVEBOT (It's too big for me to debug at my skill level without spending an entire day at it, I'm not a fan of having to search through 22 files to find a function that isn't named well, or 3 files to find one that is named well) but from me playing around with the missioner that seems to be the problem.

    Probably a more efficient (time wise not processing wise) way of doing it is to do state checks.

    "Ok something's wrong, where am I"

    System location = Destination
    Do I have my cargo? yes? ok try and dock and start over the turn in process

    It looks like this is already in place somewhat but it's not checking if it has picked up the cargo yet. So instead it goes "ok, I'm at the destination, but I had a problem...lets go ahead and head back to the pick up point and try picking up just incase that is the problem."
  12. CyberTech

    CyberTech Second-in-Command Staff Member

    Messages:
    376
    You're welcome to write a new bot, all in one file, with function names that impart so much information you need a week to digest each one.

    svn update is your friend. GliderPro committed a trial fix for this issue already on the 30th.
  13. Charles2584

    Charles2584 Well-Known Member

    Messages:
    18
    I wasn't bashing EVEBOT so no need to get defensive, I just have other preferences. I think you misunderstood what I said as well, I didn't say I'd like to make an EVEBOT (which does many different things rather well), I'd prefer to have individual scripts that does one thing very well. A ratting script, a mining script, a hauling script, etc.

    Having a hauler/miner/ratter/missioner/freighter/ what have you in one bot but call separate behaviors just seems cumbersome to those that learn by editing existing code and branching out and writing their own code.

    I guess it's the *NIX geek in me.
  14. Charles2584

    Charles2584 Well-Known Member

    Messages:
    18
    I think you misunderstood what I said, I didn't say I'd like to make an EVEBOT (which does many different things rather well) in a one file format, I'd prefer to have individual scripts that does one thing very well. A ratting script, a mining script, a hauling script, etc.

    Having a hauler/miner/ratter/missioner/freighter/ what have you in one bot but call separate behaviors just seems cumbersome to those that learn by editing existing code and branching out and writing their own code.

    I guess it's the *NIX geek in me.
  15. chronosphere

    chronosphere Active Member

    Messages:
    1
    My Fix for Warp and Dock

    Hello,
    Sometimes, probably for lag, my ship is unable to dock and stays forever out of the jump gate in the "try to dock but too far loop", so I changed a couple of lines on the obj_Station.iss file:

    from (around line 187):
    Code (Text):


    if ${Entity[${StationID}].Distance} > WARP_RANGE
    {
      UI:UpdateConsole["Warping to Station"]
      call Ship.WarpToID ${StationID}
      do
      {
         wait 30
      }
      while ${Entity[${StationID}].Distance} > WARP_RANGE
    }

    do
    {
      Entity[${StationID}]:Approach
      UI:UpdateConsole["Approaching docking range..."]
      wait 30
    }
    while (${Entity[${StationID}].Distance} > DOCKING_RANGE)

     
    to:
    Code (Text):

    do
    {

      if ${Entity[${StationID}].Distance} > WARP_RANGE
      {
        UI:UpdateConsole["Warping to Station"]
        call Ship.WarpToID ${StationID}
        do
        {
           wait 30
        }
        while ${Entity[${StationID}].Distance} > WARP_RANGE
      }
         

      Entity[${StationID}]:Approach
      UI:UpdateConsole["Approaching docking range..."]
      wait 30
    }
    while (${Entity[${StationID}].Distance} > DOCKING_RANGE)
     
  16. Hinge

    Hinge Active Member

    Messages:
    28
    Revision .736 seems to have fixed a number of issues related to the missioner.

    I still have to kick it a few times, but am getting much better results.

    My advice, look for agents in the 'archives' division of friendly corps.
  17. Hinge

    Hinge Active Member

    Messages:
    28
    Well ok, spoke too soon. I managed to get the missioner to work for about 2 days off and on. Once for about 9 hours straight. Now not so good.

    Same consistant behavior every time, all agents i've tried. Not sure if i've exceeded some pointer in terms of the number of agents i've left in an "un accepted state", or what. Here is the log.

    08:47:34: obj_Agents: DEBUG: amIndex.Used = 7
    08:47:34: obj_Agents: DEBUG: This.AgentID = 3011490
    08:47:34: obj_Agents: DEBUG: amIterator.Value.AgentID = 3011848
    08:47:34: obj_Agents: DEBUG: amIterator.Value.State = 1
    08:47:34: obj_Agents: DEBUG: amIterator.Value.Type = Encounter
    08:47:34: obj_Agents: DEBUG: lastDecline = 08:30:26
    08:47:34: obj_Agents: DEBUG: This.AgentID = 3011490
    08:47:34: obj_Agents: DEBUG: amIterator.Value.AgentID = 3012044
    08:47:34: obj_Agents: DEBUG: amIterator.Value.State = 1
    08:47:34: obj_Agents: DEBUG: amIterator.Value.Type = Encounter
    08:47:34: obj_Agents: DEBUG: lastDecline = 19:00:00
    08:47:34: obj_Agents: DEBUG: This.AgentID = 3011490
    08:47:34: obj_Agents: DEBUG: amIterator.Value.AgentID = 3012063
    08:47:34: obj_Agents: DEBUG: amIterator.Value.State = 1
    08:47:34: obj_Agents: DEBUG: amIterator.Value.Type = Encounter
    08:47:34: obj_Agents: DEBUG: lastDecline = 19:00:00
    08:47:34: obj_Agents: DEBUG: This.AgentID = 3011490
    08:47:34: obj_Agents: DEBUG: amIterator.Value.AgentID = 3016553
    08:47:34: obj_Agents: DEBUG: amIterator.Value.State = 1
    08:47:34: obj_Agents: DEBUG: amIterator.Value.Type = Encounter
    08:47:34: obj_Agents: DEBUG: lastDecline = 14:09:43
    08:47:34: obj_Agents: DEBUG: This.AgentID = 3011490
    08:47:34: obj_Agents: DEBUG: amIterator.Value.AgentID = 3016810
    08:47:34: obj_Agents: DEBUG: amIterator.Value.State = 1
    08:47:34: obj_Agents: DEBUG: amIterator.Value.Type = Encounter
    08:47:34: obj_Agents: DEBUG: lastDecline = 19:00:00
    08:47:34: obj_Agents: DEBUG: This.AgentID = 3011490
    08:47:34: obj_Agents: DEBUG: amIterator.Value.AgentID = 3016812
    08:47:34: obj_Agents: DEBUG: amIterator.Value.State = 1
    08:47:34: obj_Agents: DEBUG: amIterator.Value.Type = Encounter
    08:47:34: obj_Agents: DEBUG: lastDecline = 19:00:00
    08:47:34: obj_Agents: DEBUG: This.AgentID = 3011490
    08:47:34: obj_Agents: DEBUG: amIterator.Value.AgentID = 3019289
    08:47:34: obj_Agents: DEBUG: amIterator.Value.State = 1
    08:47:34: obj_Agents: DEBUG: amIterator.Value.Type = Encounter
    08:47:34: obj_Agents: DEBUG: lastDecline = 19:00:00
    08:47:34: obj_Agents: DEBUG: Setting agent to Huunashin Varnen
    08:47:34: obj_Agents: SetActiveAgent Huunashin Varnen
    08:47:34: obj_Agents: SetActiveAgent: Found agent data. (2580)
    08:47:34: Undocking
    08:47:48: Undock: Complete
    08:48:02: ERROR: obj_Ship:UpdateModuleList - No modules found. Pausing - If
    this ship has slots, you must have at least one module equipped, of any type.
    08:48:02: Paused
    08:48:02: obj_Ship: DEBUG: Setting ship type to Badger Mark II
    08:48:02: obj_Ship: DEBUG: Setting ship type ID to 649
    08:48:02: DEBUG: To: 30001670 At: 30021672
    08:48:02: Setting autopilot from Pasha to Baviasi
    08:48:02: Activating autopilot and waiting until arrival...
    08:51:19: Docking at Baviasi X - Ishukone Corporation Factory
    08:51:19: obj_Ship: DEBUG: Setting ship type to Badger Mark II
    08:51:19: obj_Ship: DEBUG: Setting ship type ID to 649
    08:51:19: Warping to Station
    08:51:19: Preparing for warp
    08:51:19: Warping to Baviasi X - Ishukone Corporation Factory @ 0km
    08:51:22: Warping...
    08:51:22: Reloading Weapons...
    08:52:11: Dropped out of warp
    08:52:14: Approaching docking range...
    08:52:29: In Docking Range ... Docking
    08:52:29: DEBUG: StationExists = TRUE
    08:52:35: DEBUG: StationExists = NULL
    08:52:42: Finished Docking
    08:52:47: obj_Agents: Starting conversation with agent Huunashin Varnen.
    08:52:47: obj_Agents: Waiting for conversation window...
    08:52:48: Huunashin Varnen :: Greetings, Hinge
    08:52:48: Waiting for agent dialog to update...
    08:52:54: Huunashin Varnen :: Something just came up that's right up your
    alley. A group of battle-hungry lads from Baviasi have been requested by
    officials within the Caldari State army to Shesha II - Viziam Warehouse. I've
    agreed to their request, and I'd like you to carry it out. Deliver them to
    their destination, the faster the better.
    08:53:05: obj_Agents: DEBUG: amIterator.Value.AgentID = 3011490
    08:53:05: obj_Agents: DEBUG: amIterator.Value.State = 1
    08:53:05: obj_Agents: DEBUG: amIterator.Value.Type = Courier
    08:53:05: obj_Agents: DEBUG: amIterator.Value.Name = Army Recruits
    08:53:05: obj_Agents: DEBUG: amIterator.Value.Expires = 2008.08.12 13:00
    08:53:10: obj_Agents: DEBUG: HTML.Length = 3383
    08:53:10: obj_Agents: DEBUG: details.Length = 3383
    08:53:10: obj_Agents: DEBUG: Did not find "factionlogo". Rouge Drones???
    08:53:11: obj_Agents: DEBUG: typeID = 3810
    08:53:11: obj_Agents: DEBUG: volume = 1000.000000
    08:53:11: obj_Agents: DEBUG: typeID = 3810
    08:53:11: obj_Agents: DEBUG: volume = 1000.000000
    08:53:11: Waiting for mission dialog to update...
    08:53:17: Huunashin Varnen :: Thank you, and good luck.

    At this point all the dialog boxes close down and the ship just sits in the station.
  18. Hinge

    Hinge Active Member

    Messages:
    28
    OK figured it out.

    Lost my ship just before this started...

    Yes you guessed it, forgot to rename the new ship to coincide with the script.

    Woopsie!

    My bad. :yea:
  19. GliderPro

    GliderPro Active Member

    Messages:
    184
    Just a note... The ship names are optional. If you leave them blank EveBot will not try to switch ships.
  20. Hinge

    Hinge Active Member

    Messages:
    28
    Good to know, thanks for the info.
  21. Eania

    Eania Active Member

    Messages:
    11
    I ran into the same problem. Issue was my ship had no modules in it. Once I had one it started working.

Share This Page