Unless we can find the list of approved programs by Turbine the CoC is pretty black and white. And poorly enforced (as exampled by the boxer players).
Printable View
Unless we can find the list of approved programs by Turbine the CoC is pretty black and white. And poorly enforced (as exampled by the boxer players).
I was in the Moors earlier and became aware of macroers. They are not hard to spot. When one or two freeps can wipe 10+ high level creeps and take no damage, then macroing is evident, and/'or an exploit is being used in some way. However, I do not see the GMs doing anything about it. I have complained in the past and was told that it is considered game play. I can see the dilemma from the standpoint of the GMs; How do they spot someone using macros; How do they gather the evidence? Unless there is something they can see in the game matrix that indicates that a certain player is using hardware that allows them to macro, and are actively using macros, then banning someone would be a judgement call based on intuition and less than credible circumstantial evidence. Do you know how many lines of code they would have to look at to see if an exploit is happening? Don't see it happening...Don't get butthurt and report, just get even...
Well you're the perfect example of someone who gets people banned for nothing. "Macro's" as you like to put it, were fixed some time ago. If you couldn't kill these two, those creeps were simply awful.
"Macro'ing" gives no substantial benefit anymore, other than having your skill rotation on one mouseclick. That is all. Macro's can no longer be used to exploit skills, and I would personally consider it a nerf to myself to use macro's. Skills need to be used reactively/proactively in PvP, and you can't do that with a macro.
If these freeps were exploiting something else (which I doubt), it was something else.
If you're just bad, don't blame it all on this myth called "macro's".
It is not up to the individual gamer to judge the others. If you have a suspicion, report and move on.
I understand frustration and the Name and Shame thing but too often it's just venting after a death in the moors. At least this is true for Brandywine.
that pretty much summarizes the entirety of the lotro monster forums, great post.
"Macro's" now are simply key strokes or stroke bound to cut skill animations, really anyone can do this now you could before. So while the witch hunt continues for macroers the real question is should other skills be able to cut animations? If the skill has an animation we have to assume that turbine believes thats WAI, if the animation is cut that would be the skill not WAI.
thats the reality of where we are at with macro's, as far as I can tell, and as my first wife you to say to me literally everyday "yes, you are right"
Macroing really only gives a noticeable advantage in a 1v1 standpoint with wargs being able to do 10k+ damage on an initial pounce on full audacity light armor freeps, or reavers getting a four bleed impale off in about 1 second. I echo Giliodor in those creeps just sucked. If an exploit was being used, macroing wasn't the bad guy there. However, I disagree that macroing is fine. Maybe to a heavy armor it's all fun and games, but light armors get shredded by macroers because, unlike heavies, we do not have the grace "period" of taking far less damage. Our defenses against being killed are reactive- CC and heals, and when our window of time to react is shut down, then we are put in a very difficult spot. For example, a reaver popping a four bleed impale and chaining Charge with resilience, pots, and a brand and a warg pre-potting on the initial pounce+using sprint (which macroing wargs use as part of the rotation anyways). Those two situations are almost impossible to defend against as a Light Armor class.
If someone is filing a multitude of false reports, they are subject to disciplinary action. This thread has gotten a bit out of hand and will be closed. We have no issue with civil discussion but when it turns into a battle of insults and name-calling that is when threads get closed.