Magitek - All In One - Still going strong!

I will look into this later today or tomorrow. For now, make sure your pull range in the job settings is set to < 13.

 

Turn off targeting, Fate Bot handles all the getting targets so the auto target feature in Magitek could be interfering.

 

I had my pull settings set to 3 because in the low-level fate areas, it would stand in the range to use Piercing Talon but since it isn't available at that level it didn't move.

Thanks, I'll give this a try!

 

It might just be me but i was using Magitek with order bot yesterday on my 30 smn and all he did was spam ruin. Is the build for smn not setup for under 50 or is there something i need to do.

Thanks

 

Can you post a log?

 

Updated : Temporary fix for Scholar switching cleric stance on and off for no reason. This profile needs a bunch of modification. Might be a while.

 

You need to adjust the settings for Use DOTs Above HP in the job settings. If the enemy has less HP than what is listed in those boxes, all it will do is cast ruin. They are defaulted to settings that work pretty well for level 50 parties doing dungeons, not low levels doing FATEs.

 

Are bard songs working for anyone with the new update? Mine seem to get interrupted during the cast by other abilities.

 

Updated : Fixed so the combat routine can be interrupted again since the cancast change in the latest update. Spells will now only be queued 50ms before they're available instead of 500, giving you a window to manually cast your own.

Also, the combat routine will no longer cancel spells that you are currently casting. If this screws up any other classes, let me know, but I think it should make most perform better.

 

Thank you very much, that's a lifesaver. If Magitek gets broken I'm not sure I have much reason to keep using RB. Not looking forward to the possibility of 2.4 making everything unusable.

 

Hitting CTRL to switch WAR to dps mode doesn't seem to do anything for me, and it never seems to use Maim.

 

For Monks, is it possible to change the priority to maintaining Greased Lightning 3 instead of DOTS?

ATM, when Greased Lightning and Dots are both about to run out, it will cast DOT skills like Demolish and resulting in the GL3 running out.

 

just started up on WHM and its erroring out to be hell. did same when i tried fishing.
attached WHM log.

View attachment 3692 2014-10-04 03.46.txt

 

Food again. Either put the food you are trying to use in the first slot in your inventory or just turn it off. Still waiting on Mastahg to fix messed up items. Magitek has nothing to do with fishing.

Edit: Actually, should be fixed now. Restart reborn buddy to download the newest version.

 

Code:

                    //   If we're below 38 it means we don't have Blizzard III, we need to Transpose when we get below our setting.
                    new Decorator(r => Core.Player.ClassLevel < 38, new PrioritySelector(
                    Casting.Cast(r => "Transpose", r => HasAnyAstral && Core.Player.CurrentManaPercent < WindowSettings.BlackMageBlizzardIIIMana, r => Core.Player, r => 2, r => false))));

The bot won't use Blizzard 1 if it has any Astral buff because Transpose is supposed to switch back to Fire once it hits the right about of mana. However, there's no setting for "BlackMageBlizzardIIIMana" like the bot is looking for.

Pretty sure this is why the bot just stands there and casts nothing after the initial fire set, pre 38

 

i removed repair plugin and the gourmet as well and its working fine.

 

wrong work "Swiftcast+raise".
swiftcast -> heal. how to fix it?

 

When I worked on the profile I only altered settings for the level 50 spells (Flare/Fire 3/Blizz 3/etc.) so it shouldn't have affected lower level functionality (at least that's what I was trying to avoid). BlackMageBlizzardIIIMana is the mana % you set in the job settings. I renamed the window text to "Use Fire Until" but it still calls the code for BlackMageBlizzardIIIMana.

The profile is set to call Transpose first and then Blizzard. So it should Transpose and then keep casting Blizzard until it's happy then switch back to casting Fire. Both seem to be coded correctly, so I'm not sure why it wouldn't be working.

Code:

//   If we're below 38 it means we don't have Blizzard III, we need to Transpose when we get below our setting.
new Decorator(r => Core.Player.ClassLevel < 38, new PrioritySelector(
	Casting.Cast(r => "Transpose", r => HasAnyAstral && Core.Player.CurrentManaPercent < WindowSettings.BlackMageBlizzardIIIMana, r => Core.Player, r => 2, r => false))));

new Decorator(r => Core.Player.ClassLevel < 38, 
	new PrioritySelector(
	//   Blizzard we have no Astral or Umbral (we must have just used Blizzard when we had Astral), then keep using it till we're at least 80% mana.
	Casting.Cast(r => "Blizzard", r => (HasAnyUmbral && Core.Player.CurrentManaPercent < 80) || (!HasAnyUmbral && !HasAnyAstral && Core.Player.CurrentManaPercent < 80), r => Core.Player.CurrentTarget, r => 2, r => false),
                  
	//   Blizzard if we drop below specified mana, we should then Blizzard again to get Umbral Ice
	Casting.Cast(r => "Blizzard", r => Core.Player.CurrentManaPercent < WindowSettings.BlackMageBlizzardIIIMana, r => Core.Player.CurrentTarget, r => 2, r => false))));

Have you tried increasing/decreasing the % in your settings?

 

Fixed. The toggle wasn't really implemented so if you were in toggle mode it was just always stuck on DPS rotation all the time. Now pressing control will toggle between DPS and threat modes, and if toggle is off it will switch between the two to put up buffs/debuffs and stuff.

 

I don't really know enough about Monks right now to know how to handle this. I tried testing and from the back and the side it keeps up GL3 just fine, but when attacking from the front, it just seems to keep doing bootshine and I don't know what rotation it should be doing instead. Some input would help with this.