incenerate?

[Darkjello7769]

Is there a way to get the incenerate skill to keep going with mobs around or is this just not bottable?

 

[pushedx]

It's possible, but requires a routine with special logic to do it, which the current default one does not.

 

[Ontis]

It's possible, but requires a routine with special logic to do it, which the current default one does not.

Uh, what.
How can Incinerate logic could possibly be any different from Reave logic? Slap a max distance on it and we're good.
This is really depressing. I just made a decent farmbot character with 70% blockchance to avoid stupid deaths and I find out that nobody bothered supporting Incinerate skill in the routine. Seriously. What.

Oh and the tempest shield doesn't seem to work properly. Bot still keeps trying to cast that ability, abeit not for long. Maybe I am doing something wrong?

 

[raphaelpdc]

Any new about this ? I really want a routine to incinerate >_>

 

[ArdisX]

You can still bot with Incinerate, its still fine just not max dps. Botted with 3 incinerate chars pretty long till they got banned

 

[Ontis]

You can still bot with Incinerate, its still fine just not max dps. Botted with 3 incinerate chars pretty long till they got banned

No you can not. Bot refuses to cast Incinerate at all. My character keeps running into the fray and taking hits while doing nothing.

 

[ArdisX]

It works for me not sure, i just got normal thing set as skill and range 50. It will just keep clicking Incinerate. Enable the stand still while moving thing

 

[lyvewyre]

No you can not. Bot refuses to cast Incinerate at all. My character keeps running into the fray and taking hits while doing nothing.

I use incinerate extensively on mine. I set incinerate as my melee skill, to be used within 25. I have a ranged skill to be used up to 40 (flicker strike, as I am using consuming dark). Works perfectly for me, bot gets within range, burns what its targeting then flickers to anything not in range. Sure it doesn't stand there at stage 3 burning everything around it before moving on, but I'm putting out 30k dps at stage 1, everything dies in a blink of an eye anyway.

So.. if yours is refusing to cast, you need to review your setup for OldRoutine, otherwise fresh, fresh install, do not keep any settings, and then play around with OldRoutine till you get settings you like.

 

[Ontis]

I use incinerate extensively on mine. I set incinerate as my melee skill, to be used within 25. I have a ranged skill to be used up to 40 (flicker strike, as I am using consuming dark). Works perfectly for me, bot gets within range, burns what its targeting then flickers to anything not in range. Sure it doesn't stand there at stage 3 burning everything around it before moving on, but I'm putting out 30k dps at stage 1, everything dies in a blink of an eye anyway.

So.. if yours is refusing to cast, you need to review your setup for OldRoutine, otherwise fresh, fresh install, do not keep any settings, and then play around with OldRoutine till you get settings you like.

There are two major issues with Incinerate though. The first is Proximity shield affix rares. The second is the issue of way too high cast speed. Whenever OldRoutine is trying to burn a few single target enemies instead of crowded bunch, it throws off Incinerate pulses with tiny pauses between them... which are, however a major DPS loss compared to non-stop channeling AND an extremely obvious and dangerous behaviour. It's like painting a large sign above your head "YO DAWG I IS BOTTIN HERE HURR DURR", you know.

No, let me rephrase that so you won't ask typical questions.
Proximity shield issue CAN be fixed by setting melee range to short distance, yes, but in this case bot will simply use the same distance setting against ANY enemies, no matter what their positioning is. That ends up in the constant step-by-step movement while chasing any fleeing enemy, and by that we get our Incinerate stacks lost with every single small step. Such actions are also as obvious as they could possibly be.
I suppose the reason of this is that this routine deems Incinerate skill MELEE-ONLY. Even if we set Ranged range to 80 while setting Melee range to 15, this routine will keep facerunning into large monster packs instead of sniping them from afar. And if we set Melee to higher values in order to somehow compensate routine's stupidity, well, we immediately bump into Proximity shields.
So there's that.

 

[alcor75]

Open your OldRoutine.cs
select from line 1792 to line 1840, and replace it with:

if (OldRoutineSettings.Instance.AlwaysAttackInPlace)
                    aip = true;

                if (slot == -1)
                {
                    slot = OldRoutineSettings.Instance.FallbackSlot;
                    melee = true;
                }

                if (melee || cachedProxShield)
                {
                    var dist = LokiPoe.Me.Position.Distance(cachedPosition);
                    if (dist > OldRoutineSettings.Instance.MaxMeleeRange)
                    {
                        Log.InfoFormat("[Logic] Now moving towards {0} because [dist ({1}) > MaxMeleeRange ({2})]",
                            cachedPosition, dist, OldRoutineSettings.Instance.MaxMeleeRange);
                        LokiPoe.ProcessHookManager.ClearAllKeyStates();
                        if (!PlayerMover.MoveTowards(cachedPosition))
                        {
                            Log.ErrorFormat("[Logic] MoveTowards failed for {0}.", cachedPosition);
                        }
                        return true;
                    }
                }
                else
                {
                    var dist = LokiPoe.Me.Position.Distance(cachedPosition);
                    if (dist > OldRoutineSettings.Instance.MaxRangeRange)
                    {
                        Log.InfoFormat("[Logic] Now moving towards {0} because [dist ({1}) > MaxRangeRange ({2})]",
                            cachedPosition, dist, OldRoutineSettings.Instance.MaxRangeRange);
                        LokiPoe.ProcessHookManager.ClearAllKeyStates();
                        if (!PlayerMover.MoveTowards(cachedPosition))
                        {
                            Log.ErrorFormat("[Logic] MoveTowards failed for {0}.", cachedPosition);
                        }
                        return true;
                    }
                }

                await DisableAlwaysHiglight();
                var err = LokiPoe.InGameState.UseError.None;
                if (LokiPoe.InGameState.SkillBarPanel.Slot(slot).Name == "Incinerate")
                    err = LokiPoe.InGameState.SkillBarPanel.BeginUseAt(slot, true, targetPosition);
                else
                    err = LokiPoe.InGameState.SkillBarPanel.UseAt(slot, aip, targetPosition);
                if (err != LokiPoe.InGameState.UseError.None)
                {
                    Log.ErrorFormat("[Logic] UseAt returned {0}.", err);
                }

                return true;

