[PAID] [Mage] Portal - An Advanced Honorbuddy Mage Routine [PvE/PvP]

How you guys perform with Mythic+ currently? *Piep* isn't well on Mythic+ however it is stronger on Bosses :X

So I looking for a alternate for Mythic+

 

So last update really fucked up the dps. Could you reroll it or fix it somehow?

Also, can you add an if statement to check if Combustion is active for Ice Barrier. I don't think anyone wants the cr to use Ice Barrier during Combustion no matter what. Currently it is set to use Ice Barrier at x% hp if that matters.

 

Hi,friend

You can change the option to Low hp

And set 30%hp

That's good for raid.

 

That's a DPS loss. There's almost no reason to use LB single target.

Should be fixed as of the 5th Oct update.

Haven't got around to PvP stuff yet. No support for PvP talents atm.

Use the hotkeys in Enyo/Raidbot etc to pause the CR.

 

You should be using the cooldowns hotkey to toggle holding cooldowns like RoP and combustion. When cooldowns are disabled it wont use them - i.e. maybe the last trash pull before a boss for instance you'd disable them, and re-enable at boss.

I've made a few RoP changes for the next build though;

- [All] Rune of Power will now cast on trash pulls, but only when we have (nearly) 2 charges, and there will be a unit alive for at least 15 seconds.
- Will no longer cast RoP when moving (i.e. when Ice Floes active).

Post a log file please. The last build has a sequence cast to ensure we cast RoP -> Combustion for max uptime.

RoP having no conditions other than on cooldown or on bosses makes tuning the rest of the rotation around it very difficult - because it's impossible to make it pool for other cooldowns like combustion. You can toggle when to hold RoP using the cooldown hotkey.

I'll be allowing more configurable options for interrupts in future, but it's fine as it is at the moment. It's been this way for years.

I'd maybe try disabling manual cast pause - and disable plugin pulsing option in Enyo.

 

Thanks bud, manual cast pause sorted it

 

A new public build has been pushed to the store, and is currently awaiting approval from the Bossland GmbH staff. This can take up to 3 business days.

[11/Oct/2016 - Alpha]
- Will no longer cast RoP when moving (i.e. when Ice Floes active).
- [Fire] Will now use Flame On during trash pulls - outside of the Combustion cycle.
- [Fire] Flame On will forcefully be used when burst mode enabled.
- [Fire] Further tuning to Rune of Power usage.
- [All] Rune of Power will now cast on trash pulls, but only when we have (nearly) 2 charges, and there will be a unit alive for at least 15 seconds.
- Will now only use conjured food to recover instead of any food in the bags.

 

I just bought your CR, it took about 30 minutes for it to recognize that I bought it and it wouldn't show up in my choices for CR. Just wanted to give a heads up to anyone who has this issue. Don't freak out, it just takes time for your accounts to sync.

 

Hi,
the new release it's up and i tested the new one on raid dummy in class hall. With the last release i did 174k over 5 min, now i am down to 158k. This is verry disapointing. This is a loss of 16k. Former KingWoW was the lower routine with about 8k less (166k) but now it makes about 12k more (170k).

My second test up to 100m damage was:

Portal: 157K
KWoW: 169,5K

 

I experienced similar issues in raid last night but the most "latest" update has not been pushed out to users yet from the store.

We are waiting on
[11/Oct/2016 - Alpha]
[h=5]not Version: [05/Oct/2016 - Alpha] (10/6/2016 6:00:24 AM)[/h]

 

My changelog tells me:

[11/Oct/2016 - Alpha]
- Will no longer cast RoP when moving (i.e. when Ice Floes active).
- [Fire] Will now use Flame On during trash pulls - outside of the Combustion cycle.
- [Fire] Flame On will forcefully be used when burst mode enabled.
- [Fire] Further tuning to Rune of Power usage.
- [All] Rune of Power will now cast on trash pulls, but only when we have (nearly) 2 charges, and there will be a unit alive for at least 15 seconds.
- Will now only use conjured food to recover instead of any food in the bags.

means for me the new version is running. I forgot to say this tests was as Fire Mage. Now i tested the Arcane Mage and it was 190k.

 

Sometimes after blinking.. it goes haywire bc the target needs to be in front. then starts trying to correct itself by turning the character the Opposite way of where it needs to face.. it eventually fixes itself if it doesnt die first.. looks very botty though.. I'm just on free trial, watched it for a few hours. deff gonna buy it



edit for that-- the setting was blink in any direction.. i switched it to forward and works fine. hasnt glitched out yet

 

Thanks for the comparison test - however raw figures don't show the full picture. I don't have KingWoW's routine, but he may be controlling things Portal isn't - like Time Warp, multi-target padding etc.

I've just ran a comparison of my toon in simcraft (with a profile edited slightly to reflect real world scenario) vs in game over 5 minutes.

SimCraft = 107.6k DPS
Portal = 118k DPS

This was a purely single target fight without buffs, flasks, time warp etc.

Do you have any of TuanHA's routines installed? If so remove them from your routine folder, reload HB, and try again. His rotations are causing issues with all other routines at the moment.

 

Hi

I'm completely new to combat routines (and the Mage class). I've mainly used HB for levelling and gathering etc.

I just wanted to ask if there was a certain item / stats level the toon needs to reach before they achieve decent DPS?

I realise this may be an issue with class knowledge (or lackthereof) on my part but I'm struggling to put out anywhere near good DPS in dungeons and LFR.

I guess what I'm asking is, will I see more benefit of buying / using this routine once I hit certain a certain stat range such as 50%+ crit.

 

For simple increase the dps and prevent cast FlameOn to early ( its happen often ), please add this pseudo code to your current logic.
*
bool CastFlameOn()
{
** *if (CombustionCD > 45000)
** *** *goto Jumphere;
** *
** *if (CombustionCD < 45000) // 45000-55000
** *** *return false;
** *
** *Jumphere:
** *// Your logic
** *
** *return true;
}

 

Hi, ic ould send you the logfiles of both tests so you can compare.

 

That wouldn't work with Kindling. Besides, your code is really, really ugly.

Code:

bool CastFlameOn()
{
    if (CombustionCD < 45000)
        return false;

    // Do code here

    return true;
}

 

Icy Veins and Altered Time are both great websites to read up on for stat weights etc.

Sure, go for it.

The logic behind Flame On is as follows;

- Don't cast if we dont have the talent
- Don't cast if we have any charges of Fire Blast
- Don't cast if cooldown hotkey disabled

- If Burst hotkey active
- If we have Combustion active
- If there isn't an encounter active (boss fight) and a unit will survive for more than 15 seconds.
- If Combustion will be on cooldown for more than 40 seconds (or 65s with Kindling).
- If Combustion is on cooldown, the target is a boss, and it'll die before Combustion cooldown will expire (i.e. execute phase).

I'll add some debug logging for Flame On so it's easier to see why it's being used.

 

i cant seem to use this routine with studio60 to do dailies, anyone having similar issues ? what options should i disable when using questing profiles ? like movement or targetting etc, any advice would help ty, atm it just stands stationary randomly at times and dosent do anything,

 

Make sure movement, targeting, and facing are enabled.