Amplify - a Mage CC Powered by Blast Processing!

[smag]

i hear where you are coming from. just thought it might help for those moments where hb runs solo up to a flag with 3-4 guards on it lol. but yes, the cc behaves very nicely in bgs, ive sat and watched it run some just because it has impressed me so much

 

[NL1337]

don't works for me attacking and then bugging out ...View attachment pvp frost log.txt

 

[CodenameG]

don't works for me attacking and then bugging out ...View attachment 15035

dude.
[11:51:07:665] You have not configured Amplify, Configuration is needed for this CC to work, Please Configure your Settings now

then you configured the CC or at least opened the configuration pane. but didn't close honor buddy out and restart.

i have written about how the CC needs to be configured about 10 times now just on this thread alone. please do me a favor and reading up a bit more before you decide to posts logs about things that are easily fixed.

 

[cryogenicrooster]

CodenameG, thank you for an awesome CC. I love frost and this works so well. Especially using the brain freeze procs and freeze. Keep up the good work.

Edit: managed to figure out my previous question.

 

[yepuhuh]

Love this CC.

Leveled a mage when first released and leveling another now with it.

Only thing I can ask for is an option for what to do when using frost nova, step back, jump to side or blink.

Loved just jumping back on nova.

 

[CodenameG]

Love this CC.

Leveled a mage when first released and leveling another now with it.

Only thing I can ask for is an option for what to do when using frost nova, step back, jump to side or blink.

Loved just jumping back on nova.

well its really been an evolution. we've seen the jump strife, where it really was the right solution at the right time, to now. where blink, or run away look a lot more human when compared to back peddling, or the previously mentioned jump strife. maybe in the future ill bring it back, but at this point its very unlikely.

 

[Stormchasing]

Hi CodenameG,

nice CC, works near perfectly for my lvl 80 Mage (i know the Class is written for lvl 85)
The only Problem at this time is when he trys to conjure the ManaGem, u only test for item 36799 (lvl85)
Could this be fixed to:

old HaveManaGem()

       public bool HaveManaGem()
       {
           foreach (WoWItem item in ObjectManager.GetObjectsOfType<WoWItem>(false))
           {
               if (item.Entry == 36799)
               {
                   ManaGem = item;
                   return true;
               }
              
           }
            return false;
           
       }

new HaveManaGem()

       public bool HaveManaGem()
       {
	   int[] ManaGems = {5513,5514,8007,8008,22044,33312,36799};
           foreach (WoWItem item in ObjectManager.GetObjectsOfType<WoWItem>(false))
           {
		if (Array.IndexOf(ManaGems, item.Entry) != -1)
		{
                   ManaGem = item;
                   return true;
		}
           }
            return false;
       }

This one should test for every possible ManaGem, i'll change this tonight in my local copy, but if u release a newer version it would be overwritten, so i'll have to this changes everytime a new version is released

 

[CodenameG]

Hi CodenameG,

nice CC, works near perfectly for my lvl 80 Mage (i know the Class is written for lvl 85)
The only Problem at this time is when he trys to conjure the ManaGem, u only test for item 36799 (lvl85)
Could this be fixed to:

old HaveManaGem()

       public bool HaveManaGem()
       {
           foreach (WoWItem item in ObjectManager.GetObjectsOfType<WoWItem>(false))
           {
               if (item.Entry == 36799)
               {
                   ManaGem = item;
                   return true;
               }
              
           }
            return false;
           
       }

new HaveManaGem()

       public bool HaveManaGem()
       {
	   int[] ManaGems = {5513,5514,8007,8008,22044,33312,36799};
           foreach (WoWItem item in ObjectManager.GetObjectsOfType<WoWItem>(false))
           {
		if (Array.IndexOf(ManaGems, item.Entry) != -1)
		{
                   ManaGem = item;
                   return true;
		}
           }
            return false;
       }

This one should test for every possible ManaGem, i'll change this tonight in my local copy, but if u release a newer version it would be overwritten, so i'll have to this changes everytime a new version is released

