I already tried playing with the z-axsis when this was first posted. I couldn't get it to come down any.
Printable View
I already tried playing with the z-axsis when this was first posted. I couldn't get it to come down any.
hey everyone, first of all love the idea behind this :) truly epic coding! I just wanted to highlight something. I don;t want to put a downer on things but I do want to make sure none of us are punished for our overenthusiasm
I posted this earlier but it may have been overlooked:
Could I ask a few things to those currently testing this?
First of all does the macro for casting things require you to press the button twice? or if you set coordinates does it go off automatically? I ask this cos Blizzard could potentially interpret this as automating an attack. :S (reducing a button press + click to one button press)
as for the minimap movement, again I would be very very weary of this. Even tho I don't for a moment assume you have any malintentions, there have been add-ons in the past that used waypoints and ppl using these were banned. Or is it simply using the clickto move function that blizz has in the game?
Just looking out for the community.. I would recommend having the code looked at by a blizz employee to make sure
I do hope that I am completely wrong and that this is in no way outside the rules, but I hope it's taken into consideration
I wouldn't worry too much about it.
There are other ways that minimize button press.
For example:
/use conjured food
/use conjured water
If you have this macro, you press the button once and you will eat and drink at the same time.
For the waypoint bans (if we are talking about the same thing), it was when there was a mod that created a way point between yourself and a destination and moved you along without you doing anything... basically automating your movements to reach a destination.
The scripts used is from Blizzard's own API which are basically scripts and command lines that Blizz added for the users to use to create mods and such.
So in my opinion, I'm pretty sure that there's nothing wrong with this script usage.
Shweet :) good enough for me! altho I am very easaly convinced :PQuote:
Originally Posted by 'kllrwlf',index.php?page=Thread&postID=42997#post4 2997
/wave hand
These aren't the droids you're looking for.
Out of curriosity does it have to be the mini map we ping? can we just ping the world? What I am asking is you are always at some x y z cord in the world... how would one find out these cords?
I might be doing a Jim Carey impersonation right now... in other words talking out my ass.
I thought we should start collecting data on which spells work with this script. Post ones you have actually tested.
Hunter:
Volley: WORKS
Flare: ABOVE HEAD
Warlock:
Rain of Fire: WORKS
Mage:
Flamestrike: ABOVE HEAD
Blizzard: WORKS
Priest:
Lightwell: ABOVE HEAD (and too high to actually use)
Okay, that was an uniformed question.Quote:
Originally Posted by 'The IT Monkey',index.php?page=Thread&postID=43016#post430 16
BUT, doing some research.
Volley, you can click the volley spell and then click on your mini map and the volley will go off there. Same for Flare. Flare hits above the ground just as if you used the /script macro.
So, this means that volley works as intended but we could possibly put in a bug request for flare and all the other spells this doesn't work on. It is obvious that Blizzard intended for us to be able to call down a targeted AoE by clicking on the mini map ... it's just some of the spells Z axis are off.
And it is the Z axis being off on the SPELL. Players altitude does not matter. It's the area that you are calling down the spell on.
Doing more research... will report back with my findings... what can I say... I am bored as hell at work today.
Boomkin Hurricane = 20ft above your head. Works, though. Doubt it'll hit up there though
As per suggestion's I have touched based with a GM and they have confirmed this appears to be a bug that has been un-identified untill now.
They have passed on the information regarding spells we have identified as Not Working and hopefully we will see something in the patch notes soon!
BRILLIANT!Quote:
Originally Posted by 'Falkor',index.php?page=Thread&postID=43050#post43 050
Though it could have been used to take down that annoying group of flying mobs.
Multiboxers be praised! AoE the Monstrous Kaliri to make dailies easier! ^^
Maybe it's just me, but i find it kind of funny that the AOE landing above your head bug is just now being noticed. Although, I've been playing for nearly 3 years and this post is the first i've ever heard of this particular script.
Yet more eveidence that we are at the extreme edge of WoW's gaming capabilities.
Seriously I think every active boxer should be top of the list for WOTLK beta testing.
With the progress being made in PC processing power and the fact most WoW players now have collections of alts I think Blizz should look at adding 'squad based' capabilities to this game in a future X-pac.
For instance - At level 85 you get 'squad leading' capability - allowing you to add a lv 80 toon and '2box' off the same account. Once yr main hits 86, you can 3 box with 86/84/82, lv 88 for a 4 box team of 88/86/84/82 and at 90 you get the full 5 box experience .
Of course this just means we will be running round with 5 teams of 5 and effectively 25 boxing the raid content :)
- off topic i know - still love the aoe macro ping - we really need to get this working in instances
OooOooooohh..... the plot thickens!!!!!! :DQuote:
Originally Posted by 'Falkor',index.php?page=Thread&postID=43050#post43 050
shweet find :) actually speaking of bugs, has anyone noticed with elemental shammies at least that whenever you kill a mob, whatever actuion you are currently performing gets stopped (8/10) Now I don't mean that if you are spamming lightning bolts, and the mob dies that the ones in mid cast are stopped.. I'm talking every cast..Quote:
Originally Posted by 'Falkor',index.php?page=Thread&postID=43050#post43 050
for instance..
casting at mob1... Looks like this last barrage is going to kill him so i begin healing myself.. barrage hits mob, mob dies.. healing interrupted, on all my shammies
It just occurred to me as there are many spells on other classes that this doesn't happen on, but with AoE spells this problem could be exasperated.
are you using an addon like multiboxer where it automatically calls follow when you leave combat?
keyclone and macros, nothing elseQuote:
Originally Posted by 'Djarid',index.php?page=Thread&postID=43187#post43 187
Oh and I tested it maintaining combat too.. 2 mobs heal after the first one is awaiting a barrage kill and it still happens
Glad you love this macro its had a biggg impact on the community!Quote:
Originally Posted by 'Team Squishee',index.php?page=Thread&postID=43125#post4 3125
As for instance's assuming the WoW Developers fix the Z Axis problem it might also fix the instance issue.
The only reason you cannot cast in instances is because when you cast and then target via the minimap you are effectivly targeting the top of the instance building!
Fingers crossed this should also be fixed and we will be known as the AOE Multiboxing Kings! Fear us now!
Yes this happens alot, like ill be casting my last lightning bolt needed to kill a mob. change targets and spam lightning again, and it like stops the cast and resets it when that first mob drops. Uber annoying.Quote:
Originally Posted by 'Ðeceased',index.php?page=Thread&postID=43186#post 43186
In it's current form, works in Black Morass.
hmm makes me want to rethink my group structure :(
3x shaman for utility because AoE was borked for multi-boxing but now...
Ok, for those who are setting this up for the first time do NOT test is in IF. Doesn't work and took me a good 10 min of playing around to figure out, no clue why it doesn't work in IF. Other then that works great! Much love for enabling me to cast BlizzardX3!
Might want to add a list of zones which this doesn't work in, so far looks like parts of Shatt, Org, and IF. Maybe just cities? If so, no major loss since you don't usually have a need to AoE in the major cities.
The simple answer would not be a list of area's it does / does not work but rather -
Is there a solid roof above your head?
Yes= This macro will proberly not work
No= This macro should work
:thumbup:
After goofing around with this on a Paladin led team of Mages and a Priest, I can say that the easiest use I've found so far is to gather a shit-ton of mobs with Pally (rank 1 consecrate, running like mad) then huddle up and just bring the Blizzards & max rank Consecrate or Holy Wrath down on top of your self using the simple minimap location of (0, 0)
I was trying to call AoEs by pinging the map with the Pally but even the slightest bit off will put AoEs off to the side etc. Just my 2cp.
Be sure to use [nochanneling] in your Blizzards, etc by the way.
Also, for Frost Mages, try:
the aggressive part is up to you, but I find he is such a short duration and you've got 20 mobs in a pack it usually won't cause any problems with him taking off on you. This pops pet and uses his Nova to AE the cluster, then he gets down to biznass. Since I've got wicked agro with my Pally I'm not concerned with Freezing mobs on top of myself as the Mages, in fact I want Chills/freezes for hella crits =)Code:#showtooltip
/cast Summon Water Elemental
/cast Freeze
/run MinimapingLocation(0, 0)
/petaggressive
This new find has greatly increased AoE grinding for me. Replacing Arc Explosion with Blizzard is huge now that it can be effectively done. Better mana/spellpower usage.
Another side note for the Pally. I know I might be going over old news, but since I didn't bother to do any AoE grinding really as a multiboxer and now am... be sure to use Gift of Arthas pots, and get Crystal Spire gems from Un'Goro, as well as Shield Spikes (duh). Anything you can add for reactive dmg is huge.
Anywho, I'm rambling - have fun!
having some problems with blizzard:
my pala has the following macro:
/run Minimap:PingLocation(0,0)
/script Minimap:PingLocation(0,0)
my mages have the following macro:
/cast Blizzard
/script local x, y = Minimap:GetPingPosition() Minimap:PingLocation(x * 140, y * 140)
when i cast this, first time it just shows the green blizzard circles. The next time it casts blizzard at the location i was standing the first time.
The cast after that it's again the previous location.
just a heads up it wouldnt work in org, but then once outside the city it worked great.
What happens if you stand still and click the macro twice?Quote:
Originally Posted by 'Piecemaker',index.php?page=Thread&postID=43589#po st43589
Where are you trying to test this.. location?
standing still: first time just the green circles, second time correct cast.
pala moves 10 yards forward, mages stay at original position: blizzard at pala's first location
whole team moves 100 yards: out of range (trying to cast at previous location obviously)
been testing this in redridge mountains, at various locations
edit: found a solution: put the paladin's macro on a different keybind, press it and then use the blizz macro.
I came across this in the 2.4 patch notes, not sure if it's of any relevance, but it could help possibly.
Spells that require targeting circles will now be castable on textures that would previously disallow their use.
If that has been mentioned previously, sorry for the repost.
Interesting, not sure if its addressing the same issue as in this thread (there are small problems manually using green-circle targeting in specific locations - let alone ping-map)... but one fix could fix the other. Either way, its good news.
I THINK that note was there before this post was made...though, my testing WAS on live servers, not test server, so it COULD be our fix.
I'm doing two mages with blizzard... i have to hit the ping macro twice on my main in order for my alt to cast his blizz too.
I read the whole thread and didnt see what I am about to ask..... so if it has been asked allready, forgive me
Can this be used by the click to move function in game to, move in cool formations, or to regroup after a bad fear bomb?
Can you aquire coordinates of enemy by targeting them?
These may be way out in left field questions, but hey..... Im way out in left field.
There was a post about this also. i think the answer was pretty much that it couldn't be used for movement.
Click to move using mini-map?
Well, I've verified that blizzard works OK with this. Flamestrike does not even touch the mobs on the ground, so it's useless there. Also noticed that your mages always try to target your last ping, so the cast is always one behind your current location. If you're moving enough so that the last loc is out of range, it just fails until the ping updates, then it'll cast at your desired loc.
Interesting macro, indeed.
As per my previous communication with GM's they have currently confirmed they are actually working on a fix for this patch, I don't think what you are looking at in the patch notes is what I've requested but theres a small possability someone else reported a similar error.... 1 bug can have many issues and 1fix hopefully :) well see.
Thanks for the update, I didn't think the fix would make it in 2.4 but if they're working on it now thats great news. This is a powerful ability that'll help a ton once working correctly.
Hi all,
I am new here, but have recently started dualboxing and I am loving it
I am running a Pali/Mage combo, and just got Blizzard on the mage, I tried the following
on Pali:
on Mage:Code:/run Minimap:PingLocation(0, 10)
/script Minimap:PingLocation(0, 10)
No matter where I set the distance on the Paladin the Mage only fires on herself, any help would be appreciated!Code:/cast Blizzard
/script local x, y = Minimap:PingLocation(Minimap:GetPingPosition())
Update: I added that local x, Y thing recently, I had it w/o that but there was also no change. She just casts on top of herself
Wasn't there something about pinging twice for the alt to catch it?