[LyfoxParticipant]

First of all dont be afraid to experiment. Click ? button it has documentation for every function. Choose one read about it and try playing with it on a blank scenario.

The basic guide is here: https://miqobot.com/forum/forums/topic/beta-scenario-scripting-engine/
But imo the easiest way to learn is to experiment.

[LyfoxParticipant]

This is awesome guys thanks for sharing.
Heres explanation of your issue with failing to input keys:

Miqobot wrote:

You can use sendKey() function to make a sequence of commands which will imitate behaviour.
But you will have to stop using mouse or minimize the game window, as explained here:
Miqobot v1.2.4 – Known Issues

Miqobot wrote:

Known Issues

• An issue wherein Miqobot would fail to move a game cursor, under extensive mouse movement.
  Unfortunately, this can not be fixed without code injections, and we have no plans for implementing code injections.
  Miqobot is aware of this situation, and she will patiently wait for mouse to stop moving before making another attempt. She needs a small fraction of a second (about 0.25 sec) in order to recover from this issue. Under normal circumstances you wouldn’t even notice this behaviour.
  If you want to prevent this behaviour completely, please consider switching the game to Windowed mode and minimizing it, when you run Miqobot in the background. Thus, mouse cursor will not be able to run over the game’s window and will not interfere.

Thats why we like when Miqo devs add new functions for scenarios which previously required imitation. They implement a constant feedback loop which verifies every action and make everything very stable.

So basically if you use sendKey() for UI interaction – dont touch your game.

[LyfoxParticipant]

What do you mean? Theres no movement before afking in these scenarios. At least not in 61/63. It goes to node only after it spawns.
If you want to navigate beforehand you have to add waypoint() commands before afkUntil().

[LyfoxParticipant]

All right here it is.
The file has two scenarios one for Chromite, one for Spring Water like you asked. Choose the one you need, select the chapter matching current time and start. Dont forget its 24-hour format.
I didnt bother with cordials because 2 Eorzea hours are enough to regenerate 700+ GP. Assuming youve unlocked Enhanced GP regeneration from job quest of course.

Attachments:

You must be logged in to view attached files.

[LyfoxParticipant]

Its an easy request but a little ambiguous. You cant gather Chromite Ore and Spring Water at the same time because they are in the same node. So what will it be?

[LyfoxParticipant]

It seems youre having a different issue. It would be nice if you could show a message log or at least a screenshot like Rynzvl did. As of now i can only guess. Does the node appear on screen or is it obstructed by a stone? Do you have all keybinds assigned and not in conflict with each other? Do you have your camera tilted too high? Try moving a waypoint further away from the node does it help?

[LyfoxParticipant]

craftCollect(on) enables a setting on Miqo crafting tab. Collectable synthesis will be used during actual crafting. So you have to start crafting to make it work.

craftCollect(on)
craft()

[LyfoxParticipant]

workUntil(09:00)
It doesnt work with server time only LT and ET but it shouldnt be a problem. Check documentation under ? button.

[LyfoxParticipant]

Hmm maybe your Truth icon is not accessible then. What keybind is it assigned to? What does Miqo say in the message log when she starts gathering?

[LyfoxParticipant]

Maybe youre launching them from gathering tab? Scenarios are on scenario tab. You dont have to check use truth, scenario will do that automatically.

[LyfoxParticipant]

Miqobot wrote:

Recommended settings for 2.5-star recipes:

• CP Chunks – 4:1 or 8:1.
• CPU Intensive – Ingenuity + Manipulation II.
  Innovation is not recommended anymore as it gives a very small quality boost.
• Progress First – enabled.
  A huge computational boost for only 1.8% loss of quality (0.2% when using Maker’s Mark).
• BB only 100% – enabled. Prevents bad RNG affecting your craft.
• PbP only 100% – enabled. Prevents bad RNG affecting your craft.
• Ignore Quality – disabled. Only for crafting furniture or emulating Quick Synthesis.
• Reclaim if HQ < ..% – depends on your preference.
• Reclaim if Q < …. – disabled. Only for collectables with specific requirements.

Recommended settings for all other recipes:

• CP Chunks – 8:1.
• CPU Intensive – all disabled.
• Progress First – enabled.

As @Carl Arbogast said correctly, Crafting Solver needs only a few seconds for good performance on anything below 70**.

But 360 CP is a little low. You should aim for 500+ CP with food if you want HQ.

[LyfoxParticipant]

Well this community has many active contributors. But i think everything that was needed is already created. It would be a pain if presets required constant modifications dont you think? Thats the whole point – you create a grid once and it works for years. Miqo team does an amazing job by supporting even the oldest grids. Theyve told us that even new navigation system will be 100% compatible with all presets ever made.
The problem with trial is very rare afaik. Their server is being constantly bombed by spammers/hackers but tech support is working non stop.

For the rest of your points i agree. Atm we are waiting for a new and shiny combat upgrade. And lots of QoL features are coming next. Look at sticky threads most relevant information is usually there.

[LyfoxParticipant]

It came out of nowhere because windows defender downloaded an update which introduced a new bug to its signature database. It can happen anytime.

[LyfoxParticipant]

Already discussed, false positive is a bug in antivirus. Official word here: https://miqobot.com/forum/forums/topic/miqobot-flagged-as-trojan-virus/

[LyfoxParticipant]

Eureka is pointless for botting. Why bother with getting yourself banned when you can just afk in NM train. Miqo shows NMs directly on your screen and imo its the only thing you need. A sound notification would be nice though.

[Author]

Posts