it should only be one item that scales. if you have an older mage, one before Cata, try deleting the mana gem in the bag, and conjuring a new one.

that should fix it, since the old one and the new one have diffrent item ID's, hell one of my mages still has a mana agate. lol

 

[yepuhuh]

well its really been an evolution. we've seen the jump strife, where it really was the right solution at the right time, to now. where blink, or run away look a lot more human when compared to back peddling, or the previously mentioned jump strife. maybe in the future ill bring it back, but at this point its very unlikely.

I agree with you mostly but do think the jump strife is more human like (I know I do it all the time) in most situations than blink.
Playing a mage in pvp, blinking after a nova is asking to be killed. In pve, blinking was used when there were multiple adds mostly while in single mobs the jump strife was what I mostly did.

The blinking implemented now is very nice and works well but I do catch him blinking into more mobs more than not. Happens in instances as well but not as often.

I like your CC and will continue to use it.

Thanks again for making it.

 

[schmedes2]

This works great, thanks

 

[db00]

How can I disable the blink?

 

[facedark]

Does this cc use conjure food for long grind sessions? thanks in advance

 

[keleshia]

was wondering is there a blink option? Because since it doesn't detect the blink direction has unfriendly npcs that may cause to aggro another pack, something like this would be handy.
nevertheless, this CC is still awesome! Thanks code...!

 

[aeus]

Love it! Perfect CC...BUT there should really be an option to disable blink.

When I use Archeology Buddy in low lvl areas it looks stupid when Pet shoots and then mage blinks away when mob is less then 10%.

It's a good idea but should be optional.


Keep up the good work!

 

[tilopa]

Thanks for the CC. I wanted to also point out the only major issue I'm having like others are stating is that the toon blinks too often and unnecessarily and cause her to aggro. Is there a way to tone down the blinking?

I made a simple grind profile that was pretty congested with mobs in a tight area and loaded it for my mage with your cc. It was harrowing to watch because she was aggroing like crazy, not just because of the blink but also I'm using the latest HB version that just came out and there is some bug with the pet aggro. Anyway, I was pretty amazed to see her survive through it all as your cc uses poly really well and takes advantage of mirror image and DF. She was able to take control and continuously take down everything with zero deaths.
Much better cc than the default.
+rep

 

[aeus]

If you dont want your toon to blink, disable Frost Nova in CC options and it will stop the blinking....

 

[CodenameG]

If you dont want your toon to blink, disable Frost Nova in CC options and it will stop the blinking....

just so everyone knows im trying to find a creative soultion to the problem, however running back, will put you in the same place so that out. the only thing i can think of is to check to the the mobs in front and behind you, and see, but im not sure.

 

[aeus]

CodenameG: I don't know if anyone said this before but there is a sheep issue when you got adds.

Ex. When 2 mobs attack me, bot sheeps one target properly and then kills the other one. But when the bot killed one of them it supposed to continue with the sheeped one but it doesn't.
It tries to fly away (Archeology scenario) and when it fails because of "In Combat" it just stands there until the sheep is gone from mob. Then the bot waits to get attacked by mob before taking any actions...

Is it possible to force the bot to attack the sheep directly after the other add(s) are killed?

 

[CodenameG]

CodenameG: I don't know if anyone said this before but there is a sheep issue when you got adds.

Ex. When 2 mobs attack me, bot sheeps one target properly and then kills the other one. But when the bot killed one of them it supposed to continue with the sheeped one but it doesn't.
It tries to fly away (Archeology scenario) and when it fails because of "In Combat" it just stands there until the sheep is gone from mob. Then the bot waits to get attacked by mob before taking any actions...

Is it possible to force the bot to attack the sheep directly after the other add(s) are killed?

it shouldnt, i havent had a problem where it wouldnt target the sheep after the main target was killed. it might just be a big introduced in the new hb. but ill take a look

 

[Shakam]

will u ever implant the fire spec? i don?t know when i heard from this, but atm this idea seems to be death
i love your cc big fun watching it