|
Patching the client memory (modifying the client) is what makes it illegal. There are two type of winamp "mods" around:
One is mostly a conventional type of mod. It has lua/xml script that works in game. However it exploits a hole in the UI (key bindings) to save information in real time. A separate polling program watches for those changes and works winamp from there.
This method is being killed in 1.9 by Blizzard. The bindings-cache file will not update in realtime but only on reloads. They've done this many times for other holes like the config.wtf file and chat logs. They don't want mods interacting with outside programs in real time. It makes botting more accessable to the masses. The winamp mod that uses this does not modify the game client at all (patching its memory or hooking parts to an outside program).
The other winamp "mod" is a directx overlay program that sits as a top-level frame and has no relationship to WoW. This one is safe. It can run with or without WoW and is as legal as a calculator applet that runs as a toplevel frame.
Neither of these winamp mods patch client memory or alter the client as your program does. Blizzard doesn't want anyone injecting executable code into their game outside the scripting system that they gave us.
If the program can be modified so it's a window summoned by a global key and has no hooks or relationship to WoW, it'd likely be perfectly acceptable and probably a very successful program.
|