Amplify - a Mage CC Powered by Blast Processing!

Hello - nice class so far

With some flaws.
1. It doesn't looks for mobs immunity for frost/fire and not use opposed spells
2. It doesn't use Procs of Instant Fireball/Frostfire
3. It reaction on Adds is way to long - this issue is still unclear but followed my logic i've got myself in glider CC - it's a custom class responsibility.
4. Sometimes its just dumps red tree behaviour things to debugtab and stops reacting at all. Restarting of script doesn't help - i should then restart whole HB. <-this is a main reason why im back to default class.

 

I'd like to thank you once again CnG for another great CC.

Was wondering if you can help me tweak it just a bit on my side.

I would like to give Ice Lance a higher priority over Arcane Missiles if FoF is procced.

thanks again.

 

1. no mage cc ever has, and it will happen eventualy.
2.yes it does, if its not you need to post a log.
3. not exactly sure what your talking about but if polymorph/frostnova is working on the default CC, and not on amplify then theres something up with your install since its the same code.
4.not exactly sure what you mean there. but again post a log, you should be getting the same performance / reliability with amplify as the default CC gets.

post a full log with an attachment

 

Amplify Version 1.1, out now!

 

Since all my mates have decided to play LotR while I was on holidays for 4 weeks and have given up WoW. I had dragged their 4 of their backsides for 2 months through instances with my tank to gear them up, now they have deserted me when I want to level my mage

Amplify and Instancebuddy, FTW

G

 

I tested 1.1 on my mage, and works great. Tested arcane spec, and it did hit arcane missiles often, but it was spamming frostbolt rather than arcane blast. I'm still excited to use it once i hit 80 tho, as arcane is a very high PvE dps spec at the moment.

 

Got a talent tree for this, ones on EJ are foobar (34/5/3) when only 34 pts available. Pure arcane or a couple of ponts in fire and frost ?

 

Tries to conjure mana gems all the time, even when there is one in your bag, or maybe thats just me

G

 

Be nice to be able to make Glyph of Mage Armor again, 1000g a pop starting price on my server since Blizz hasn't fixed it, daylight robbery I tell ya.

 

it might just be you, make sure you dont have any Mana Agates or anything like that after the patch, and if your mana gem has a diffrent name then just "mana gem"

 

or hop on the chat and i will help diagnose it

 

Had a mana saphire in there, seems to be working now, thanks for the headsup.

G

 

http://forums.worldofwarcraft.com/thread.html?topicId=27188059040&sid=1&pageNo=4#60

With all the things wrong with mage glyphs, is anyone bothering to play a mage ? Bliz don't seem interested in fixing it either, 1 class completely foobar and they don't give a rats.

G

 

Great update!

 

Hey, just wanted to say that this CC is GREAT, I'm almost level 40 on my mage and it realy works fantastic!

 

tried new amplify 1.1 u just added,,, with the new IB and new HM.... now my mage is not attacking... i turned all poulls off except frostbolt... any suggestions?

 

could u add mirror image and Blink that would be awsome it should have a blink and mirror for pvping

 

Zomg! Great great update. Works so much better now and not taking any damage! Thank you for your hard work and effort!

 

Since the newest Version of this CC i got these errors...after he kills something. And sometimes he pull a mob and stand still...and die

Code:

System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei Amplify.Amplify.<Frost_rotation>b__9d(Object ret) in c:\Users\Pierre\Desktop\kollegah\CustomClasses\Amplify\Frost.cs:Zeile 35.
   bei TreeSharp.Decorator.CanRun(Object context)
   bei TreeSharp.Decorator.a.a()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.PrioritySelector.a.b()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.Switch`1.<Execute>d__2.a()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.PrioritySelector.a.b()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.PrioritySelector.a.b()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.Decorator.a.a()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.PrioritySelector.a.b()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.PrioritySelector.a.b()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.Decorator.a.a()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.PrioritySelector.a.b()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.PrioritySelector.a.b()
   bei TreeSharp.Composite.Tick(Object context)
   bei TreeSharp.PrioritySelector.a.b()
   bei TreeSharp.Composite.Tick(Object context)
   bei Styx.Logic.BehaviorTree.TreeRoot.b()

 

yea, i know, its at a certain level, but for some reason, something isnt getting past what its suppose to, and ive been trying to track it back. but no luck so far, if your having issues like these, roll back.