Changed to my WHM earlier and Agil went into an endless loop equipping gear back and forth.
It looked like it was where particular body pieces cant equip head gear. So it would equip body, then try to equip head gear and would keep looping.
Was just leaving for work so didn't get log.
Fresh install, deleted everything. Still nothing. Maybe its something on my end? Should i delete RB and reinstall everything?
Yup, that's a problem. There's no way for Agil to know if a piece of equipment will remove something else. Since Agil checks equipment every 5 seconds, it'll see the empty slot and equip something there constantly. I don't know of an easy solution for this. On the other hand, it shouldn't affect anything really. The check happens every 5 seconds and it won't happen when you're in the middle of something, like gathering or crafting or doing a fate, so it'll only happen when your character is running around. You could leave it like that if you wanted and it won't stop your character from doing stuff. You can also disable optimization for those specific slots in the Settings so it won't check on the problematic slots.
What's the error? Got any logs?
Does it go to repair? If you could, could you go into Settings and change "Debug: False" to "Debug: True" then start the bot again, and attach the log? It'll let me know what's up. The check doesn't happen when you're doing something, like in combat, in a fate, crafting, gathering window up, etc. It only happens in between activities. Best way to test it, teleport to Limsa Lominsa, unequip something, and start Fate Bot. It should almost immediately equip something back on the empty slot. You can also test repair by setting the "minimum durability" on Settings to 100, then start Fate Bot anywhere with something in your gear damaged, it should immediately go to repair.
When you put it that wayI guess I could add an "unsafe" self repair, were if you don't meet the requirements the bot gets stuck.
AgilSettings.yaml
Repair: true
OptimizeGear: true
MinimumDurability: 60
MinimumItemLevel: 1
Good evening! I am running version 1.0.9.
While I was running one of the crafting profiles, Agil took over to mount up and run to a merchant to repair, was successful, mounted up and ran all the way back, and made it. However! Once I got back to the starting position, he stayed mounted, and the profile failed to continue.
Since Agil is in control while the moving/repairing/returning, can you add one last check to the return move to verify character has dismounted before releasing control back to the profile? Thank you!
Keep up the fantastic work!
EDIT: Also, I've been following the thread, and am not seeing some options I would have expected to in the settings menu. Here are the only options I get when I pull up the settings menu.
[HIDE][/HIDE]Code:AgilSettings.yaml Repair: true OptimizeGear: true MinimumDurability: 60 MinimumItemLevel: 1
Is there something that I am missing, was it removed from this current version, or do I need to add in the other options manually?
Again, thank you very much!
So i tried what you said w/ the fate bot, it switched gear for every other class except for brd. However, it left some slots empty instead of filling it with gear. Attached is a log.
EDIT: Also, I've been following the thread, and am not seeing some options I would have expected to in the settings menu. Here are the only options I get when I pull up the settings menu.
This is the kind of stuff I just don't know it needs until someone finds it, thanks for the report. I'll add a force dismount at the end.
It seems like it equipped stuff for the other classes. For the Bard, it looks like it went to repair first thing after starting the bot, then it went directly to a fate. The optimizer won't equip anything while its repairing nor while it's going to do a fate. It only does it during the "downtime" of the bot. For Fate Bot, that's when no fates are going on. For OrderBot, that's when you're not locked on an item crafting or the gathering window is up. After the fate ends, you should see it equip everything. The problem with letting the optimizer work when going to do a fate is that fates often synchronize the level, causing the optimizer to change to something for the new level, which is usually not what you'd want.
The idea is that if you leave your bot doing fates overnight, there will be times when no fates are around and that's when the repair and gear optimizer kick in. It works different for OrderBot though.
Did you download the new zip from the original post? The settings on in have the full list of options. I'm no longer using GitHub.
Repair: True
OptimizeGear: True
Spiritbind: False
MinimumDurability: 60.0
MinimumItemLevel: 1
Debug: False
SlotEnabled:
MainHand: True
OffHand: True
Head: True
Body: True
Hands: True
Waist: True
Legs: True
Feet: True
Necklace: True
Earring: True
Bracelet: True
Ring1: True
Ring2: True
Hmm, I'll test it out with a fresh install, let me see.
@Inferno as for your questions:
1. Your gear can be anywhere except your retainer. It'll check your armory and bags.
2. It is plug and play except for Spiritbind. If you want to Spiritbind, you have to enable it on the Settings. But once enabled, it should just be plug and play, nothing else required.
3. I have tested it with OrderBot and FateBot so far, both crafting and grinding, and it works fine for me. I haven't tested it for the old Grind bot.
4. When you enable Spiritbond on the Settings, it'll work by equipping the item with the lowest spiritbond value that is greater or the same as the minimum item level you specify in the settings. If you have 100% spiritbond endgame gear, and 0% bond level 1 gear, and you leave min ilevel to 1, it'll equip the level 1 gear. It'll always equip the gear with the lowest spiritbind and THEN its stats. So stats are secondary when Spiritbond is enabled. You don't need to move your endgame gear out or anything.
WORKING as charm. only thing is annoying is that agil will force the items even after u switch them to want you want to wear.....