4.0 PUBLIC TEST REALM: Up and ready for boxing testing.

[wonz]

/castsequence works ,,,,,,,,,, does not work its not going to be easy for a mixxed group thats for sure

Well, so i believe this is going life as well.

Say goodbye to commasequence macros.

I did post an alternative, but it seems some are worried that could be a bannable offense.. even if keytrokes just get ignored. No idea, if blizzard would ban those who use it for that.

In fact that would mean that even round robin simulations could be a bannable offense, or any kind of key redirection. Because i also could just reroute the key to a empty actionbar button..

[ebony]

Well, so i believe this is going life as well.

Say goodbye to commasequence macros.

I did post an alternative, but it seems some are worried that could be a bannable offense.. even if keytrokes just get ignored. No idea, if blizzard would ban those who use it for that.

In fact that would mean that even round robin simulations could be a bannable offense, or any kind of key redirection. Because i also could just reroute the key to a empty actionbar button..

this could be looking bad what and what we can not do. noone got banned for ,,,,,,,, so if they was that pickey they would if its useing a blizzard macrio then we "sould be safe" i have manged to make a few simple marcios. dps is poor though.

Round robin simulation's who knows.

[Bigfish]

Personally, I'm probably going to use the method I did before of mapping out DPS rotations and just writing really long macros that take around 60-120 seconds of DPS to get through.

I suppose from a design standpoint, all the procs and such that players have to keep track of is meant to make the game a bit more whack-a-mole with multiple moles instead of whack-a-mole with just one. Personally, the talent trees seem to involve a little too much pigeon holing to me. Seems kind of a double whammy to have our macros broken and then taking away almost all the customization of the talent trees.