Miqobot

Forum Replies Created

Viewing 15 posts - 1,951 through 1,965 (of 3,069 total)
  • Author
    Posts
  • in reply to: Patch 4.58 – Miqobot Status #10005
    Miqobot
    Miqobot
    Keymaster
    8+

    The recovery process is almost complete and we are currently at 90% milestone.
    New version of Miqobot will be available for download in 6 hours.

    in reply to: [Beta] Combat #9990
    Miqobot
    Miqobot
    Keymaster
    5+

    Yes, we have already planned a research of the new Doman Mahjong minigame and its algorithmic applications. But first we have to see whether it becomes popular enough to be a viable time investment.

    In the meantime, new Combat features will remain our topmost priorities.
    Thank you for your request!

    in reply to: [Beta] Combat #9981
    Miqobot
    Miqobot
    Keymaster
    2+

    However I did encounter some oddity’s when playing as WHM, I had “heals and buffs” & “allow switching targets” on. When switched from the monster to a target, unless the target player was below (what looked like 50%) assist wouldn’t heal them. But it wouldn’t let me lock back onto a monster until I manually healed the player to full. What ended up happening a lot of the time was that assist would DPS perfectly as WHM, then target the tank (at 75%) and do nothing.

    This also happened with raising dead players. Assist would target the dead person, cast swiftcast and do nothing.

    This behavior indicates that Miqobot wanted to activate a hotbar icon, but it was not accessible by keyboard. Judging from your description, Cure and Raise are the icons in question.
    Please follow our guide on Keybinds and Icons Recognition.

    We would also recommend looking at the message log when you encounter this behavior next time.

    EDIT: We were wrong.
    This is indeed a bug as it was identified after receiving more information. It will be addressed in the upcoming hotfix.
    Thank you for your assistance very much!

    • This reply was modified 7 years ago by Miqobot Miqobot.
    in reply to: [Beta] Combat #9980
    Miqobot
    Miqobot
    Keymaster
    3+

    Only messed around on WHM a bit so far but did note that it doesn’t Esuna Sludge from the Giant Tunnel Worm in Cutter’s Cry.

    Thank you very much!
    We will add Sludge to the list of important DoTs for Esuna.

    There were also a couple times where Miqo healed my character when it wasn’t necessary, might have been targeting back to Enemy too quickly or something.

    I will say she really likes to use Medica atm. Let’s the tank get a pretty damn low at times while topping off tiny amounts of damage on rest of the group.

    The healing thresholds may feel unstable at the moment, but since Miqobot can not predict incoming damage she has to compensate by keeping everyone healed with equal priorities. Sometimes it will lead to unnecessary overhealing and sometimes the damage will be too much to react in time. It’s impossible to balance without correct damage prediction, and this feature is still under research.

    But at the very least, when we implement settings for precise customization you will be able to adjust the healing thresholds to your liking.

    I wonder if it’d be too much trouble to make it so it switches targets only to damage rather than only to heal? Or just have that as an option. It would make using Eye For an Eye possible, currently, you’d have to pause or macro it. Very minor issues.

    We will try to experiment with this request, but most likely it would require implementing a completely different algorithm.
    The current system keeps DPS at the basis, and healing module is attached on top of it. Doing it the other way around is not an easy task.

    Before getting swiftcast, unfortunately, it would try hard casting raise while the tank was beaten to death a couple times. I just let it happen as it was a full party of sprouts so a couple wipes seemed appropriate for the “full experience” 🙂

    Please note that if you interrupt the Raise cast, it will not be reattempted for 15 seconds. You may use this behavior to control whether Miqobot should raise or do something else instead.

    in reply to: [Beta] Combat #9979
    Miqobot
    Miqobot
    Keymaster
    2+

    Thank you everyone for your feedback very much!

    is there any scenario support for this?

    Hi Miqo! Can this new assist be turned on via a scenario?

    We are sorry, Assist Mode is not designed for Scenario Engine. It requires user presense to control the character and select enemies in order to be functional.
    Scenario Engine can be integrated with autonomous features only.

    For scenarios we prepare another feature pack which will include Custom Fights and Monster Grind.
    It will be available at a later date.

    Notice it will not use Empyreal Arrow (lv54) Bard ability. Any plans to implement?

    Of course, as we mentioned we continue working on battle rotations and will be releasing incremental updates in the upcoming versions.

    It uses pitch perfect (52) and iron jaws (56) flawlessly as well as sidewinder(60)

    Just in case anyone is curious about end-game content use: RDM, WHM, and SCH all have their full 70 rotations in this release.

    Any 51+ abilities you may witness are not optimized. If you observe Miqobot carefully, you will notice many important details that are not evaluated. For example, on BRD the DoTs may accidentally fall off due to Iron Jaws not being timed correctly.
    Some 51+ abilities were implemented during our experiments with different mechanics, and it’s too much of a hassle to remove them from the source code for release. Since this is a beta version, it may contain unexpected features or work in progress.

    in reply to: [Beta] Combat #9948
    Miqobot
    Miqobot
    Keymaster
    6+

    Miqobot v1.3.18

    Download Miqobot Beta

    Assist mode is implemented.
    Please read the new guide section in the first post.

    – Assist Mode: Auto-pause is implemented.
    – Assist Mode: Toggle hotkey is implemented.
    – Assist Mode: Additional features can be enabled on UI.

    Battle rotations are optimized for levels 1-50.
    – Partial rotations are implemented for all levels, however some 51+ abilities may be used incorrectly or not used at all, so please do not expect the best performance at level 70 just yet. We continue working on battle rotations and will be releasing incremental updates in the upcoming versions.

    Important Note!
    Please remove any keybinds from “Reply” and “Switch Chat” actions.

    – You can find detailed explanation in the new guide section.

    Certain abilities require placement macro setup.
    – Rook Autoturret (MCH)
    – Bishop Autoturret (MCH)
    – Shadow Flare (ACN SMN SCH)

    in reply to: [Beta] Scenario Scripting Engine #9921
    Miqobot
    Miqobot
    Keymaster
    4+

    Using additional threads would imply parallel processing, while Crafting Solver is a strictly sequential algorithm.
    Solver states are sorted in a strictly determined order, and each subsequent state depends on previous calculations. Parallel processing would only make things worse and slow the algorithm down 100-200 times.

    We are very sorry to disappoint, but the Crafting Solver algorithm is already optimized as much as possible.
    Because of this optimization, its performance is equivalent to 100-200 threads of a parallel algorithm.

    in reply to: [Beta] Combat #9837
    Miqobot
    Miqobot
    Keymaster
    3+

    Any news or ETA on the next update and the combat assist? I’m pretty curious to see what the combat assist can do.

    We will try to make the initial release of Assist Mode before Patch 4.5.

    I’ve a question though, will be possibile to have some customization over the rotations or we’re gonna stick with miqo’s ones?

    Yes, of course. Additional customization options will be implemented as we move closer to complete level 70 support.
    You can find more information in this thread: Combat Assist

    Any ETA on the next Squadron Dungeon? What is the next dungeon planned?

    Next dungeon planned is from 50-60 level tier.

    in reply to: [Beta] Combat #9836
    Miqobot
    Miqobot
    Keymaster
    4+

    Miqobot v1.3.17

    Download Miqobot Beta

    Starlight rhythm minigame is supported.

    New scenario functions are implemented.
    Full documentation is available directly in Miqobot. Press ? button to open it.

    1. npcStarlight() – Perform the starlight rhythm minigame at the closest NPC.
    2. setStarlightReward() – Set reward pattern for the starlight rhythm minigame. Default is 3.
    3. setStarlightAim() – Set performance aim for the starlight rhythm minigame. Default is great.
    4. npcQuestStart() – Accept a quest from the closest NPC.
    5. npcQuestComplete() – Complete a quest at the closest NPC.

    Note: This is a bonus update for the ongoing Starlight Celebration event.
    New scenario functions allow farming the starlight minigame for unique housing rewards.

    The algorithm is by no means perfect and may accidentally miss some of the rhythm diamonds, but since the event is time limited we don’t think that perfection is required. In addition, performance aim is slightly randomized and additional settings allow you to control the randomization factor.

    • critical – Miqobot will try to align input perfectly with each diamond.
    • great – Miqobot will randomize input by hitting diamonds at Great or Critical.
    • good – Miqobot will randomize input by hitting diamonds at Good, Great, or Critical.

    Please be careful and try not to interrupt Miqobot’s performance with your own input, otherwise the inner pattern tracker may get out of sync and fail to complete the minigame.

    A critical issue is addressed.
    – Due to danger of pulling monsters from inaccessible areas and potentially causing a logic deadlock, Foe Requiem is removed from BRD rotation.

    in reply to: Collectable crafting issue #9789
    Miqobot
    Miqobot
    Keymaster
    0

    Yes, this is a known issue which happens for some unique combinations of crafting level, craftsmanship value, and recipe difficulty.
    It is described in details in our primary Crafting Guide.

    A temporary workaround is to slightly alter the input parameters, for example, temporarily remove Rapid Synthesis II from the hotbar.

    The issue is impossible to fix completely, because the true crafting formula is evaluated server-side and therefore is unknown. But we improve the internal formulae used by Miqobot with every new version based on the data our users provide.

    Would you please enable crafting logs in Miqobot and send us the output for analysis? The more data we have, the better algorithm will be in the next version.

    Thank you for your assistance very much!

    in reply to: Randomizing options #9777
    Miqobot
    Miqobot
    Keymaster
    1+

    At the moment we focus on implementing the core Combat features, but we will try to push some of QoL improvements into the next release.
    We apologize for inconvenience.

    in reply to: Trying to run gatherer grid but get this error output #9775
    Miqobot
    Miqobot
    Keymaster
    1+

    This particular issue is confirmed to be caused by using an outdated version of Miqobot.
    As the game changes with every patch, it is technically impossible to support old versions.

    Please use the latest Miqobot version which can be downloaded from our website.
    Thank you very much!

    in reply to: [Bug] Crafting solver time tracking incorrect #9617
    Miqobot
    Miqobot
    Keymaster
    3+

    We apologize, but we don’t see the bug.

    (14:40:23) Hitting Confirm button. :3
    (14:49:29) Solver DONE: 538876.463735178 ms

    The difference between timestamps is 9 min 6 sec.
    Reported solving time is 538,876 ms ≈ 539 sec = 8 min 59 sec.

    The mismatch of 7 seconds is the amount of time it took Miqobot to hit Confirm in the crafting log, wait for synthesis window to appear on the screen, and initiate the solving algorithm.

    On a side note, please note that Crafting Solver needs only a few seconds on anything below 70*** and 1-2 minutes on 70**** recipes.
    If you select any option that brings the computation time above 2 minutes, you increase the average HQ rate by 1-2% at best.

    in reply to: Trying to run gatherer grid but get this error output #9593
    Miqobot
    Miqobot
    Keymaster
    1+

    We have investigated your issue more closely.
    According to our logging system, you are using an outdated version of Miqobot.

    Do you see the following message in the Output Area?

    Look! There's a new version of me available: https://miqobot.com/#get-the-bot

    If so, please follow the link and download the latest version from our website.

    in reply to: Trying to run gatherer grid but get this error output #9592
    Miqobot
    Miqobot
    Keymaster
    0

    Would you please give us more information about your issue?
    Please show us a complete message log from the Output Area. (Starting from “Hello! I am your Miqobot!”)

    The more information we have, the faster we’ll be able to help you!

Viewing 15 posts - 1,951 through 1,965 (of 3,069 total)