Hope you can keep up with mana

P.S. MaxRangeRange most be considered what it is...Melee range, if you trick it to think 40 is a good meleerange, you are doomed. (the ProxShield logic consider you a smart person that set a melee range within 15/18, so that, if you fall in the ProxShield logic, it will move you within MaxMeleRange (15/18) even if you have no slot selected for melee, and so inside the shield.)

 

[Ontis]

Open your OldRoutine.cs
select from line 1792 to line 1840, and replace it with:

if (OldRoutineSettings.Instance.AlwaysAttackInPlace)
                    aip = true;

                if (slot == -1)
                {
                    slot = OldRoutineSettings.Instance.FallbackSlot;
                    melee = true;
                }

                if (melee || cachedProxShield)
                {
                    var dist = LokiPoe.Me.Position.Distance(cachedPosition);
                    if (dist > OldRoutineSettings.Instance.MaxMeleeRange)
                    {
                        Log.InfoFormat("[Logic] Now moving towards {0} because [dist ({1}) > MaxMeleeRange ({2})]",
                            cachedPosition, dist, OldRoutineSettings.Instance.MaxMeleeRange);
                        LokiPoe.ProcessHookManager.ClearAllKeyStates();
                        if (!PlayerMover.MoveTowards(cachedPosition))
                        {
                            Log.ErrorFormat("[Logic] MoveTowards failed for {0}.", cachedPosition);
                        }
                        return true;
                    }
                }
                else
                {
                    var dist = LokiPoe.Me.Position.Distance(cachedPosition);
                    if (dist > OldRoutineSettings.Instance.MaxRangeRange)
                    {
                        Log.InfoFormat("[Logic] Now moving towards {0} because [dist ({1}) > MaxRangeRange ({2})]",
                            cachedPosition, dist, OldRoutineSettings.Instance.MaxRangeRange);
                        LokiPoe.ProcessHookManager.ClearAllKeyStates();
                        if (!PlayerMover.MoveTowards(cachedPosition))
                        {
                            Log.ErrorFormat("[Logic] MoveTowards failed for {0}.", cachedPosition);
                        }
                        return true;
                    }
                }

                await DisableAlwaysHiglight();
                var err = LokiPoe.InGameState.UseError.None;
                if (LokiPoe.InGameState.SkillBarPanel.Slot(slot).Name == "Incinerate")
                    err = LokiPoe.InGameState.SkillBarPanel.BeginUseAt(slot, true, targetPosition);
                else
                    err = LokiPoe.InGameState.SkillBarPanel.UseAt(slot, aip, targetPosition);
                if (err != LokiPoe.InGameState.UseError.None)
                {
                    Log.ErrorFormat("[Logic] UseAt returned {0}.", err);
                }

                return true;

Hope you can keep up with mana

P.S. MaxRangeRange most be considered what it is...Melee range, if you trick it to think 40 is a good meleerange, you are doomed. (the ProxShield logic consider you a smart person that set a melee range within 15/18, so that, if you fall in the ProxShield logic, it will move you within MaxMeleRange (15/18) even if you have no slot selected for melee, and so inside the shield.)

So this code must fix the issue of bot facerunning non-Proximity enemies all the time? Will it deem non-Proximity enemies as "fit for Ranged incinerate attack"?

 

[alcor75]

this make it so you start cast incenerate (err = LokiPoe.InGameState.SkillBarPanel.BeginUseAt(slot, true, targetPosition); ) at the max range configured ( my setting: combat:65 melee(slot -1):15 ranged: (Incenerateslot)33 ) and keep firing and turning to next best target without stopping shooting, until the bot decide that he need to move, and release the skill key (LokiPoe.ProcessHookManager.ClearAllKeyStates(); ).

 

[Ontis]

this make it so you start cast incenerate (err = LokiPoe.InGameState.SkillBarPanel.BeginUseAt(slot, true, targetPosition); ) at the max range configured ( my setting: combat:65 melee(slot -1):15 rangedIncenerateslot)33 ) and keep firing and turning to next best target without stopping shooting, until the bot decide that he need to move, and release the skill key (LokiPoe.ProcessHookManager.ClearAllKeyStates(); ).

Sounds very promising. Could you please upload an updated .cs file? I tried to replace the abovementioned block of text but it seems that I've messed something up, since the routine no longer works.

 

[alcor75]

Here another perfect example of why i don't help this community as i wish.
Is not enough to provide information so people can fix their stufs, you always have to spend at least 1 hour to make so people have their dinner ready.

Incenerate Routine