Forum Replies Created
-
Posts
-
2. With the increased amount of players utilizing Miqobot, more people have reported their bans to the official Miqobot tech-support. Most of these do not engage into discussions here on the forums.
Well TOO BAD! I doubt that an official ban report topic would turn away new potential users (every botter knows that he’s at ban risk every day), but at least we could learn from eachother’s mistakes if we knew what led to ban (too much grind per day? GM checks? player tells? what exactly do they tell? just simply too much gil sold? sold which way? etc)
Now, to the point. An opinion of someone who stopped to renew licences because of lack of features needed:
1) Open world grinding is ok (most of us grind the open world, just we grind mats rather than mobs), MSQ support is not. First, as you’ve said, there is another bot for that; second and most important – it would require INSANE amount of time to implement (because there is a lot of quests, and w/o teleport hack it would need covering whole zones with grids). I can just repeat what I’ve always said: forget hi-effort tasks, go for “low effort, high impact”. It shouldn’t be that hard to buy a jump potion, or to buy complete account if someone is that desperate.2) Don’t start any monitoring – it makes AV software alert, and generally it’s just a bad habit (we’ve got enough of this crap from M$ side already). Multiboxing is personal decision and personal risk (and, indeed, nobody should get refunds because of bans).
Do you have all the grids on one scenario and set them to run at specific times with teleports and stuff included?
This. Go to grids subforum and download some example – it should probably provide some insight.
How can I change the rotation on this? On average, Single Mind > Utmost Caution > Impulsive x3 > Single mind > Impulsive will get you a lot more than the rotation this grid is using.
There is no point for any rotation to end with Impulsive – its buff goes to waste anyway. Methodical should always finish the rotation.
-
This reply was modified 4 years, 9 months ago by
Gray.
or desynth, the success rate will be 100%, the see-sawing when leveling multiple classes will be removed, and in general we want you to use desynth on your extra items more.
It will still take months of raiding / looting / desynth to compensate price of materials spent leveling desynth up to 450. Well, unless “success rate will be 100%” will apply to desynth of ilvl450 item with skill 1 (in which case nobody would have to ever level up desynth at all, and desynth level will become completely meaningless, though this won’t happen). So I guess desynth will stay as it is: useless for botters, barely useful for legit players.
Also, we’re thinking of making it so that gatherers won’t be detected by monsters when riding a mount.
Won’t help anyway. I mean, won’t help us botters. As long as there is at least a little chance that mobs detect our toons while just they are just dismounted but not yet stealthed, we will still move dismount/stealth point miles away to make sure our toons won’t wake us up in the middle of night with login screen cutscene sound (because char have died and disconnected due to afk). There is just a single thing which will help with aggro mobs, and it’s not some fleeing AI… it’s system which will restart scenario after char’s death depending on current time.
So I think conditions are:
Well duh! I just realized this group of nodes has its ephemeral node, just nobody cares to harvest it, so I didn’t even notice it before. So basically this is the same “backtrack here and there while ephemeral node is spawned” bug I reported before %) sorry!
it would make you seem less bot like if someone were watching
You would still do such a crapload of things “bot like” (for example, stopping at beacons / before going to stealth for some milliseconds, while human would move non-stop; dismounting via mount key before digging while human would auto-dismount by hitting a node; and so on), so if some GM actually decides to watch you for some time, then you are dead meat anyway – he won’t even have to contact you to make sure…
We have experimented with your grid and haven’t encountered anything unnatural.
Would you please clarify, which beacon does Miqobot backtrack to and under what conditions?From beacon 21 it observes and collects southwestern group of nodes, then proceeds to northwestern via beacon 22 and gathers two spawned nodes from the [0,1,4] set. After that it should proceed to beacon 18, but sometimes it backtracks to 22 after collecting either 1 or 4. I’m not really sure about conditions, but to me it seems that it happens when both nodes near waypoints 16 and 0 were spawned and collected w/o using beacon 22 as actual beacon (because node near waypoint 0 is directly visible from waypoint 16).
P.S. Never happens when node 14 is spawned (because it’s the last node Miqo visits, and no other nodes are visible from it, so beacon 22 is actually used as beacon). So I think conditions are: nodes 12, 16 and 0 are spawned.
I tend to reduct everything farmed during full “cycle” (Eorzean day) during the least useful of 6 4-hour “windows”, but there is a problem… amount gathered is random. So, if amount is low, my toon arrives to the next farm spot before its ephemeral node appears, gather(1) makes it try to gather the nearest common node, then it hangs up because there is nothing to gather into collectable, and effectively gets disconnected by anti-afk system. I can of course add something like afkUntil(4:00ET) – but then again, in case there is a lot of loot, this command can launch at, say, 4:05ET – which effectively makes my toon try to wait for the whole Eorzean day, which wastes time and leads to the same disconnection. So far I managed to find just a single workaround: I add afkFor(1:00ET) to make sure it arrives to the next place after 4:00ET (as it never takes less than 3 hours to reduct everything gathered), but this is still an ugly hack 🙁 Does somebody know a better workaround? The best would be to make my toon gather common nodes using the same ephemeral rotation until ephemeral node spawns (if he arrives before “window opens”, that is), but how to do it?
P.S. workUntil() followed by aetherialReduct() does not interrupt the latter when “deadline” comes, either.
-
This reply was modified 4 years, 9 months ago by Gray.
Of course, any additional information will help us identify the issue faster.
Ok, here goes. Other users might find it useful too (if you ignore backtrack issue) – it’s leveling BTN 56-60 with collectables on Birch place in Clouds.
It’s implemented in the current release. You can find the detailed explanation of the beacons rotation algorithm in your thread: <span class=”d4pbbc-underline” style=”text-decoration: underline;”>General gathering problem (HW/SB only)</span>
Then I have no idea why does it backtrack to a beacon just visited… I can attach the grid which produces this bug if that helps.
The current algorithm has no rule to move cursor. At each moment it evaluates the required gathering slot based on the current environment and settings. It does not have any memory of a previously gathered item. Therefore in order to address this issue, we will have to redesign this feature from the core.
Weird %) I’d just add a single variable to store number of last gathered slot (1-8), which is reset to zero once node is fully gathered. This way bot can perform GP check only in case variable holds 0 (i.e. we didn’t gather anything from the new node yet), otherwise it should stay on the last gathered slot unless it disappears (and then it shouldn’t perform GP check anyway – just take the next “no {} brackets / no rotation” item name from the list.
But oh well, you could have did it yourself already if it was that easy, hehe…
-
This reply was modified 4 years, 9 months ago by Gray.
This solution is already implemented. Please note that the beacon is only marked as visited when Miqobot flies directly through it. Alternative routes in close proximity do no count.
I’m sorry… any chance you clarify it a bit? Did you mean it’s implemented in the current release, and I’m just doing something wrong (what exactly)? Or that it’s implemented, but not released yet?
Yes, we are aware of this problem. The solution you proposed, however, will not work due to the existence of rare items which disappear from the node after one hit.
Hmmm why? If an item disappears – then you more “cursor” to another item; though, my idea is that you never move “cursor” because current amount of GPs changed (i.e. no GP checks except for before the very first hit)!
from what you said they kindda did me wrong ?
I wish there was a rule (much like on most other forums): when you file a ban report, answer at least minimal set of questions:
1) How many hours per day you were botting?
2) Did you use any proxy?
3) Did you have any accounts banned before, which were run on the same hardware (not Miqobot case [yet], probably)?
4) Did you sell any gil? How much?
and so on… Otherwise it’s kind of hard to guess. Leaving account unattended means nothing. I see several notorious bots at our server for months (they were botting already when I was n00bie, still leveling my skills), and they bot every day on the same place, so…RAAAA RAAAA shhhh GAME OVER! What got me banned was the Maelstorm Scenario.
Did you run it 24/7? Did you sell any gil?
I mean, I’ve sold more than 300 mil gil so far, and I wasn’t hit, not even a warning (knock-knock). But then again, I never run a single account for more than 12 hours a day.
-
This reply was modified 4 years, 9 months ago by
