[tkinParticipant]

zebby wrote:

Miqobot posted an update about this aboput a week ago as it was causing some problems (me included).

If you download the new version of the bot it fixes the problem, its not a scheduled new version update but it has an update for Revisit all the same and it solved my own Revisit issues

Is that version 1.3.51? That’s what I have now. Or should I delete the version I have and just redownload it?

• This reply was modified 3 months, 2 weeks ago by  tkin.

[tkinParticipant]

I must be “very” unlucky… or I’m just doing something wrong.

I’m using Miqobot 1.3.51 (I don’t see any other version available to use)
I’m using Orange-Script-scenario-with-Rroneek-Horn-Token-buys-2.txt
I removed Solid Reason and Ageless Words and replaced it with the macro, which appears to work properly.

I got a revisit on all three nodes I tried this on. I don’t know if I’m hitting that corner case you mentioned, or something else is just wrong. Every time I get revisit, it locks up saying it can’t teleport (because I’m still on the node). Is there something else I need to do? Or did I just get absurdly unlucky 3x in a row?

I’m watching it run now.. curious to see if it Revisits and fails every time.

[tkinParticipant]

Thanks for sharing!

[tkinParticipant]

I understand that most (all?) grids have been made by the community. Up to now, I’ve been mostly a “taker” and not a “provider.” All the grids I’ve tried making before have been pretty bad.

What are the best practices for making new grids? Specifically, things like efficiency while not looking too “bot-ish.”

I see some grids use a “beacon(?)” above a set of nodes, and then it spiders down into a circle of mount/foot lines around the area. Is that what most people do? Is there a better way? I wouldn’t mind making grids and providing them to the community, but I don’t want to provide hack-ish garbage either.

• This reply was modified 3 months, 3 weeks ago by  tkin.

[tkinParticipant]

I’ve used it on GNB and DRK. No issues. Sure, it doesn’t know about certain abilities, but it does clear it and the time isn’t so bad. I think I average about 11.5 minutes. Maybe other jobs are broken?

[tkinParticipant]

No issues here on GNB or DRK in Holminster Switch.

[tkinParticipant]

It was a 3 year old post.

But I can chime in. I was banned for a non-miqobot related issue that was bot-related. Naturally, you don’t sh*t where you eat, so I didn’t use my main. It wouldn’t be hard to connect the two accounts though. Not sure what information they can get – but it is a different CC, but ultimately it links to the same address. I use my wife’s name on one FFXIV account and mine on the other. However, there is a clear “trail” to my account by way of mail or trades. Sometimes I tried to make it look “legit” as if it was an exchange of services, but when 99% of what the botted character did benefits my account, it wouldn’t be hard.

I was not banned on my main. However, I’m wary. Miqobot not working might be a good thing for me – from a self-centered stand point.

However, I will say – take the advice of others. Don’t be stupid about how you use it.

[tkinParticipant]

This will make me resub. So kudos to you for sharing with the community and for helping Miqobot developers get some more money from me 😛

[tkinParticipant]

Great script. At i620ish, takes about 20 minutes. Few tips I’d like to share:

– unbind some of your alt/shift chat keybinds (like say, alliance,etc). Sometimes the inputs for movement and ability usage cross and the bot winds up entering text into the chat window and just halts

– add repair() to the script near the top (before the other key entries) and keep a few stacks of repair materials on you

– I find that on occasion the very first attempt to starting the dungeon fails (cursor doesn’t reach “join”). If I correct it that one time, it seems to work properly after that for hours

[tkinParticipant]

I wanted to say thanks for providing further updates. I haven’t gotten past 60 yet (don’t have much time these days). However, I found that many of the trap locations are covered. It makes things a bit safer using the grids you provided.

[tkinParticipant]

I jumped into floor 21 to check out how this works. Pretty impressive. It would be really something else when it gets more datapoints for the higher floors.

When it comes to adding more trap points, you wrote:

If you see a trap with the sight pomander: run into it first – (deal with potential dangers)
Once you ran into a trap, Miqo has marked that position with a white circle and a name like trap…

Does that mean the bot auto-marks it on its own somehow?

[tkinParticipant]

So, it was interesting in that it mostly operated how I expected. It managed to handle Player 1 popping the dungeon (I put a short wait on player 2, so it wouldn’t hit “squadron(1)” until the window was already open on their screen. Two tanks in a zone – both using the “tank path” or whatever. It was like having a shadow following me around, except I was doing double damage essentially. It ran _very_ well until one of the last pulls. Then it was like tank #2 would simply run through enemies that tank #1 already pulled.

I just wish I understood the logic of how it worked.

I wasn’t expecting this to be a supported feature. But it seems like it is probably just one defect away from working for a use case that wasn’t even anticipated. Fairly robust code.

[tkinParticipant]

Follow-up:

That was it. Running seamlessly now. It is all about knowing what to look for – and I didn’t know what to search for. Thanks, Lyfox.

[tkinParticipant]

That’s probably exactly what I’m looking for. Thanks for (likely) resolving my problem!

[tkinParticipant]

I made a rough keyboard-only macro to farm a tiny spot in a loop, mostly for exp. It was all keyboard presses and in-game macros. It has no brains for error control and has 1 “pixel read” to keep it going. If I learned one thing from making this… is I miss Miqobot. However, absence makes the heart grow fonder.

[Author]

Posts