Ima try doing it the other way then i guess and leaving everything default. After not being able to figure it out i set all the atma hours to 0 and the atma amount to 1 hoping that it would farm one zone until he got an atma, and then teleport to the next. This was not the case. I woke up with 5 of the same atma lying on the floor dead lol. So ima try it the other way Either way, if its not based off server time then it shouldnt be teleporting every minute. It should be teleporting every hour. How would i go about fixing this?
Hi Neverdyne, thanks for this plugin, however is there a way to stay in the same zone till we get an atma and then go to next zone ? After setting atma hours to 0 and atma amount to 1 (like precedent poster) he just stays in the same zone.
Is there any way to make this NOT teleport every fucking hour (read = ONE FATE per zone before teleport)? I looked up something else called '' Atma Hunter '' but someone there said it's too old to use and you should use this instead .. (+atma hunter doesn't show up on my plugins for me for w/e reason ..) All I want is a bot to farm the same zone for the fates until it drops, THEN teleport to the next zone and do it again. Also I just looked at my bot stand in North Shroud for an hour before teleporting to next zone. It only stood at the aetheryte. There were 3 fates up the whole time, and it never even moved. Manually moving away was impossible because default loc to return to is aetheryte. WTF? I also set minimum level for fates at 1 in the plugin settings yet I'm witnessing the bot run past multiple fates in Western La Noscea only to run to the lv44 one way farther away.
Dude, be polite and ask nicely... If your char stood at the aetheryte while there were fates up it's because those were boss fates and you have to change settings in fatebot options (aka boss % wich is at 60% by default you have to put it at 0% if u want him to do them solo). Fatebot is working perfectly you just have to know how it works.
I already did that, thanks tho. Boss fates are set to 0% and the fates in the scenarios above weren't even boss fates. The character still just stood at the Aetheryte until the eorzean hour passed only to teleport away. Which in this case makes it impossible to get an atma from a specific zone like that because it never does anything but stand there.
I am not maintaining this, it was meant as a quick side project. I'm too busy with the other projects. If someone wants to fix it, go ahead, all the source is there.
hmm..is there anyway I can change the teleporting from once an ingame hour to once a real hour? Gil isn't really thaaaat big an issue, but it does add up
Yeah, it's only one line of code you have to change. Go to the TeleportLogic.cs file, and on the TargetByAtma() method, change the following: ORIGINAL: FIXED: That should work, it'll now use your local time.
Thanks a bunch, just started so still trying to figure out where I can change stuff and going thru the apis! hmm...I also noticed it sometimes mounts and the immediately demounts and tps seems a little wierd looking but probably not a big deal!
UPDATE - Atma hunting should be fixed. It was using Eorzea time, which made you teleport around a lot. It now uses JST. - Added some areas for leveling, and changed the level ranges to better values.
You say this on your first page.... Download the zip folder. Extract it and move it inside your plugins folder, so that it looks like: "/Rebornbuddy/BotBases/FateStayTeleport". Is it plugins folder or install in the botbase folder? Thanks
Thank you for the plugin. It took around 9 hours to farm 12 atmas for me, and I'm so happy I didn't have to go through that boring grind myself!
No problem I got it to work by the plugins folder but thought I was making it work incorrectly Thanks and at least you know of the mistype BTW thanks for all your hard work on ALL the other stuff!
it only seems to run the 2 fates in the starting area is that normal?, also is there a way to get this to grind mobs while its waiting for fates?
