There's a VAST difference between doing stuff "Blizzard doesn't want" and using standard functions to serve our purposes. If Blizzard doesn't want us to use something, they'll remove the functionality, tell us "We don't like how this was being used" and leave it at that, just like they did with the old Decursive, whispercasting, minimap ping-targetting etc.
I'm still waiting for Blizz to remove the ability to use armor by slot number or allow it to have a failure action so if it can't be used it's just like trying to use a spell you don't have. Until then, it's fair game using something that is accepted by the standard macro interface. And even if it does go, people will just switch to using some of the other methods, like "timing" it through castsequences.,,,,,,,,,,, timing got removed. We find a way round it.
I hardly consider that a "questionable" tactic. We're using it for exactly what it's meant for, movement and interaction.ctm-itw had been a topic for a long time. Not what it was made for! (and i check every ptr patch waiting for it to get removed)
I'll keep my mouth shut about why it would be taboo "elsewhere" but I've yet to see anyone, at any time, banned or actioned for sending too many keys at once in this manner. Could you get actioned for flooding the servers? Sure, but I think you'd really have to go out of your way to create a hotkey that would send that much information to the servers. For our purposes, we have the ability to duplicate this with ingame macros by using /click.Spamming loads off keys at the Same time you get banned for saying this on the other site (or topics removed) dark topic still yet we all still use it. the "one key press at a time". is it ok to use?
Everything you've mentioned is wholly doable within the game using Blizzard's own macro system. It doesn't need to be given a stamp of approval for us to use it, Blizzard already gave their stamp of approval when they added it to the game for any player to use.All the top stuff had nerver been oked by blizzard and has been use at own risk not saying we should use ofollow if its automated but bending the rules is what we good at. and if all this does is finds a system blizzard forgot about then its all good.
This, IMO, is not the same thing as what oFollow is trying to do. Blizzard very deliberately removed the ability for people to use the follow command in BGs. Then they came out and said "Hey, we did this on purpose, we don't want people to use /follow in BGs anymore." And oFollow is NOT using an alternative method as provided by an ingame function, it requires the download and use of an external, paid program that reads information on the game client to automatically adjust and move a specific toon in a very specific path to get to a goal location. There is NO ingame function that can duplicate this. It is not now, nor has it ever been, possible to do what oFollow is trying to do via any combination of ingame actions.
Thank you for digging in to this Feehza. This works exactly how I expected it to when I read the instructions.
Connect With Us