(10-06-2013, 08:43 AM)fxfire Wrote:  well for once, we were restarting our server stuff multiple times in the last 24h, each time you guys got kicked (results in ffx closing and sommeeetimes in a crash ;) )

Can you guys open always the BotStatus info when you bot and IF the screen goes gray, then you can at least see in what "task" the bot was in that moment. We need info on when it happens with more details. Because I'm running two bots like 24/7 here and have yet to see my first crash during normal grinding....

(10-07-2013, 04:01 AM)an0nym1z3r Wrote:  In case anyone is interested, I found a quick 'workaround' to automatically re-summon your pet in case of death while grinding.
1.) Start up ffxivminion. You MUST do this step first before modifying the ffxiv_helpers.lua file as the MD5 will be different and automatically overwrite the file if you do not.
2.) Open up ffxiv_helpers.lua in the LuaMods/ffxivminion folder with notepad/wordpad or any lua/text editor.
3.) Edit the GetNearestGrindAttackable to the following... Make sure to replace the 170 (which is the ID of Summon II) with the ID of the summon spell you wish to use.

Code:

function GetNearestGrindAttackable()
    local mypet = Player.pet
    if ( TableSize(mypet) > 0) then
        ml_debug("Name: ".. mypet.name)
    else
        ml_debug("Summoning pet")
        -- Cast Summon II for now
        local skill = ActionList:Get(170)
        if (skill ~= nil) then
            if (skill.cd == 0) then
                skill:Cast(0)
            end
        end
    end
    local level = Player.level
    local el = EntityList("nearest,alive,attackable,onmesh,minLevel="..tostring(level-1)..",maxlevel="..tostring(level+1))
    if ( el ) then
        local i,e = next(el)
        if (i~=nil and e~=nil) then
            return e
        end
    end
    ml_debug("GetNearestAttackable() failed with no entity found matching params")
    return nil
end

4.) Reload the code by going to 'Control' -> 'Reload Lua Modules'

Question for the devs. It looks like the intended way to do this would be to update the ffxiv_combat_arcanist.lua file appropriately and then add my own 'menu' item which would stop/start that script instead. Is this the intended approach?

(10-07-2013, 01:54 AM)Sully13 Wrote:  Been running FATE grinding most of the day so will now post my observations. I have been running the Western La Noscea mesh and added three grind markers. I was grinding fates with Max lvl of 22 and min lvl of 20. I set an evac point in Aleport on the mesh. Most of the time I did fates with grinding but set it to fate only for a while to test evac point.

1. I had no crashing problems the entire time. Bot ran very stable.
2. Evac worked perfectly. At one point I checked do only FATE and he would return to the evac point whenever a fate was not active, just like he should.
3. Seems to ignore the FATE level designations. He would continue to go to FATES that were more than 5 levels below the min setting. That would not be so bad except for the next problem.
4. I can't find a way to activate the level synchronization when he goes to a fate which is more than 5 levels below. The synch window pops up and, unless I manually clicked on the synch level button, he just tries to attack and gets the error he is too high a level for the fate. If I click the synch button his level is adjusted and everything happens as it should. There is good xp to be had from doing fates that require level synchronization so I hope there will be a way to address this problem, especially since the min level doesn't seem to be working.
5. Several times during the day the bot would move to a fate or a grind spot and just stand there and do nothing. When he was just standing like that the task was always MOVETOPOS. Several times I let it go like that for several minutes to see if he would ever activate again, but he never did. If I moved him with the keyboard he would start moving again or attacking if mobs were around but that was the only way he would recover. I observed this happening at fate locations as well as grind spots and it happened a good 6 to 9 times over a 2 to 3 hour period.

6. I am running a lvl 20 Thaumaturge with a fairly simple skill manager profile. When playing manually I use the following attack rotation:
fire, fire, fire, transpose, blizzard blizzard (at this point the mob is usually dead). This rotations takes advantage of Astral Fire and Ice and conserves MP so I never run out, but the transpose is an important part as it converts the astral fire to ice and vice versa. I haven't been able to figure out how to get the skill manager to perform this rotation, especially using transpose at the proper time. As a result, my dps and mp usage is very sub-optimal when botting. If anyone knows how to do this please educate me.

That's it. I think mmominion is doing quite well considering it is only day 2 of the beta. Great job and hopefully some of my observation will be helpful.

Sully