jackie what issues is it causing with fate grinding?
mounting from what I've seen works fine guys, I tested every mount I have and it works perfectly.
I cannot test the goobue, and unicorn as I do not have those. However every other mount I tested works fine.
I have noted the following bugs. If party mode is enabled and you are not in a party it will bug out and randomly attack things. I'll find a fix for this soon. in the mean time just make sure you only have it enabled if you are in a party.
There is still no way to know if a monster is claimed by you or not. and there will be instances where it will attack a monster that is not claimed by you. I'm going to beat my head on it and see if I can find a solution for it.
The spamming of the stance should not be occurring anymore I removed that portion of the bot.
Koopla in regards to your question I haven't really done any testing with pets. I know that the companion should work well, the pet should as well it is after all in the party, I'll see if I get a chance to do some testing on it. and let you know.
Now it's important to note guys I'm working on a fairly large module which is consuming alot of my time. and I'm unable to give this module the attention I did before if you have an issue you can try popping in on the live chat the website has I hang out there a lot.
what its causing with fate grind is to kill mobs that are not fate mobs. everyone thas been having problems with the bot killing mobs that dont belong to a fate have this mod. I been running fates for a while and no problems i installed this mod to day for hte first time and bamn the bot starts attacking mobs that are not part of the fate even if they are not listed in the priority list. i then removed the mod and everything working fine again.
I'll take a look into this and release an update that fixes it.
Wondering if there is any way to make it so this will not target mobs outside of the mesh? At current, I have a spot but a mob is constantly spawning that is in a place where I can target but cant attack. Its not in my mesh but the program is picking it up because it is one of the priority mobs im attacking.
why not just one of the 100% meshes and then place your own grind marker
(12-08-2013, 10:30 PM)wildicedemon Wrote: [ -> ]mounting from what I've seen works fine guys, I tested every mount I have and it works perfectly.
I cannot test the goobue, and unicorn as I do not have those. However every other mount I tested works fine.
Just gave 1.97 a try. Here are my results. Blocks are with different mounts selected. No other options selected. Minion config is Grind, Fates/Fates Only, Rest in Fates. This is using a mesh that I ran to get from 43 to 50. Other modules include ymko's toolbox, ymko's crafting tool, and XPStats.
Selected Goobbue mount.
Fate around 300 meters away. Bot stood there. Started walking toward the fate, bot ran back to evac. Waited around 2 minutes. Summoned a mount manually and bot ran toward fate. Fate ends, bot sprints and breaks aggro. Stands still. Wait around 1 minute and the bot summons Ahriman, Goobbue is still the selected mount. Bot runs toward Fate #2.
Changed mount to Ahriman.
Bot is currently completing Fate #2. Fate #2 ends bot sprints and breaks aggro. Bot pauses, standing still for around 5 minutes. Watch fate spawn, and complete, on map on other side of Mor Dhona. Toggle auto-run, bot moves an inch before stopping. Manually summon mount, bot begins moving toward fate. Despawn mount, bot continues to stand in place.
Changed mount to Coeurl.
Stop/Start bot to clear possible hold. Bot continues to stand in place. Checked console for error, nothing evident. After 3 more minutes, bot spawns Ahriman mount. Bot moves toward a newly spawned FATE (#4) and begins FATE.
Change mount to Legacy Chocobo.
FATE completes. Bot doesn't break aggro. Disable bot, manually run from attacking mobs. Re-enable once out of range. Wait 15 seconds, bot summons Magitek mount.
Conclusion: Removed module for second time due to mount being incredibly unpredictable...
(12-10-2013, 08:06 PM)blazernt Wrote: [ -> ] (12-08-2013, 10:30 PM)wildicedemon Wrote: [ -> ]mounting from what I've seen works fine guys, I tested every mount I have and it works perfectly.
I cannot test the goobue, and unicorn as I do not have those. However every other mount I tested works fine.
Just gave 1.97 a try. Here are my results. Blocks are with different mounts selected. No other options selected. Minion config is Grind, Fates/Fates Only, Rest in Fates. This is using a mesh that I ran to get from 43 to 50. Other modules include ymko's toolbox, ymko's crafting tool, and XPStats.
Selected Goobbue mount.
Fate around 300 meters away. Bot stood there. Started walking toward the fate, bot ran back to evac. Waited around 2 minutes. Summoned a mount manually and bot ran toward fate. Fate ends, bot sprints and breaks aggro. Stands still. Wait around 1 minute and the bot summons Ahriman, Goobbue is still the selected mount. Bot runs toward Fate #2.
Changed mount to Ahriman.
Bot is currently completing Fate #2. Fate #2 ends bot sprints and breaks aggro. Bot pauses, standing still for around 5 minutes. Watch fate spawn, and complete, on map on other side of Mor Dhona. Toggle auto-run, bot moves an inch before stopping. Manually summon mount, bot begins moving toward fate. Despawn mount, bot continues to stand in place.
Changed mount to Coeurl.
Stop/Start bot to clear possible hold. Bot continues to stand in place. Checked console for error, nothing evident. After 3 more minutes, bot spawns Ahriman mount. Bot moves toward a newly spawned FATE (#4) and begins FATE.
Change mount to Legacy Chocobo.
FATE completes. Bot doesn't break aggro. Disable bot, manually run from attacking mobs. Re-enable once out of range. Wait 15 seconds, bot summons Magitek mount.
Conclusion: Removed module for second time due to mount being incredibly unpredictable...
I'd don't know what to tell you blazernt I have two bot's running doing fate's and have been as we speak working flawlessly both of them have and are doing fate's aswell, using this module as well as the craftingtool made my yMKO. Both are running without incident. Mounting is working great I can switch whenever I want and everything works just fine. I don't know how many have this issue but by all means everyone that does please say so, so I know if it's isolated to just a few or if alot are having it. Thank you.
blaznt try removing xpstats and let me know if that fixes it.
(12-09-2013, 10:51 PM)jackie1234 Wrote: [ -> ]why not just one of the 100% meshes and then place your own grind marker
Im gonna guess you didnt understand what I said. Ive made the mesh but the area where the mob spawns is only reachable by a series of jumps, which Ive actually seen the bot do once or twice but 9/10 times it just keeps jumping against the cliff trying to attack the target. Somehow or another Ive found a sweet spot between my mesh point and the range to attack mobs finally and Ive had it running for a few hours now without a problem.
I've said it before but this is really good work! Please keep it up.
(12-10-2013, 10:18 PM)m33pm33p Wrote: [ -> ] (12-09-2013, 10:51 PM)jackie1234 Wrote: [ -> ]why not just one of the 100% meshes and then place your own grind marker
Im gonna guess you didnt understand what I said. Ive made the mesh but the area where the mob spawns is only reachable by a series of jumps, which Ive actually seen the bot do once or twice but 9/10 times it just keeps jumping against the cliff trying to attack the target. Somehow or another Ive found a sweet spot between my mesh point and the range to attack mobs finally and Ive had it running for a few hours now without a problem.
I've said it before but this is really good work! Please keep it up.
just add some off mesh connections 2 way ones.
(12-10-2013, 09:55 PM)wildicedemon Wrote: [ -> ] (12-10-2013, 08:06 PM)blazernt Wrote: [ -> ] (12-08-2013, 10:30 PM)wildicedemon Wrote: [ -> ]mounting from what I've seen works fine guys, I tested every mount I have and it works perfectly.
I cannot test the goobue, and unicorn as I do not have those. However every other mount I tested works fine.
Just gave 1.97 a try. Here are my results. Blocks are with different mounts selected. No other options selected. Minion config is Grind, Fates/Fates Only, Rest in Fates. This is using a mesh that I ran to get from 43 to 50. Other modules include ymko's toolbox, ymko's crafting tool, and XPStats.
Selected Goobbue mount.
Fate around 300 meters away. Bot stood there. Started walking toward the fate, bot ran back to evac. Waited around 2 minutes. Summoned a mount manually and bot ran toward fate. Fate ends, bot sprints and breaks aggro. Stands still. Wait around 1 minute and the bot summons Ahriman, Goobbue is still the selected mount. Bot runs toward Fate #2.
Changed mount to Ahriman.
Bot is currently completing Fate #2. Fate #2 ends bot sprints and breaks aggro. Bot pauses, standing still for around 5 minutes. Watch fate spawn, and complete, on map on other side of Mor Dhona. Toggle auto-run, bot moves an inch before stopping. Manually summon mount, bot begins moving toward fate. Despawn mount, bot continues to stand in place.
Changed mount to Coeurl.
Stop/Start bot to clear possible hold. Bot continues to stand in place. Checked console for error, nothing evident. After 3 more minutes, bot spawns Ahriman mount. Bot moves toward a newly spawned FATE (#4) and begins FATE.
Change mount to Legacy Chocobo.
FATE completes. Bot doesn't break aggro. Disable bot, manually run from attacking mobs. Re-enable once out of range. Wait 15 seconds, bot summons Magitek mount.
Conclusion: Removed module for second time due to mount being incredibly unpredictable...
I'd don't know what to tell you blazernt I have two bot's running doing fate's and have been as we speak working flawlessly both of them have and are doing fate's aswell, using this module as well as the craftingtool made my yMKO. Both are running without incident. Mounting is working great I can switch whenever I want and everything works just fine. I don't know how many have this issue but by all means everyone that does please say so, so I know if it's isolated to just a few or if alot are having it. Thank you.
blaznt try removing xpstats and let me know if that fixes it.
I also had to stop using the mod because it refuse to use the mount.