Quote:
Originally Posted by Landiin
Agree, a program that reads the log files and writes a script to be executed by the /do_command is hardly interacting with the game the way the EULA is talking about.
|
It wouldn't be too hard at all to write something that makes it considerably easier to two/multibox using this method. You could even issue "instructions" from one client to another... just setting up macros in the master client that say to group chat (or private chat channel, etc) stuff like "follow me", "cure me", etc... then the automation program reads the log, figures out a command was issued and racks up a /do_file_commands file.. and all you have to do at that point is hit the magic key that executes that.
Yeah, you can do a lot of stuff fairly easily while two/multiboxing.. but this would make things dumbed down to slap a key simple.
Heck, given the hardware it wouldn't be hard at all to set up a raid this way...it sure would be an easy way to cut out the problems with people who just cant hack it, yet you want to bring them along.. they run a specially configured script engine and get told to punch a specific key every second and nothing else. (yes, thats an extreme and stupid example).
Taking it a step further... it's also easy enough to keep track of other things going on and queue up more custom /do_file_commands sets... for example you could have the healer client watching for people taking damage and choose appropriate heals, the tank client could watch for people getting hit and automate a rescue, etc.. and just putting that into your regular rotation means you can react faster and more accurately.
The question for me is at what point does this start violating the spirit of the EULA enough to get "corrected" by SOE about it?