i.m using the bot for mining.
yesterday evening everything was ok, in the morning after a quick update, the bot doesn.t move after he has mined the first node.
no idea what to do. i.ve tried with a new mesh, new markers...
in the console i get those messages i.ve screen shoted.
ty
P.S.: Fixed my "bug" when bot was stopping after mining 1 node.
Deleted everthing in folders LuaMods/ffxivminion & LuaMods/minionlib, i let the autoupdate run. Made new mining markers and everything it.s ok.
I think it started ignoring the Combat Range % setting, it goes in closer than I set it to (much closer by 5-6y). Even after it did that I can go back just fine until I'm out of skill range and then it goes back in to that closer range. Even tried removing my mods.
Also, can you make it optional that the character doesn't go to town when it dies in fates?
(12-13-2013, 03:05 PM)Koopla Wrote: [ -> ]I think it started ignoring the Combat Range % setting, it goes in closer than I set it to (much closer by 5-6y). Even after it did that I can go back just fine until I'm out of skill range and then it goes back in to that closer range. Even tried removing my mods.
Also, can you make it optional that the character doesn't go to town when it dies in fates?
I don't see anything in the code that would have changed the range behavior...I'll have to run some tests. Did you experience this in grinding/fates or both, and what class/profile are you using?
Am...About left-right running, 5 minute ago my bot in Northen Thalanan was running again this way...Dunno why, it was only 1 FATE available..In coerthas all was good.
And about "kill atacking non fate mobs" in fates menu - this as i saw in some times works, in some times not) It'll be greate to repair it. And ur new Blaklist cleans after each start bot programm and reload luas...
(12-13-2013, 05:41 PM)f3re Wrote: [ -> ] (12-13-2013, 03:05 PM)Koopla Wrote: [ -> ]I think it started ignoring the Combat Range % setting, it goes in closer than I set it to (much closer by 5-6y). Even after it did that I can go back just fine until I'm out of skill range and then it goes back in to that closer range. Even tried removing my mods.
Also, can you make it optional that the character doesn't go to town when it dies in fates?
I don't see anything in the code that would have changed the range behavior...I'll have to run some tests. Did you experience this in grinding/fates or both, and what class/profile are you using?
Fuck now I did some testing (waited until a bot started attacking a stationary fate mob, went back until the skills were red (out of range) and the bot seemed to take only 2-3 squares of steps) and it seemed good, maybe something on my end I'm not sure, will do some more checking and will report if it's bad.
You should probably remove this auto update, auto download of meshes. If we set our own markers for gathering it changes the md5 and next time we launch the bot it redownloads the meshes, removing our manually added markers.
I'm a little pissed that I added 30 or so markers to my meshes this morning, had a client crash, restarted and the only meshes that I added markers to were overwritten, and now I don't have those markers.
Guys, i wanna to know 1 more thing, did smb get banned in Final Fantasy 14? I read topic about banned, but there i saw only GW2 players...And what about FF?) About that "lug" left-right running i hope those, who seen it haven't written to support about it...
(12-13-2013, 07:14 PM)j4x0rr Wrote: [ -> ]You should probably remove this auto update, auto download of meshes. If we set our own markers for gathering it changes the md5 and next time we launch the bot it redownloads the meshes, removing our manually added markers.
I'm a little pissed that I added 30 or so markers to my meshes this morning, had a client crash, restarted and the only meshes that I added markers to were overwritten, and now I don't have those markers.
We are very sorry about this, we didn't mean to force update anything rather than the mesh itself. It should just download the marker files if you don't already have them and not force update. It was an error on our part.
(12-13-2013, 07:14 PM)j4x0rr Wrote: [ -> ]You should probably remove this auto update, auto download of meshes. If we set our own markers for gathering it changes the md5 and next time we launch the bot it redownloads the meshes, removing our manually added markers.
I'm a little pissed that I added 30 or so markers to my meshes this morning, had a client crash, restarted and the only meshes that I added markers to were overwritten, and now I don't have those markers.
That really sucks...sorry, sincerely. We'll make sure that kind of thing doesn't happen again. If you're paranoid, you can make a backup of the *.info files as those are the ones that contain the marker data. Not that you should have to do that, but just for future reference.
(12-13-2013, 07:14 PM)j4x0rr Wrote: [ -> ]You should probably remove this auto update, auto download of meshes. If we set our own markers for gathering it changes the md5 and next time we launch the bot it redownloads the meshes, removing our manually added markers.
I'm a little pissed that I added 30 or so markers to my meshes this morning, had a client crash, restarted and the only meshes that I added markers to were overwritten, and now I don't have those markers.
what not just copy the file rename it then make it your own??
this way nothing can ever happen to it