Magitek - All in One

Should be fixed now on SVN.

This is fixed too, thanks.

 

The monk routine works best with combat assist because like you said, the bot doesn't reposition itself. Unfortunately it'll just use the basic combo when grinding or doing fates. If you're using Combat Assist then you manually go to the flank etc and it'll adjust its rotation.

 

Ah thank you. I think this is because I'm not familiar enough with the MNK rotation to know what the optimal place to be is at certain times. It's more difficult for a newcomer MNK as I don't know the best way to weave my combo/movements (since I don't know what abilities the bot will use next). Can any high level MNK shed light on how they use this routine?

Example: when buff1 is up, run behind target. When buff2 is up, switch to flank, etc.

 

The simplest rotation alternates between 3 moves flank and 3 moves rear. Its Flank(Dragon Kick > Twin Snakes > Snap Punch) > Rear(Bootshine > True Strike > Demolish). This will give you better dps than 90% of monks, but you'll be about 10% dps shy of optimal, because you're clipping Dragon Kick, Twin Snakes, and Demolish.
The best rotation isn't really a rotation, its more of a priority system especially once you add in downtime from dodging mechanics and such. Basically, in each form you have a high potency move with no extra effect (Bootshine, True Strike, Snap Punch), and a lower potency move that adds a buff or debuff (Dragon Kick, Twin Snakes, Demolish). You want to maximize uptime on your buffs and debuffs, without clipping them too much by reapplying too soon. Generally 3-5s is a good number; if the de/buff has less time than that refresh it, otherwise use the non-effect move and refresh it the next rotation. Picking which move to use is a matter of being in the right position at that time. Just fyi I can't do this personally outside of a training dummy, although I know some monks in my FC who can and they blow other dps out of the water.

Regarding non-rotation stuff, the most important thing for a monk is to keep Greased Lightning up. Losing a GL3 is a huge dps loss, and on that note I have a suggestion for the routine. Touch of Death, Fracture, and Haymaker aren't part of your forms combo, and in some cases can result in you losing GL by delaying your combo. Using any of these to start off is a dps loss as well, as it delays you getting into GL3. A condition like this would minimize the chances of this happening:

Code:

new Decorator(ret =>
                {
                    if (!Core.Player.HasAura("Greased Lightning III", true, msLeft: 10000))
                        return false;
                    return true;
                }, new PrioritySelector(      
                    Casting.Cast(r => "Haymaker", r => true, r => Core.Player.CurrentTarget, r => 2, r => true),        
                    Casting.Cast(r => "Touch of Death", r => !Core.Player.CurrentTarget.HasAura("Touch of Death", true), r => Core.Player.CurrentTarget, r => 2, r => true),      
                    Casting.Cast(r => "Fracture", r => WindowSettings.MonkUseFracture && !Core.Player.CurrentTarget.HasAura("Fracture", true), r => Core.Player.CurrentTarget, r => 2, r => true)
                    )),

although there might be a better way to implement it, and they would only cast one per rotation, and never cast for monks below level 40(?) who can only stack GL twice.

 

Exmortem, could I request that for the WHM job settings you add an option to stoneskin tank only (or tank classes, for raids when there's two tanks - I'm not sure how your tank detection works)?

