Forum Replies Created
-
AuthorPosts
-
I vote AGAINST implementing Aurum Vale and postponing everything else.
My reason for this is, you can speedrun Aurum Vale with a party of 4 blue mages with specific skills in ~5 minutes. It’s pretty braindead, too. Last Treasure Trove, I was able to farm 100 tomes for the necklace in a short amount of time using this technique. Here is a video of a strategy similar to what my friends and I did. Completed in 4 minutes. (Not my video)
Also, I could see that Miqo devs were really struggling from the community pressure to get grade 4 expert supported. I was in favor of the recipes getting supported as soon as possible at that time, because the rankings season lasted 7 days, and Miqo devs (rightfully so) needed a 2 week break afterwards. Treasure Trove lasts March 15 to April 13, which is 29 days. What Miqo devs said above, “Working hours will be doubled. We will burn through the available resources twice faster,” that sounds like another burnout waiting to happen.
- This reply was modified 3 years, 8 months ago by jponry.
The Peeping Tom thing is a good idea. I should start doing that when going on a farm spree.
What do you use as a notification sound?
The default sound is what I use, it’s distinctive so I immediately know what it is 🙂
- This reply was modified 3 years, 9 months ago by jponry.
Miqo is my first bot so I was worried too. Years-old FF character and all with items, friends, FC… Even on longer botting sessions I have never been bothered; granted I am at my computer tabbed out with audio notifications for various chat channels and QuickLauncher plugin “Peeping Tom” (audio trigger when targeted by someone). Admittedly I have, at my own risk, left her unattended for short periods of time (less than 20m), but again I (thankfully) have not been bothered.
Just keep Miqo company and be smart 🙂
December 31, 2020 at 9:03 pm in reply to: A little early, but might be worth talking about the next expansion and miqo #25768Lately I’ve been thinking about the next expansion + what my personal endgame priorities will be. Here is what I could really use Miqo’s help on:
1. Crafting/gathering
– collectible support
– quick synthesis support2. Level 90 trust dungeon support (assuming that’s a thing)
– for tomestone farming, mainly for the purchase of tome crafting materials
– yes, I would prioritize this over 81 – 89 dungeons, I can bite the bullet and level my trusts to 90 by hand
– unless Miqodevs are able to implement level 81 and/or 85 at the same time3a. Automated collectible turn-in
3b. Automated scrip (+ tome?) exchange for specific items
– Since this involves navigating a couple sub-menus to get to the item purchase, perhaps a couple scenario engine commands to tell her what to press?4. Scenario Engine updates
– including the ability to call scenarios recursivelyThank you for all your hard work 🙂
December 31, 2020 at 12:44 am in reply to: Suggestion: Automatic interruption for unspoiled nodes #25721December 25, 2020 at 7:41 pm in reply to: Suggestion: Automatic interruption for unspoiled nodes #25630In my opinion a new Scenario function would be better. I already suggested (and some others have too) the possibility to call specific chapters in a scenario from within a scenario (basically like functions, you can call everytime and everywhere you want).
A variation of that with an function likehookTime()
would prove quite helpful not only in your case, but possibly in more cases like the old unspoiled nodes from Heavensward/Stormblood or others in the future aswell. The function would work like this:hookTime(Scenario-Unspoiled-Node-8AM, 08:00et) hookTime(Scenario-Unspoiled-Node-1PM, 13:00et) hookTime(Scenario-Unspoiled-Node-4PM, 16:00et) teleportIf(REGULAR NODE LOCATION) gatherPreset(PRESET) gather(999)
So it adds a condition which is periodically checked (like every second or so?) and once it matches a condition, the hook triggers the Scenario mentioned in the argument.
I actually like this idea better! Seems like it would be much more flexible and expand Scenario capabilities immensely 🙂
I was working on a scenario last night that involved navigating NPC menus via sendKey().
It’s very finicky. If a key gets skipped, it’s because Miqo tried to send it and the game was not able to respond (for example, the menu was loading). The default delay I use is 1.0, but for opening/closing menus I use anywhere from 2.0 – 3.5 depending on how long it takes the game to process the command. For scrolling through lots of items, or otherwise spamming a certain key, the delay I use is 0.5. Also, sending “esc” to close menus doesn’t seem to work at all unless FFXIV is in focus, so I set a secondary keybind for “Close all UI windows” or whatever it’s called and had Miqo send that instead.
My logic with choosing delays is to err on the side of caution, and choose a longer delay, because all it takes is one lag spike to completely mess up the scenario flow.Edit: When testing the scenario, you also need to make sure that menu navigation is in “cursor mode” as opposed to “mouse mode” (not actual names, just what I think of them as). If you move your mouse in-game, it will switch to “mouse mode” even if the last menu you nagivated was in “cursor mode”. This will mess up the menu navigation because the first key sent to the game (while in a menu) won’t do anything other than activate “cursor mode”.
- This reply was modified 3 years, 11 months ago by jponry.
October 22, 2020 at 11:48 pm in reply to: Scenario: Collectibles -> Slithersand – turn in & cash out script #24720 -
AuthorPosts