Forum Replies Created
-
Posts
-
By using something else than the log, maybe you guys will be able to make triggers for those mechanics, within your custom scripts for specific encounters.
I would be interested in knowing if this was possible and it is really required for certain fights as you’ve said.
By required, I mean the bot cannot do many fights unless it can react to those ‘visual only’ mechanics…actually nearly every standard AoE effect in the game is like this…so they must have that covered.
Miqo, what I mean is more like storing the finished rotation and corresponding player stats. Data like:
Recipe:
70 dur, 1100 difficultyPlayer:
410 cp, 698 craft, 678 controlRotation:
Basic Touch, Steady Hand, Observe, etcI don’t see any need to store the proof of it, which I assume is what the 30+gb is. No need or benefit really, so long as its only stored if its generated by the bot…digital signature or some security method.
I think it makes sense at least?
/micon "Great Strides" /ac "Byregot's Brow" <me> /ac "Great Strides" <me>^ Off topic a bit, but this macro might help you too. If you were to get an excellent when you’d otherwise be popping great strides, it can really ruin your craft to use Byregot’s Blessing on Poor Quality. This will instead use Byregot’s Brow on any Excellent or Good quality. It is a small loss when its only a good, but for most applications it only removes the NQ’s since you’ll probably be over-killing the 100% anyway.
-
This reply was modified 7 years, 11 months ago by
Nott.
At the moment Crafting Solver requires about 22 hours of extensive calculations in order to solve a 60** recipe
Should the reduction of these times not pan out, could I recommend that Miqobot store these solved rotations in a database online? I realize gear is going to make this difficult. But what could be done is miqobot could check to see if the players gear is within a range where others are all getting the same recipe.
For example say player A first did the solver and player B with lower stats ran it later, received the same rotation. Both are now stored in the database when Player C comes along. He trys to run the solver but Miqobot sees his stats fall between the two, obviously he’d get the same rotation if he ran the solver, instead of waiting 10min-20min he could just click a button that says “Proceed with Community Recipe”…or some such.
There may be a level of risk involved, but everyone running the same computations seems wasteful to me…especially when you’d have to run it again everytime you change gear as well.
Raiding Bot, just like any other feature, will be implemented in parts.
Each AI upgrade will be an iterative improvement over the previous one.- First of all, we are going to implement a DPS Solver.
- Secondly, we will implement the ability to define an enemy priority list (a feature similar to Gather by Name).
- Thirdly, we are planning to upgrade the 3D Radar, so it will be able reflect the timing and phases of the current raid.
This sounds amazing. I just started up again today after a long break. Glad this is still going. I wanna say thanks to the Miqobot team and the community that is supporting them. Looking forward to seeing this stuff happen…both for just the science of it and for seeing if the computer thinks I’m doing shit right as far as dps goes, hah.
-
This reply was modified 7 years, 11 months ago by
