-
Content Count
20 -
Joined
-
Last visited
Community Reputation
1 NeutralAbout freebeer2go
-
Rank
Bronze IV
Recent Profile Visitors
680 profile views
-
1. bot uses leaguestone regardless "Right Click leaguestone before stashing" option is marked or not 2. the default forcesell pickit doesn't have leaguestones, seems it was reverted to a previous version. 3. crashing still, on average every half hour or so for me. 4. I saw the bot got stuck clicking a 4L glove from stash, for unid chaos recipe for some reason. I had to stop the bot to unstuck it
-
There seem to be a wave of bans recently, an entire guild got banned, even innocent players. It seems the botter joined a guild that are mostly innocent players, then the botter got banned, with the entire guild.
-
How do you guys deal with new config every version?
freebeer2go replied to topic's freebeer2go in Archives
That's weird, I'm pretty sure the bot intentionally does this, it activated an elreon mission by talking to him, stayed there and killed monsters, then after the mission is over, the bot talked to Elreon to get credit for the mission. Unless I accidentally downloaded skynet, the bot definitely seem to be intentionally doing master missions. It also activates haku missions, then just enter the haku cave, and then logout instantly, then log back in, and restart from town. These are the only two masters I've observed so far. -
How do you guys deal with new config every version?
freebeer2go replied to topic's freebeer2go in Archives
I don't think it's accidentally activating master mission, it's doing it intentionally, but mostly they fail and it just slow down farming. -
The bot tells me to do new configs every version, and I do it. It's pretty tedious to redo every setting, and edit pickit. How do you guys deal with it? Btw how to stop the bot from doing master missions on dried lake?
-
I think the reason is you have the "chaos recipe mode" set to disabled?
-
You could manually set this? where is this setting?
-
Bug with attacking invisible monster/Running back and Forth
Qwilleran replied to topic's freebeer2go in Archives
Also when the bot meets a divine shrine, the bot would keep attacking the monsters, but not take the divine shrine buff, resulting it endlessly attacking monsters that can not die. -
Bug with attacking invisible monster/Running back and Forth
Qwilleran replied to topic's freebeer2go in Archives
Same here, it keep trying to open the voll's confession thing, and looping endlessly there. -
用smart pickit里面的规则,我直接把Rare区域的都删了。总之只要smart pickit规则里面没有的东西,就不会pickup
-
I think it can be detected if it encounter a bug and starts looping the same action for a long time. So if you play on your main, I think you have to babysit it all the time, which is what I do. If you see it looping, intervene immediately.
-
Isn't this as easy as go to the top of the list (by pressing up numerous times), then start from there? there's really no reason to use screen slot position instead of real slot position. I don't afk bot, so my main shouldn't be banned. I will intervene my bot within 5 seconds of looping. I just don't like to farm by hand because wrist/arm pain. Just sometimes I go take a shit and come back and see my bot logged into another char and gets it killed. This seem shouldn't happen when it's so easy to fix and the bot can do many more advanced things, but keep login the wrong char. I know I maybe a minority user, but it's extremely annoying to me that every time the bot chicken (mostly for no apparent reason), it'll login the wrong char, and I have to babysit it back to the correct char, and when I'm happened to not notice it immediately, then it'll login the wrong char and kill it in dried lake.
-
I have 25+ char on my account, my bot char is slot 13, but when it relogin, it doesn't start scrolling from the #1 slot, it starts at the #1 position currently shown on screen (which could be say #8 slot in my account in reality). This behavior leads the bot to eventually scroll to the end of my account and login the 25 or 26th char. This happened to me numerous times, and resulted in killing my summoner char on dried lake. My suggestion would be always scroll to the real #1 slot and start there, instead of just assuming the #1 slot currently shown is the real #1 slot. Also is it possible to set the char name to login, so it can't login the wrong char?