+- MMOMinion (https://www.mmominion.com)
+-- Forum: FFXIVMinion (https://www.mmominion.com/forumdisplay.php?fid=87)
+--- Forum: Support - English, Deutsch, 中文 (https://www.mmominion.com/forumdisplay.php?fid=92)
+---- Forum: English Support & Questions (https://www.mmominion.com/forumdisplay.php?fid=93)
+---- Thread: Marker issue (/showthread.php?tid=9150)
Marker issue - dai-suu - 09-11-2014
I made new small mesh for fishing and put a new fishing marker
but minion didnt create .info file
so after zone changes I need put a marker again
RE: Marker issue - Cichard - 09-11-2014
make sure your folder for minion is in C:\minion and also make sure its not right protected.
RE: Marker issue - TauTau - 09-12-2014
since I have the bot I have it in the same directory, and I already did this (make new mesh, drop markers). However, I now have the same problem. What's also strange, the mesh I created isn't empty but the same mesh as before (without markers though). Or does the "record mesh" now mesh a huge area instantly? However, can't drop markers. Bot doesn't create file, and doesn't write to a manually created.
The "C:\minion" path doesn't make any difference from a professionals view, since I already have everything under D:\games\ffxiv\minion, so UAC doesn't make any difference
RE: Marker issue - Ace - 09-12-2014
Make sure your markers have unique names. Markers within the same zone, cannot share names.
Edit: I'll investigate to make sure there aren't other potential problems in this area.
RE: Marker issue - TauTau - 09-16-2014
Usually when I do that manual marker/mesh stuff it's only for fishing, if I'm after a specific fish, so I just mesh a little area and drop maybe three markers (simply named fish1/fish2/fish3) to be able to stay in the spot. So double marker names shouldn't be an issue. Also the error in console (can we have copy&paste there please? ;)) was more a "cannot find file" type. This was the first time I had that problem, I'll try after the update.
RE: Marker issue - Ace - 09-16-2014
Several marker problems should be corrected after the new update goes into effect.