What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Amplify - a Mage CC Powered by Blast Processing!

I've never had the problem of spamming arcane brilliance. MrBig you Gould know better than to post without logs or looking at the CC files yourself :(
 
can someone help me with the arcane part, need it to get atleast 3 stacks before firing AM ?
 
can someone help me with the arcane part, need it to get atleast 3 stacks before firing AM ?
it bugs the CC out man... I have tried to get it to do this and it breaks the rotation. Also, what makes it even worse there is nothing in the logs to show why the rotation stops... so I am guessing this feature is gonna need to be an overhaul or a complete rotation rewrite imo... but CnG already stated his CC is to be used for leveling and general instanceing/grinding. Not min/max raiding/top dps
 
Ok evrything works fine expet 1 thing... The mage dose start the attacks with the Pull spell but after that spell he is not using the main spam spell... (like frostbolt in my case!) can someone help me plz?
 
again, i need logs, because i have it turned off for BG's now, so it should only do it in instances, and once the party is buffed up it shouldn't be a problem.

I had that problem awhile back but haven't tried out 1.8 yet... looking forward to giving it a go in BGs. Would it be possible to have the toon cast Arcane Brilliance at maybe 20 seconds to go in prep time (assuming the toon isn't mounted)? That should cover just about anyone entering the BG and give plenty of time for the toon to mount up and get ready to ride out. After that point it would be best to only cast it once upon rez...
 
Arcane = Sucks for leveling
Frost = the Bees Knees

Arcane also sucks for very low level farming/questing profiles. Wastes arc blast cast time when AB will single shot. Any chance entering an if target Hp 10k or lower = casts AB before anything else? Shouldn't hurt or slow it down since it is behaviortrees correct? Just an addition, even though dual speccing fixes that if your offspec is frost.
 
it bugs the CC out man... I have tried to get it to do this and it breaks the rotation. Also, what makes it even worse there is nothing in the logs to show why the rotation stops... so I am guessing this feature is gonna need to be an overhaul or a complete rotation rewrite imo... but CnG already stated his CC is to be used for leveling and general instanceing/grinding. Not min/max raiding/top dps

If you look where it decides if it should cast Arcane Barrage, it shows the 3 stacks check... Add this check to the Arcane Missiles check. Easymode
Edit: Oh and then move the arcane missiles check above arcane barrage, so it won't waste the mana, and AM does more damage anyways.
 
Last edited:
Arcane also sucks for very low level farming/questing profiles. Wastes arc blast cast time when AB will single shot. Any chance entering an if target Hp 10k or lower = casts AB before anything else? Shouldn't hurt or slow it down since it is behaviortrees correct? Just an addition, even though dual speccing fixes that if your offspec is frost.
heres the thing, people want the rotations to reflect high end raiding, and im fine with that, give me the information (thats not outdated or completely convoluted) and ill write the rotation to reflect it, but this CC has always be primarily a leveling CC, even in PVP its almost impossible that you'll get even 2 stacks of arcane blast let alone 4.

thats why when i released this new version i build it more like Zerfall, where there is room for a Instance rotation, and a PVP rotation. but people keep posting things and 90% of the time the conversation goes as follows

User: it noah wrokz fix iz!
Me: can you post a log, since your not being anywhere need descriptive enough theres no way i can track down the issue without a log
User:....

N1 if you wanna help send me a pm and ill send you my skype info and we can talk, but ive pretty much given up hope that anyone will give a flying fuck long enough to speak up about what they actually want instead of just complaining.
 
Yes Cng, I hope you didn't forget the Fire rotation :(
I'll redownload Penguin Messenger and sign into MSN messenger, which I should still have you added on. We can discuss on there. In about 3.5 hrs I'll be home and on MSN.
I look forward to discussing options with you here.
Talk to you soon, N1Y
 
I just stumbled across this large error while looking for something else in the log, not sure if it'll mean anything to you or if it will help. Just thought it may mean something to you as it doesn't to me. I didn't see it when it happened so I'm not sure what it meant.

Code:
[15:21:11:208] Changed POI to:Type: Kill, Name: Coldlurk Burrower
[15:21:11:758] Spell_C::CastSpell(116, 0, 0xF330C0C3001CADC7, 0) [2081]
[15:21:11:774] [Amplify]: Casting Frostbolt
[15:21:13:424] Spell_C::CastSpell(116, 0, 0xF330C0C3001CADC7, 0) [2082]
[15:21:13:693] [Amplify]: Ground Clicked for Spell Freeze
[15:21:15:689] [Amplify]: Target Frozen Blinking Away.
[15:21:15:707] Spell_C::CastSpell(122, 0, 0xF330C0C3001CADC7, 0) [2083]
[15:21:17:134] [Amplify]: Blink!
[15:21:17:135] Spell_C::CastSpell(1953, 0, 0x0, 0) [2084]
[15:21:17:441] System.NullReferenceException: Object reference not set to an instance of an object.
   at Amplify.Amplify.BlinkBack() in c:\Users\Ewan\Desktop\So much work\NEW HB\CustomClasses\Amplify\Methods.cs:line 423
   at Amplify.Amplify.FrostNova() in c:\Users\Ewan\Desktop\So much work\NEW HB\CustomClasses\Amplify\Methods.cs:line 294
   at Amplify.Amplify.<Frost_rotation>b__127(Object ret) in c:\Users\Ewan\Desktop\So much work\NEW HB\CustomClasses\Amplify\Frost.cs:line 92
   at TreeSharp.Action.RunAction(Object context)
   at TreeSharp.Action.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.Decorator.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.Switch`1.#h.#TF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.Decorator.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at Styx.Logic.BehaviorTree.TreeRoot.Tick()
[15:21:17:441] Cleared POI - Reason Exception in Root.Tick()
[15:21:17:441] Cleared POI
 
i need FULL logs as attachments and descriptions of the issue. just posting snippets does not help me help you.
 
Well the file is too large to upload to the forum unfortunately
 
Put it in a .zip file. Or break it into multiple .txt files...
 
Hey guys. I have an awkward problem. I think its the way I have configured things though.
When the bot sees a mob. It walks up then starts to frostbolt, stops midway through steps 2 steps forward then starts casting again. This continues untill either the frostbolt completes or the mob is actually aggroed.
Anyone have any ideas? Maybe i should try to get it to pull with ice lance instead?
 
Hey guys. I have an awkward problem. I think its the way I have configured things though.
When the bot sees a mob. It walks up then starts to frostbolt, stops midway through steps 2 steps forward then starts casting again. This continues untill either the frostbolt completes or the mob is actually aggroed.
Anyone have any ideas? Maybe i should try to get it to pull with ice lance instead?
That's how the pulling is coded, there is no problem here. Set your pull to an instance cast is your best choice.
 
How come it isn't using Frostfire bolt on the procs?
 
Back
Top