Magitek - All in One

Shame this is no longer being worked on. With this, I don't really have any use for Rebornbuddy any more.

 

I think most people fall in the same boat. Magitek has been abandoned, Kupo is still mostly unusable, and with Wheredidigo not releasing his Combat Routine until the Buddy Store is released for RebornBuddy (which could be months away) I think most people will start looking at other bots. Honestly the only other I know of that seems to have a decent reputation is FFXIVMinion (MMOMinion's bot), but I've never used any of their bots so I have no idea if they're any better/worse (although I do know most prefer their Hearthstone bot over Hearthbuddy, even with one of the Minion devs attempting to convert his Silverfish AI over from Minion to Buddy).

These are dark times for FFXIV botting.

 

I tried MMOminion's combat profiles a while back, sure they have alot of options and potential, but they really are not updated anymore sadly.

 

I've talked with Mastahg about RB implementing the Store and it's definitely a ways away....probably closer to 6-8 months with the way RB development gets prioritized. I am currently working on fleshing out the details of how my CR will work with RB. I'm currently testing my Bard CR with OrderBot using the 1-50 Grinding profile and I'm getting good results.

I will probably be releasing a CR for each individual Class/Job 1 at a time and they're probably going to cost $10 USD for a single class or a discounted price to buy all of them.

What I have so far is Archer/Bard....Lancer/Dragoon.....Pugilist/Monk. Those CR's have all the rotations done and optimized for a full 1-50 lvling experience.

I also have a lvl 50 only Routine for Summoner that I currently use to Raid with, and the Paladin Routine has been worked on....but it hasn't been tested very much.

I plan on finishing the Bard, then Monk, then Dragoon CR's first. Then I'll finish getting Arcanist/Summoner ready to be used in a full 1-50 manner, and then I'll do the BLM CR.

After the DPS CR's are done, I'll finish the Paladin CR and do the Warrior CR

After Tanking is done, I'll do the Scholar CR first, and then finally the WHM CR

Obviously this is a lot of work, but that's the plan that I have for it.

 

6-8 months? Wow!. Looking forward to your work. It will be a long road but it will be fun.

 

Just want to clarify that the 6-8 months was a guess of how long before BuddyStore is implemented in RB...with that being the case, I'm going to release my stuff before that.

 

I've already got some money set aside for the Archer/Bard CR. When you start working on SCH I'll definitely throw some money your way for that as well.

 

I've thought about attempting to repair Magitek in the meantime but I'm not well versed in C# (although I do have some history with C variants). If I ever get time I'll be looking it over but Where will probably go public before I ever make any progress lol.

 

Well... I spent a lot of time looking into Magitek itself, and reacquainting myself with Visual Studio and attempting to relearn what I could of C# (and investigating "TreeSharp").

Turns out, Magitek is working fine now. I didn't do anything, but ExCombatAssist and Fate Bot both seem to be working great. No complaints here.

With that said, since Magitek was working for the time being and since I already had everything setup; I decided to add a few features I felt were missing. Here's what I have so far (see if you can spot the additions).



It was pretty simple to add both of those to the rotation. Tomorrow I'll try tackling a tougher issue (integrating Flare into Magitek's AoE rotation). If I can get that sorted out I'll release what little I've done so far (BLM improvements).

 

Nice are those new check boxes on the buffs and abilities?

 

Yes, I've added Quelling Strikes and Virus to the beginning of the rotation (once Astral Fire III is up, and every time they're up after that during AF3).

The Flare rotation is going to be tricky because the logic wasn't correct to begin with (I've had it miscast Swiftcast/Convert when attempting to use the "Flare Single Target" toggle in the past). Once I correct the logic to use Swift > Flare > Convert properly I'll see about adding it to the AoE rotation. Then BLM will finally be on-par with the other Jobs in Magitek (I'm sure there are plenty of other tweaks to be made, but BLM always stood out to me as unfinished).

All credit still goes to Exmortem though. I'd never be able to create all of this from scratch. I'm just altering the code he left behind.

 

Thank you Endus.
I was loosing hope

 

When using Magitek with Fate Bot, it hangs when trying to initiate combat with the next mob. Issue isn't persistent with Kupo. There has to be something wrong with the initiating combat part of the code. This is with SCH specifically and BRD also has the same issue.

 

It's just not facing the target. On a Melee class Magitek works great.

 

Wow great work Endus, I'm really looking forward to your stuff!

