2 Questions...
1.) Is there a way to have the bot not blow up when you switch areas? In one of Kick's profiles (I think Empire 10-17 Questing) at the end it has you board your ship. I've never tested this part of the profile (I usually finish a planet manually). Does the bot do this correctly? Any time I have the bot latched onto an instance of SWToR, and switch planets, instances, ect, it blows up. Anyone have a fix for this, or is it just me?
2.) I'd like to be able to have my bots just move forward (for example, through an instance portal). However, You have to have the cords at this point. For example, if you try set the cords before a portal, you never zone. If you calculate what the points would be past the zone-in and try a MoveTo to that location, the bot thinks it hasn't reached it's destination and keeps trying. My work around right now is I have a plug-in that monitors where we are, and when we reach a specific coord, I move forward with a method in the Navigator class (I can't remember the method name). It works "ok", but I was hoping we could have a profile tag made, something like "AutoMove" that just moves forward, backwards, ect. Or, remove the EndX/Y/Z attributes from the <JumpTo> tag (I had this working as well, but it would keep trying to end at the End points, and if there was a loading screen, it just made matters worse).
I hope that makes sense.
1.) Is there a way to have the bot not blow up when you switch areas? In one of Kick's profiles (I think Empire 10-17 Questing) at the end it has you board your ship. I've never tested this part of the profile (I usually finish a planet manually). Does the bot do this correctly? Any time I have the bot latched onto an instance of SWToR, and switch planets, instances, ect, it blows up. Anyone have a fix for this, or is it just me?
2.) I'd like to be able to have my bots just move forward (for example, through an instance portal). However, You have to have the cords at this point. For example, if you try set the cords before a portal, you never zone. If you calculate what the points would be past the zone-in and try a MoveTo to that location, the bot thinks it hasn't reached it's destination and keeps trying. My work around right now is I have a plug-in that monitors where we are, and when we reach a specific coord, I move forward with a method in the Navigator class (I can't remember the method name). It works "ok", but I was hoping we could have a profile tag made, something like "AutoMove" that just moves forward, backwards, ect. Or, remove the EndX/Y/Z attributes from the <JumpTo> tag (I had this working as well, but it would keep trying to end at the End points, and if there was a loading screen, it just made matters worse).
I hope that makes sense.