Forum Replies Created
August 20, 2019 at 4:15 pm in reply to: Asking the community: Thoughts on Open World Combat and User Protection #16801
I honestly don’t think MSQ features should even be added, it feels like a lot of work for so little payoff (at least for the average miqobot user); and if they are added, they should definitely be limited to a single instance.
If people want an alt, they’ll only use it once, so it’s wasted dev time. If they want to pump out a lot of alts, they’re probably trying to sell gil and that feels like such a minority (I could be wrong) that I don’t think it’s worth prioritizing features for them.
Also, if legit gil sellers (not people trying to make a couple of bucks) start using this program to pump out characters, you will be drawing unwanted attention, mainly because they won’t care about being discreet, since they don’t actually give a shit about the account, they just want to make gil to sell; judging by the PvP kill switch, you guys don’t want negative attention.
As for my opinion on future features:
1) While trusts should definitely be next up, they’re just a band-aid fix. What we really need is mesh grids, so the players themselves can automate any dungeon they want. Imagine if every time an expansion dropped the devs had to create gathering grids for every single node. So what we really need is “scenarios” for dungeons with mesh grids.
2) Vendor interactions, hopefully something that lets you interact with a nearby vendor by name, then list an item in its inventory, along with how many of it you want to buy.
3) Lvl 80 rotations. I realize that unless you’re a physical ranged dps/tank, rotation optimization will never be good enough to net you a 90% parse, simply because for the remaining jobs the rotation isn’t really the hard part, it’s doing the rotation while dealing with movement, and in the case of healers, CD usage changes fight by fight, so the bot will never be optimal in savage content. Still, I don’t want to get carpal tunnel syndrome so it’d be nice to have combat rotations to use outside of savage.
Also on a somewhat unrelated sidenote:
If people get banned and complain, literally laugh in their face. I’ve seen so many idiots use this program. It took me 1 run of the aetherflow scenario to realize that that shit was not safe. On the marjoram step, the grid flies into a tree trunk and stealth walks 20+ feet to the node. The chances of a player doing that is 0%. I could go to the marjoram node next time it spawns and over the course of 10 minutes find over a dozen people using miqobot. Now I know unless you yourself are using Miqobot you probably won’t know what’s going on right away, but I’m not risking even having a fellow miqobot user know I’m botting. Some people are assholes, what if another botter reports me because they want to reduce competition? I can guarantee you that has happened.
July 25, 2019 at 8:11 pm in reply to: [Scenario] Gatherer Scrip Farming (Yellow/Leveling + White) #15866
- This reply was modified 2 months, 3 weeks ago by AirForceOne.
I’ve been using the scenario for a while with no issues, but today it stopped working all of a sudden. When it teleports to any location, it moves to the start of the navigation grid but then it completely stops, and eventually the kill switch triggers. Literally nothing has changed between yesterday and today, aside from me changing some keybindings around, but that shouldn’t be a problem since I’m not getting an error with “no key assigned to x”, the only error I’m getting before the kill switch is the “I got lost in the woods” one. Anyone run into something similar/know what the problem could be?
EDIT: The problem was the keybinds. I had “move camera” set to shift+f keys, and that wasn’t working, but the bot wasn’t saying there was a keybind issue. Changed them back to just f keys without the shift modifier and now it works normally.
Also does anyone know if there are plans to let users create their own dungeon scenarios eventually? Seeing how incredibly easy creating grids with miqobot is, I feel like if we had the ability to do things along the lines of
if casting(x, y)
implementing dungeon scenarios ourselves would be incredibly easy, since once those functions are available the rest of it would just be busywork, and nothing is better to get busywork done than throwing a bunch of people at it in the form of everyone here willing to give it a shot.
- This reply was modified 3 months, 3 weeks ago by AirForceOne.
I’d still advice you not step away while botting for the next week or so in case a GM tries to verify that you aren’t botting. I don’t think a single report is enough to warrant action from SE but no one really knows, so better safe than sorry, especially if you’re like me and have put in thousands of hours of your own time into your character.
I’ve been botting exessively for the past 3 months, but what I do is the following: any botting that requires my character to be outside in the world (i.e. gathering) I only do while I’m at the computer. I also have a chat tab that only shows emotes, whispers, and /say so that if anyone tries to talk to me I never miss it. And then while I’m away/sleeping, I either run squadrons or craft at the inn/squadron barracks. Nothing has happened so far and sometimes I’ve been online without AFKing for over 100 hours straight.
As for the small servers comment from rem, I’d be wary, smaller servers have less people but those people tend to be a lot more casual and friendly, so they’re more likely to try talking to you imo. I’m in (…) and I honestly cannot remember the last time someone even tried talking to me while gathering/doing fates etc.
- This reply was modified 3 months, 3 weeks ago by Miqobot. Reason: Please be careful about your server
Just based off of how they work, I’d pick a ranged physical DPS, since their rotations can be done while moving and they’re relatively easy so it shouldn’t be hard for devs to implement an optimal rotation. Of the 3 MCH and BRD have the least amount of utility, so I’d say they’re both pretty safe bets, leaning more towards MCH if the rotation is implemented optimally. I’d stay away from dancer since they have the most utility out of all 3, so people might ask you to hold off on certain abilities, which atm the bot cannot do.
If I were you I’d avoid melee and casters altogether, since the bot has no way of knowing when movement will be required, so it might use CD’s right before you have to move out/away, which would ring some warning bells that you’re either terrible at the game or using a rotation bot.
You can use that same macro but meld only CP to max it using VI materia and that way you can sneak in a “Reuse” before the final synthesis. Buying it all would only cost around 100k, and on top of that removing VI’s as long as they aren’t used for advanced melding (which you don’t have to, don’t meld anything but CP) is guaranteed to succeed, so you can get them back to resell or reuse for the next set of gear.
I looked into beacons like you told me and figured it out. The problem seems to be that the nodes were too far away for miqobot to know which were up. So I just added beacons in between each of the hubs and now it works fine without compass, and I can skip the ephemeral like you said by excluding its name from the list. Thanks a lot for the help. Might post it if no one has made a cotton boll grid yet, it works beautifully, 100% looks like a player gathering.
Ok now it is gathering when it’s right in front. Can’t remember what the error was last time but I must have changed something that made it work. Now though, I get “(10:36:52 PM) Scanning for shiny gathering nodes like ‘Lv80 Lush Vegetation’ *.*” after it finishes a “hub”, it doesn’t move to the next set of nodes even though there is a path in the grid and the overlay shows that it’s recognizing where the next nodes are.
Using deliverGCGear(), no. It will turn everything in until it caps, then will turn in 2 more and then finish. So if you have 20 items, and cap on the 15th, it will still turn in 2 more, so it’ll stop at 17/20. What you can do is create the turn in scenario on your own using sendKey(), and then determine how many times it runs using one of the repeat commands.
Yeah I’ve been using it to get everything to 61 and this is by far the best botting program I’ve ever used, although I’ve only used 3. Still, holy shit this goes above and beyond the other 2. I was just checking if there was a faster way before starting the grind, although maybe I’ll just wait for HoH functionality to be implemented and see how that works out since there’s still plenty of time before ShB.