Forum Replies Created
-
Posts
-
Don’t worry AR1416. You cannot delete your own posts, and you can only edit your posts for a certain amount of time (I believe it’s 15 minutes or so). Posting several times back to back after the timer runs out isn’t a problem.
Scanning for shiny gathering nodes like ‘
‘ *.*
usually means, that Miqobot cannot see any nodes nearby. Make sure, that you have all Arbor Call/Lay of the Land/Truth of the … abilities on your hotbar.The easiest way to get in contact with the Miqobot Dev Team is via E-mail through the support form:
https://miqobot.com/#supportAlso, the Miqobot Dev Team reads posts here on the forums as well.
Just used Miqo on the ship for the first time and instantly got my shark mount 🙂
@sefirosukuraudo: Did you have all the necessary skills on a normal hotbar (not a gamepad cross-hotbar) with keybinds set to every key?
This is impossible, because once you enter a PvP-Area Miqobot will activate its Kill-Switch.
Miqobot will not operate and prevent all functionality during PvP content and the devs will not implement PvP functionality for the following reason, as stated by the Miqobot Dev-Team themselves:
We are very sorry, but Miqobot does not support any PvP activities.
She will immediately trigger an integrated kill switch upon entering a PvP zone.Please note that PvP activities are extremely dangerous for botting due to high player congestion.
There is a very high risk of being reported by another player in PvP. And it will most likely result in account suspension.It is true that PvP grinding would be relatively easy to implement with Scenario Engine, and it would drive a lot of attraction to Miqobot.
But at the same time it would trigger much hatred from players who prefer to grind Frontlines manually. They would most likely take it as a personal insult and initiate witch hunting, which could potentially lead to a schism in the game community and significant damage to the game itself.We care about our players very much, and we would not want Miqobot to become a tool for game destruction.
We sincerely apologize, but at this time we have to postpone all PvP features requests.
edgedy’s solution however does work. It did in Eureka and it works in any instanced content, as staying in the HUD-layout screen counts as non-stop activity in the game’s programming, so please use this method instead. Miqobot however will not support PvP activities.
Easy.
setCraftRecipe(Elm Lumber)
startCrafting(50)
setCraftRecipe(Walnut Lumber)
startCrafting(50)
setCraftRecipe(Sandteak Lumber)
startCrafting(50)You will need the mats for it, but this will craft all the items you listed. If you don’t have the mats, you might need to additionally download a grid for each mat and create additional operations before crafting, like:
teleport( Location where your first mat is )
job( The job that can gather the mat, abbreviated as either BTN or MIN )
waypoint ( any waypoint on the grid )
startGathering(13) //13 because every node has a minimum of 4 items, giving you more than 50 matsDo that for every mat and then put this line before your crafting stuff:
job( the job for your craft, like CRP for carpenter )
Just a suggestion, what possibly might have happened:
Apparently there was recently an automatic update for Windows 10, which messed a lot with Windows Defender’s security settings. Several of my programs, like XIVQuickLauncher, Teamcraft and also Miqobot were somehow removed from my whitelist and I had to relist them as exceptions + give them permissions manually again.
Maybe everyone who seems to have issues should check up on their WinDefender settings, if anything happened there.
There isn’t, but I have a workaround for you:
Create an ingame macro with only the following line and put it on your hotbar./shutdownThe following scenario code piece should close the game. Place it at any point you want the game to shut down.
sendKey( Your Macro's Hotkey ) sendKey( Move Cursor/Target Cursor Left Key ) sendKey( Move Cursor/Target Cursor Left Key ) sendKey( Confirm Key )You just have to change the keys to your keybinds and you’re good to go.
What the /shutdown macro does should be obvious: It opens the exit game window. Then the second line of the macro tries to press the menu navigation left key, but it only spawns the cursor, which normally isn’t displayed by default. Then it presses the key again to move the cursor left to the confirm button and then presses confirm, essentially logging you out of the game.
In case for some reason in your scenario the cursor is already visible when it tries to press the shutdown macro, just remove one of the move cursor lines.