It's definitely not easy, I myself dropped out from programming in school

 

Enable facing your target when using an action in your game settings.

 

Alright, so far all I've done is rebuild the BLM profile from the ground up. I haven't even attempted to remove any of what appears to be old code (for Spread Thunder and such) as it didn't interfere with my changes. I've still got a lot to learn so if any real Devs look it over and see any newb mistakes feel free to call me out lol.

Also, even though it works great for me, it might not for you. Let me know if any of you who try this notice anything odd/broken (especially lower-level functionality, although I tried my best to leave that intact).

Improvements
Single Target Flare works properly now (on cooldown and no glitches leaving you @ 0 MP)
Flare has been worked into the AoE rotation
Swiftcast used on cooldown (used for Fire/Fire2 when Convert for Flare isn't available)
Better MP management (more fires, no getting stuck @ low MP due to odd spell usage)
Smarter proc usage, including a more efficient Firestarter/Transpose mechanic
Added options for Quelling Strikes and Virus usage
Will only use Physick when MP is available (will cycle into Umbral to regen MP to continue healing rather than healing to no MP and sitting there)

[HR][/HR]

Notes For Proper Usage
If you're 50, it's important to set your "Fire Until MP%" setting correctly to obtain max DPS. Whatever % you set it to needs to make your MP come out to slightly below 969. Here's why:

969 (Player MP) - 638 (Fire1 MP cost in AF3) leaves 331 (Player MP) for emergency Blizzard3 (319 MP cost) should you drop both Astral/Umbral at low MP (due to raid mechanics or whatnot)

It's also needed for the rotation to function properly:

969 (Player MP) - 638 (Fire1 MP cost in AF3) leaves 331 (Player MP) - 79 (Blizzard3 MP cost in AF3) leaves 252 (Player MP) for Umbral filler spells which are Thunder (212 MP cost) before regen kicks in and Scathe (212 MP cost) after first regen tick but just before last tick (might add options for different filler spells later, as everyone's spell speed AKA MP regen is going to be different)

Basically, for me it's:

.263 (26.3%) * 3654 (MY MAX MP) = 961 (under the required 969) and 961 - 638 = 323 (above the required 319)

If you're not 50, for now just play with the setting until you feel it's in a good spot. As long as you don't set it to an extreme number (like 10% or 70%) it'll still work fine. I didn't add this feature, it was already in Magitek, I'm just explaining how to get the most out of it.

Also, if you ever experience the bot just standing there after combat, you might want to set your Rest Energy to 0 as BLM's don't need to rest with Umbral anyway.

[HR][/HR]

If everything goes well with this I might touch it up a little more and move onto another class (hopefully one not as complicated as BLM lol).

 

If you want a specific mana amount, why not that hardcode that number in the routine rather than having the player enter a % (and probably screw it up)?

 

Because everyone's MP will be different (depending on Piety and Level), so it makes percentages hard. If I just hardcode >319 and <969 then it will break the code for lower levels (MP costs scale as you level).

Getting the percentage incorrect won't break the profile, you just won't be doing max DPS. If you set the percentage too high it won't cast that last Fire1 @ 969, causing a loss in DPS. If you set the percentage too low you'll eventually run into a scenario where you can't Blizzard3 for Umbral Ice, causing you to have to Convert or cast Blizzard1 (if there's enough MP for that). Both are recoverable, they just aren't efficient/max DPS.

Although you do have a point, the less users have to think about the better.The feature was there to begin with so I just left it in/worked around it. Technically I could split the profile in half (one half for max DPS @ level 50, and the other half for leveling) There is also code to pull a player's MP and the current MP costs of spells, but that's only half the battle (then you have to do the math for EVERY level, to know where the "optimal" numbers are for them).

I'm just thinking out loud at this point though. I'll look into it.

 

Did that, still didn't fix the targeting hangups. Only thing that is working well are melee classes because I set those to have such a close range.

Fantastic work! I'll test this baby out today! All other classes I imagine won't be hard at all since the other classes work great with their rotations except for a few hiccups.

Only issue I constantly run into is targeting hangs. For any ranged class I have running any portion of the bot it hangs on targeting the next mob. I have it set to face target when casting skills which is the default setting, but the bot just doesn't cast until the mob is in front of it. No clue what's going on with that. Maybe there is a bit of code that could be implemented that makes the character face the target before attempting to pull.