While stoneskin for the whole group is useful, I'm finding more and more that it is easier to skip it on dps entirely, but this doesn't reduce the usefulness of it on the tank (I've been manually stoneskinning).

 

with the all basic classes routine, (pugilist) it used bootshine > true strike > snap punch on enemies if they were in front of you. I have noticed this does not happen with the monk profile. (i am level 34 currently) Is it possible at all to add it? (providing it doesn't mess it up somehow) The monk profile applies twin snakes and spams bootshine if the enemy is in front of you.

 

Hoping I'm not stepping on any toes, but try replacing the Monk.cs file in your magitek rotations folder with this: View attachment Monk.cs
Should solve the issue of attacking from the front as well as the one I mentioned above, although I didn't test it while level sync'd so can't make promises. There's several other tweaks I made to mine, but a grinding routine doesnt have the same requirements as a raid combat assist routine.

 

I mainly use magitek for dungeons and such, and leve's out in the open. How different is your modified profile compared to Ex's?

 

After griding more than half of my books and dailies I was trying to figure out how to get the bot to follow the party and then have the combat bot do it's DPS thing, but I can't seem to figure out how to do this outside of the fate bot running to fates. Is there anyone that can point me in the right direction as to how I can have it run through dungeons doing dps for me? I don't want to just walk away from the game entirely, but be able to study and keep an eye on it while it's doing the work basically.

Is the only way to accomplish this is to basically /follow someone and let the combat run itself? Not sure I would risk it in that case.

 

with all basic classes (archer) when the straighter shot buff is up, the bot doesn't seem to cast straight shot. (which would make it a crit)

 

Ah, I meant that the one I use personally has several addition tweaks, like manual Perfect Balance and AoE and some other stuff. The one I posted above just has the small changes of using your full rotation from the front and dotting only right after reapplying GL.

 

What is this used for? Sorry but I'm new to FF and considering buying the bot. Looking for something that can do quests to level all the classes to 50. If anyone can help out a newbie I'd appreciate it!

 

This is a combat routine. It's the 'logic' behind what ability to use, and when.

RB doesn't do quests yet, so if you've got storyline to do, you need to do it by hand, but it does do fate grinding, which is very good XP.

Download magitek and put it in your 'Routines' folder (and 'excombatassist' in your 'BotBases' folder - although you don't excombatassist for fate grinding, only for combat assist).

Find out the best zone for fates for your level and go there. Attune to the aetherite. Select the Fate Bot in the RB bot list and open up bot settings.

Select: When no fates are read: return to aetherite (or return to specified location, just don't forget to go to that location and click 'Set' in the option below it).
Set: Level requirements: enabled. Min level: The minimum FATE level it will grind (not your level). I usually set it to the lowest fate in zone that's within my level range. Quarrymill for example I set it to 19. Max Level: your level +X - X being whatever you set. So if you're 25 and you set max level to +5, it will do fates up to level 30. When you level up to 26, it will do fates up to 31, and so on.

Close fate bot settings, hit start, and it should start grinding out fates for you.

 

I have a request for a feature. Can we get the option to use Cleric Stance for SCH? I've got it cross skilled as it makes my DOTS hurt a lot more and it's really nice for soloing or doing fates on my own.

 

Good news, it's already in. Enabled Solo Mode under the Healing Manager.

 

Awesome. Very nice. Would it happen to start using Bane too?

 

hello mate, since the latest update it doesnt seem to be registering in the bot. any ideas?

 

After updating Magitek routines with SVN, I'm not able to use them.
Here is the log file:

[10:16:17.221 N] Currently a level 50 WhiteMage
[10:16:17.224 D] Reloading AssemblyLoader<ff14bot.AClasses.BotBase> - Initializing
[10:16:17.307 D] Poi: Type: None |
[10:16:17.721 D] [BotManager] Botbases have been reloaded.
[10:16:17.722 D] Ex Combat Assist v0.0.0.0
[10:16:17.722 D] Combat Assist v1.0.152.0
[10:16:17.722 D] Fate Bot v1.0.152.0
[10:16:17.722 D] PvP v1.0.152.0
[10:16:17.723 D] Fishing v1.0.152.0
[10:16:17.723 D] Grinding v1.0.152.0
[10:16:17.724 D] Gathering v1.0.152.0
[10:16:17.724 D] Order Bot v1.0.152.0
[10:16:17.732 D] Reloading AssemblyLoader<ff14bot.Interfaces.IBotPlugin> - Initializing
[10:16:18.022 D] Reloading AssemblyLoader<ff14bot.Interfaces.ICombatRoutine> - Initializing
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(69,107) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Deadtarget'.
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(69,179) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Deadtarget'.
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(69,269) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Deadtarget'.
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(187,154) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Deadtarget'.
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(187,226) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Deadtarget'.
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(235,70) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Eyeforaneyetarget'.
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(235,152) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Eyeforaneyetarget'.
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(187,316) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Deadtarget'.
[10:16:18.785 N] Compiler Error: d:\FF\Rebornbuddy 1.0.152.0\Routines\Magitek\Rotations\Summoner.cs(235,215) : error CS0117: 'Magitek.Helpers.PartyHelper' non contiene una definizione per 'Eyeforaneyetarget'.
[10:16:18.814 D] [RoutineManager] Routines have been reloaded. Current class-specific list:
[10:16:18.815 D] Kupo [ConjurerWhiteMage] v1.0.152.0
[10:16:18.816 N] Building Actioncache
[10:16:20.135 N] Action Name:Stone Action Id:119
[10:16:20.135 N] Action Name:Cure Action Id:120
[10:16:20.135 N] Action Name:Aero Action Id:121
[10:16:20.135 N] Action Name:Cleric Stance Action Id:122
[10:16:20.135 N] Action Namerotect Action Id:123
[10:16:20.135 N] Action Name:Medica Action Id:124
[10:16:20.135 N] Action Name:Raise Action Id:125
[10:16:20.135 N] Action Name:Esuna Action Id:126
[10:16:20.135 N] Action Name:Stone II Action Id:127
[10:16:20.135 N] Action Name:Repose Action Id:128
[10:16:20.135 N] Action Name:Stoneskin Action Id:129
[10:16:20.135 N] Action Name:Shroud of Saints Action Id:130
[10:16:20.135 N] Action Name:Cure III Action Id:131
[10:16:20.135 N] Action Name:Aero II Action Id:132
[10:16:20.135 N] Action Name:Medica II Action Id:133
[10:16:20.135 N] Action Name:Fluid Aura Action Id:134
[10:16:20.135 N] Action Name:Cure II Action Id:135
[10:16:20.135 N] Action Nameresence of Mind Action Id:136
[10:16:20.135 N] Action Name:Regen Action Id:137
[10:16:20.135 N] Action Nameivine Seal Action Id:138
[10:16:20.135 N] Action Name:Holy Action Id:139
[10:16:20.135 N] Action Name:Benediction Action Id:140
[10:16:20.135 N] Action Name:Virus Action Id:169
[10:16:20.135 N] Action Name:Blizzard II Action Id:146
[10:16:20.135 N] Action Name:Surecast Action Id:143
[10:16:20.135 N] Action Name:Swiftcast Action Id:150
[10:16:20.135 N] Action Name:Eye for an Eye Action Id:175
[10:16:20.135 N] Action Name:Fetter Ward Action Id:1565
[10:16:20.135 N] Action Nameurify Action Id:1584
[10:16:20.135 N] Done building Actioncache
[10:16:20.151 D] [RoutineManager] Routines have been reloaded. Current class-specific list:
[10:16:20.151 D] Kupo [ConjurerWhiteMage] v1.0.152.0
[10:16:20.151 N] Starting Kupo [ConjurerWhiteMage]
[10:16:20.155 N] Old context:None CurrentContext:Normal
[10:16:20.164 D] Replaced hook [Kupo.Combat] b11ceb89-e222-4691-a043-f5b746c37813
[10:16:20.165 D] Replaced hook [Kupo.Pull] de08dc6b-6267-4d6f-a7a1-db5b71b34490
[10:16:20.165 D] Replaced hook [Kupo.Rest] 69f8a195-9c7d-45af-bfeb-20a29d6e26c9
[10:16:20.166 D] Replaced hook [Kupo.CombatBuffs] 57eb1b8f-db22-45df-b0a0-151f21b35bd3
[10:16:20.166 D] Replaced hook [Kupo.Heal] c5e858be-de9f-4759-a2c3-a73579e06a10
[10:16:20.166 D] Replaced hook [Kupo.PreCombatBuffs] 51728954-b59d-4321-8bc0-25bf89e6e72f
[10:16:20.166 V] Verified behaviors can be created!
[10:16:20.166 N] Initialization complete!

 

Reupdate SVN.

 

I rewrote the group code, let me know if you run into issues.

Heal Alliance in the healing manager will allow Magitek to heal people outside of your party, if you notice a big FPS drop then disable this feature. Looking through all game objects and sorting which ones are healable causes the game to slow down. There's currently an issue where WHM esuna throws an object reference error, it's still dispelling but i'm looking into it.