Forum Replies Created
-
Posts
-
Miqobot is fixed for Patch 4.5!
All active license codes are automatically extended with bonus time.
Thank you for your patience and unceasing support!But apart from that, I’ve noticed a few issues with myself and the assist feature. I don’t know if that was just a problem on my system, but here are the things:
1. Once I started using the assist feature, the game started to get lag-spikes every 5 or so seconds, where the game freezes for about half a second
2. Tried using the assist feature in Eureka and somehow Miqo isn’t quite responsive, when it comes to attacking. Often times I had to do the first attack after selecting the enemy (with double right click confirmation), before Miqo started to do anything and often after evading AoEs I had to kick Miqo in the butt with another attack so she resumed the fightThis behavior usually indicates that there is a third-party application interfering with the game and Miqobot performance.
We can try to diagnose your issue, but we will require more information.- What jobs have you tried in Assist Mode?
- What settings have you enabled on Combat tab?
- Please try disabling some or all of the settings. Does it make any difference in performance?
- What draw method do you use for 3D Radar: Overlay or Always on Top? Does switching to another one make any difference?
- Do you experience this problem with any other high FPS feature (Squadron Dungeons, Minion Square Minigames), while using the same Miqobot version?
- Please show us a complete message log from the Output Area. (Starting from “Hello! I am your Miqobot!”.)
The main reason I suggested it was it appeared that because my target had switched off the tank to the enemy, it healed my character rather than the tank.
We would kindly ask you to verify if this is indeed the case when the new version is released.
Miqobot performs several confirmations after acquiring a target lock and before casting a healing spell. Please refer to the battle log to verify who exactly received healing and whether that character was not selected at the start of the cast.If the behavior you describe is true, it means that there is a bug in confirmation algorithm and changing target uptime will not fix it.
The secondary benefit would be you could cast buffs on the tank such as Eye For an Eye, Divine Bension, or whatever.
Keeping the focus on healing target would not help with Eye for an Eye or Divine Benison, because the healing target may not always be the tank.
For example, if a DPS stepped into an AoE and received extra damage, Miqobot will acquire the target lock on him and you won’t be able to cast protection on tank anyway.Perhaps a different system is required, wherein Miqobot would allow you to switch and keep the target lock independently until you decide to release it yourself. We will try to experiment with your request in the future upgrades.
I personally think it would be great to give an option to turn on or off (in a tick box maybe) and then switch the healer roles from.. priority: Heal secondary: attack/dots/etc OR priority: attack/dots/etc secondary: Heal. The reason for giving the option is that everyone plays the healer either 2 ways.. like what the quote says (placing fighting over healing, which is stupid if you ask me for 55+ content) OR placing healing first over damaging.
Having a tick box to alternate code on/off (depending on the player) I think would be a much easier option and easier to program maybe..? Thinking about it.. wouldnt the “placing battle over heals” already be implemented with the assisted battles? so you could use that code (or some of the code) and some how implement it into a “healer class user option” for dungeons tick box.
This option is already implemented.
If you would like Miqobot to DPS as top priority, please disable “Heals and Buffs” setting.
If you would like Miqobot to heal as top priority, please enable “Heals and Buffs” setting.
If you would like Miqobot to focus on healing only, please enable “Heals and Buffs” and do not target an enemy.The original question was not about priorities, but about where to keep the target lock when there is nothing else to do.
For example, during cast there are no other actions available other than wait until the cast ends. As the spell destination target is locked after beginning of the cast, keeping the target focused is not required for the duration of the cast.
Therefore healing module releases the target lock and the control is given to DPS module. If at the end of the cast the healing target requires more healing, the target lock will be immediately reacquired.
So the request was about keeping the target lock on healing target indefinitely, even when are no healing actions available.
(Please correct us if we misunderstood the task.)As to how much healing is done exactly, it has to be adjusted via a special customization UI which will be available in the future updates.
And you will be able to create different variation presets between “DPS-as-priority” and “Heal-as-priority”.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!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.
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.
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.Miqobot v1.3.18
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)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.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 AssistAny ETA on the next Squadron Dungeon? What is the next dungeon planned?
Next dungeon planned is from 50-60 level tier.
Miqobot v1.3.17
Starlight rhythm minigame is supported.
New scenario functions are implemented.
Full documentation is available directly in Miqobot. Press?button to open it.- npcStarlight() – Perform the starlight rhythm minigame at the closest NPC.
- setStarlightReward() – Set reward pattern for the starlight rhythm minigame. Default is 3.
- setStarlightAim() – Set performance aim for the starlight rhythm minigame. Default is great.
- npcQuestStart() – Accept a quest from the closest NPC.
- 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.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!
