Forum Replies Created
-
AuthorPosts
-
Lots of crystal farming when I sleep.It’s going to suck not being able to use the bot to turn in coffee biscuits. But oh well, still I hope the developers are safe.
Please don’t tell me you’re actually still doing coffee biscuits in endwalker instead of turning in Endwalker leves. please oh god.
Yeah, but to be fair the first boss in 71 does mechanics that cover the entire arena several times in row, whereas the first couple bosses spread out their mechanics so you can eat one or two without dying, especially if you slide in a mitigation skill here and there. With the 81 dungeon specifically
The Heroes’ Gauntlet awards 50 poetics per run currently, that would be your best bet for farming poetics with trusts. Keep in mind, this is an incredibly slow way to farm poetics in general, and so would paglthan. 20 dungeon runs of paglthan would be upwards of 10 hours to get to poetics cap, and Heroes Gauntlet would require around 20 hours.
Leveling dungeons would add literally 0 functionality to the bot, am I being stupid for thinking that’s just a straight up fact that’s not up for debate?
Adding a level 90 dungeon also adds zero functionality to the bot. The addition of the 81 dungeon is for longevity. We only will be farming aphorism for the duration of Endwalker, but the 81 dungeon to level alt jobs will remain a useful function for the lifetime of Miqo.
Your take also blatantly ignores any new users interested in using the bot, in favor of opportunistically benefitting on a temporary currency. Aphorism is also widely available through relatively effortless means. We have hunt trains running all day every day that get you capped on aphorism extremely quickly.
Personally, I would rather see the quality of life changes that have been constantly on the list for a long time that always get pushed to the back as miqo attempts to keep up with the content drip and remain relevant. But if I were to choose between the 81 dungeon and the 90 dungeon, it would definitely be the 81 dungeon.
You’re going to have to accept that light farming with miqo will be ‘suboptimal’ compared to running Haukke Manor manually. However, you can use the squadron combat assist in Sohm Al after entering into the dungeon unsynced and farm light completely afk.
Here’s my scenario
`Attachments:
You must be logged in to view attached files.You have to add the repair function to your hotbar if you’re using dark matter.
job(YOUR JOB HERE) solverPreset(recommended) recipe(COPY PASTE THE EXPERT RECIPE HERE) key(alt+=, 5.0) //food, make sure you have alt+= keybound or whatever key you want, and put the food on your hot bar key(alt+8, 5.0) //tea same as above (this is for 30 minute lasting crafting syrup/tea whatever) workFor(00:12:30) craft(max) key(alt+8, 5.0) //tea--add double slashed at the beginning of the line if you don't want to use tea workFor(00:12:30) craft(max) repair() repeatChapterFor(00:80:00)
edit: Forgot to add materia extraction. Do this on a second chapter if you want to extract at the end of crafting for 80 minutes
startMateriaExtraction()
Make sure the Materia Extraction icon is on your hotbar, and the slot that it is in has a keybind so Miqo can use it.
- This reply was modified 3 years, 7 months ago by Much Thicc.
I really appreciate the time you took to respond and clarify as well as answer some questions I’ve had.
Funny enough, even after you’ve described this, I still don’t see how Miqo isn’t capable identifying the names of dialogue options as its presented to the player, because what I would assume is that at some point the actual text in any given menu that is displayed to the player would be detectable by Miqo in some form right? Also to be clear, I’m not referring to Miqo actually ‘reading’ the screen. I’m suggesting that at some point the text, such as ‘Limsa Lominsa’ in the teleport menu, exists somewhere in the data that Miqo takes from the game.
I understand collectibles is a difficult menuing UI to cover, but a better example would be teleportation. How is Miqo able to identify ‘Limsa Lominsa’, or even better, something like ‘The Crystarium’ which is pages and pages down the menu, if Miqo isn’t simply ‘searching’ for the term within the teleportation menu? Correct me if I’m wrong, and I’m sure that I am, but how it seems to operate is similar to using a search function here on the forums or anywhere else, really. My input is ‘The Crystarium’, and Miqo then uses the menuing keybinds to scroll down the teleport list until it reaches a matched query.
If the above actually functioned the way I described, that’s pretty much what I’m suggesting, just for any menu.
So for example, lets say I want to go to my apartment. In the scenario, I would write the keybinds to actually go to the front door of the apartment building and open the menu, but then use optionSelect(‘Go to your apartment.’), then Miqo, similar to the way I assume menuing through teleportation works, would go to that dialogue option.
I know that might sound redundant, but there’s tons of elaborate scenarios where bad server ping happening even once throws off the entire menuing process. It would make menuing more precise, on top of potentially being faster overall (as opposed to manually typing every keybind for menuing, along with pauses)
I only have a loose understanding of programming but I’m curious what’s stopping you from creating an internal index of dialogue options once the command is reached in the scenario, then miqo searching internally for the text populated from the data collected based on the menu that’s currently open.
I guess I see what you mean considering how many different dialogue boxes there are, but given the limited number of actual commands it takes to get to any one selection, and in general there are broad menu options that could be included in tandem commands like an accept() function, I feel like I’m missing a key part of how the program works in terms of the actual data miqo is looking at at any given moment
-
AuthorPosts