[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.

[tkinParticipant]

I wound up taking that macro above and tying it in with another script to not-so-robustly loop around part of the island. It isn’t pretty though. The bottom line is… it doesn’t know which way is north. And camera angles throw it off. Looking forward to when the bot is updated, whenever that is 🙂

However, it was a lick-and-a-promise type script. When it works it is great. When it doesn’t, it is pretty bad. Not my proudest moment.

• This reply was modified 1 year, 8 months ago by  tkin.

[tkinParticipant]

alxrite wrote:

I just use a macro on my keyboard and a macro in game to get this done. Been gathering for hours on end with no help. Rank 9 and still going! I use a Logitech G815. I can show a pic of my macro on the keyboard and show you where to start if you want.

I’d be curious how you did it. I have a coding background with various scripting tools. The only limitation I’ve had is pathing on a map. I’ve used other bots in the past just for pathing while my script did all the work on top of the pathing tool. If you managed it with just an external macro coupled with an in-game macro, I’m sure people would love you to share.

[tkinParticipant]

I suppose I’m a bit surprised it would be a big undertaking. The nodes appear to be static. They are targetable. Mind you, I’m no pro at Miqobot. I used it for a few things here and there, but gathering was not one of them. I suppose I don’t see why a grid wouldn’t be possible. The islands are all the same. The node positions are all the same. How is that much different than nodes in the normal zones? Not all spawn points are up at all times. If anything, it would appear to be easier.

Of course, the underlying code might be far more complicated than a regular user (such as myself!) would understand. But, just wandering around my island, it appears that targeting nodes works just like regular gathering would. Only difference is now flying, which probably just means we’d need waypoints that are fairly precise to get to certain areas.

[tkinParticipant]

I’m receiving frequent error messages when running the BTN w/ collectable turn-in that says it should “spam the compass less often” or something. At which point, it AFKs out of Diadem but the bot continues to try and gather (“looking for shinies! in the log).

What should I be changing?

[tkinParticipant]

I ran it once – mostly came out with Fairies and Ashfish worth 4 to 8 points. I did have some sculptors worth 250 each. Is that what the goal was?

[tkinParticipant]

Sfia wrote:

What is the difference between 6.1.1 and the 6.1 that you linked five days ago?

Can you elaborate on the manipulation? I think I get it, but i’m not entirely sure.

Should I just start from whatever chapter matches the weather?

Also, what type of fish is the goal?

[tkinParticipant]

So I initially didn’t use the Universal one here. There aspects about it I didn’t like. I used someone else’s grid/scenario and tried tailoring it for Botany. But frankly, it would fail too often to make it worthwhile. And that’s ok. Maybe it worked for them. Not for me.

I’m looking for just Skyward points. Exp and gil doesn’t matter. Just care about the points. I wound up coming back to the scenario posted in this thread. I pretty much cut out the stuff that looks suspicious and seemed to be problematic to me.

I got rid of the chapters that deal with “DiademBoom” – which I guess is using the Augur. Considering it flies out of its way to use it, it seemed inefficient to me. I got rid of the “repairNPC” step at the beginning. I can repair my own gear. Running off to that NPC looks suspicious. I also got rid of the “turn in collectables” part. That doesn’t buy me anything. If my inventory is filling up, turning it in doesn’t help me. I also changed the “num0” to target NPC to start Diadem. I found it was unreliable on a good day. I essentially mapped “target nearest NPC or object” to a key and then used that in place of num0 for the step that targets the NPC. The key thing is that by removing the “DiademBoom” chapters, it still takes 30 minutes to complete the other chapter between. Which means that Return is back up again by that point.

Mind you, some of this stuff could have been left in. But, I’m tailoring it for my needs and this is working much better.

I commonly start the scenario when I begin telework (yay for being doubly productive!). My other script, I was having to check on it every 30 minutes. It was uncommon for it to make it the full 3 hours and then put me back in Diadem to repeat it. But with the Universal script, it pretty much just runs and runs.

[Author]

Posts