MMOMinion

Click on the ingame mmominion button, Bottox folder, then Dailies Manager.
Otherelse, wiki :)

http://wiki.mmominion.com/doku.php?id=da...alm_reborn

Okay, it seems I had weird meshes for some reason - I just deleted my whole Navigation folder and re-installed everything from scratch. It does work better now, I'm still testing, but it's already much more automated than before.

One thing I noticed on an alt: If you click on "Sylph Rank 1 to 2", the bot teleports to little Ala Mhigo again and again and again, endlessly. This was after accepting the quest "Pilfered Podlings". A reload fixed it, maybe it was because I did the Amalj'aa dailies before. After the reload, it tries to accept the quest over and over again from Voyce, apparently endlessly as well, which is pointless as the quest is already in my quest log. There is currently no way to stop this (i.e. I can't keep the bot from running back to the NPC over and over again by anything else than reloading or quitting the game) or tell the bot that he already accepted the quest after a reload, it has now to be done by hand.

If you could add something like "is this quest already in my log?" to the Rank X to X quests, that'd be great.

Can you clarify the new navigation system downloads on dropbox? I see "new" and "old" but when I tried out the new navigation system download it just kept teleporting me to the aetheryte at whichever beast tribe i was doing.

The new nav system is not live yet and seems to be delayed at least for 2 weeks. So i deleted the new files on dropbox and will share them again one time new nav system is out. I allready ran dailies with it and it definitely fixes all nav problems we have since months.

One thing I noticed when doing the Kobold dailies: If you're playing as a healer class and have Assist running (as is required, I think the bot also auto-starts Assist mode now, which is quite nice), and the bot drops down to that one dude you need to talk to, as soon as he dismounts due to interacting with the NPC, Assist kicks in and heals due to player character having like 10% hp after dropping down which interrupts the NPC interaction. The bot then just acts like it successfully spoke to the NPC, but that leads to follow-up quests not being done properly as one step is missing.

It then ports to the nearest Aetheryte and just idles there.

Maybe you could add something like 'double-check if the NPC has been talked to' or something to avoid this? :)

This part is supposed to work since months, but since this particular function has been updated recently that's possible it brings bugs on Kobolds. I'm going to check this. Do you remember if it was on low, mid, or high level quests?

(03-01-2018, 02:44 PM)InDaSkyz Wrote: [ -> ] @Pairak Mog is ready, we're waiting for a minion update to start tests. The beta will be available as soon as the minion is ready in the Heavensward Pack.

Any update on Mog or Ixal?

Mog beta this week i hope
Mog and Ananta release in single volumes next week.

This has been happening to me recently for Vath dailies, it will port fly over accept all the quests, get onto the quest vehicle spew out this error and continuously port back to the aetherite.

https://prnt.sc/iscqvd

Looks like a mesh that is not updated since a long time. Vaths quests actual state is simple, it remains one bug (the most tricky of course): If 2 or 3 quests are given by the same npc, and 2 of those 3 quests need you to interact with this same npc at the middle of the quest, your character will loop the quest since the bot thinks it talked to the npc and unlocked next part of the quest, which obviously is not unlocked so the bot will not find the interactions. It's the exact same problem on Vanu Vanu actually. And it allways happen after the end of the 1st quest, so during the 2nd or 3rd quest.
That needs to be fixed definitely, even if we need to run the quests like 1 +1 +1 and no 3 at the same time, even if it takes 2 or 3 minutes more in order to finish the quests.