Forum Replies Created
-
AuthorPosts
-
The reason it takes time is because it’s gonna be sophisticated.
I’m really really hoping to be able to do something important, playing with 2 XIV accounts at the same time, one with an healer alt entirely controlled by Miqobot, and one with me on my main DPS, so I can “duo” plenty of things, like for example farming Aquapolis entirely alone.
There are plenty of interesting things in this game to “duo” like this when you have a dedicated healer at your disposal 24/7.
I only use French one. If it’s too much trouble, don’t bother, I’ll add new lines when I find them.
Also, if I want to force my “NQ” crafting preset directly into the Pre-Requisite Crafting part of your script (often I don’t need the Pre-Requisite ones to be HQ), and at the same time force Collectibles off at the beginning for when I forget to turn it off in Crafting tab, would this work:
miqo += "//Pre-Requisite Crafting\r\n"; miqo += "solverPreset(NQ)\r\nnqhq(balanced)\r\nreclaimOff()\r\ncraftCollect(off)\r\n\r\n"
I’ve been using your script every day since weeks now and I forgot to stop by and say: thank you Lyfox.
For a different language than English, there’s some recipes I need to adjust and add a “,2” or “,3”, but once I identified them I got used to fix them before launching the scenario.
I suppose I could add a line like this:
miqo = miqo.replace(/recipe\(Laine peignée\)/g, "recipe(Laine peignée, 2)");
Or should I do differently?
Very useful script for some painful achievements.
- This reply was modified 7 years, 2 months ago by Carl Arbogast.
This bot is totally safe to use if you respect a couple of conditions:
1. Never ever mention the bot in any kind of chat in game, that means even in /tell, do not talk about the bot inside the game. Because that’s how GM can find in your history logs on their servers that you mentioned you’re botting, and it’s enough for them to give you a warning. That’s one of the 2 things they can use against you, they really have only 2 weapons, they cannot use anything else, no screenshots, nothing from outside the game.
2. Don’t be stupid and don’t set up the bot to farm the same thing for longer than a human could/would do, for example, do not set the bot for playing a Gold Saucer game for more than 4 hours. A good rule of thumb, since you have the scenario feature, make the bot change activities often, like every 2-3 hours. Don’t run it in total for more than 12 hours a day, because their second weapon is to find out you ran the same activity for a super long impossible time, no one can play Out of a limb for too long, don’t give them any clue, anything that could lead them to suspect you, use the bot like a real person with lots of free time would do, no more. That means no more than 8-12 hours/day, and change activity often, and log off for the night.
3. Do not let the bot unattended, you must be ready to answer a tell. Have it run in the background, turn off music and some other stuff, but let system sound on, you must be able to hear a tell, or a specific LS chat or FC chat.
If someone reported you (it’s super rare and very unlikely if you respect the above advices), a GM can check on you, you must be ready to answer the GM within 5 min.
The bot only required 15 FPS (except for Chocobo racing and Out of a limb), so you can run FFXIV along another game with no performance issue on a modern computer, so run it only when you can answer /tell or other in-game solicitations.If you respect all this, you won’t have any problem. People have been using safe bots (no hack, no injections) on FFXIV since 2010 with no problem at all for 7 years by using the bots smartly. Square Enix doesn’t care, as long you are discreet, you don’t brag, you don’t mess with players, with the market, with real money or the game. Be smart.
Are you sure you gave a proper key bind for everything required? You might want to check this:
If you have your crafter classes high enough, use the Scenario Engine feature to tell the bot to repair after x amount of time.
For example:
Chapter 1:
teleport(name_of_teleport_destination) changeJob(name_of_gathering_class) selectGatherPreset(gather_preset_name_that_include_my_grid)
Chapter 2:
workFor(02:00) StartGathering() teleport(name_of_teleport_destination) dismount() repair() repeatChapter(4)
You need to have the repair icon on your hotbar with a keybind set.
The grid you’ll use must be connected to an Aetheryte, since you can’t repair mid air, and it’s not safe to dismount randomly anywhere, teleporting to the aetheryte, then dismount there and repair is a safe choice.
With this example, the bot will work for 2 hours (real time), and it will repeat the chapter 2 four times.It’s just an example, there’s plenty of ways to handle it with Scenario Engine.
FFXIV > Keybind > Target tab > Bind a key to Target the closest NPC.
You might want to check this also:
July 25, 2017 at 4:17 pm in reply to: [Crafting]: Place less weighting on Byregot finishers as HQ approaches 95% #4694If I don’t say any mistakes, this behaviour was implemented to decrease immensely the time taken by the solver to solve a craft, Miqobot ignores the quality max number, and considers it as infinite and therefore try to reach the maximum quality possible, and only stop the craft when she can not increase it any more.
I believe that the time you would win by doing it differently would be lost by having the solver taking dozens of minutes to solve the craft that way. -
AuthorPosts