Is there a ban risk associated with the compatibility tool though...
as I already wrote:
I think steam might want to reconsider what ITS position is on this. hooking into the user's windows api files (like kernel32.dll in this instance) is borderline viral and/or rootkit activity.. blizzard got into trouble changing users windows files and monitoring users files running in memory and the like.
this steam compatibility tool doesn't do anything except reset the windows api that STEAM itself hooked. no steam code is changed with ANY of our trainers or this tool.
our trainers manipulate the game code itself and nothing more.
I think steam is messing around with something here that might get them into trouble..
best,
Cal
Is there a ban risk associated with the compatibility tool though...
as I already wrote:
I think steam might want to reconsider what ITS position is on this. hooking into the user's windows api files (like kernel32.dll in this instance) is borderline viral and/or rootkit activity.. blizzard got into trouble changing users windows files and monitoring users files running in memory and the like.
this steam compatibility tool doesn't do anything except reset the windows api that STEAM itself hooked. no steam code is changed with ANY of our trainers or this tool.
our trainers manipulate the game code itself and nothing more.
I think steam is messing around with something here that might get them into trouble..
best,
Cal
i hope so cal, its the only way that companies learn that the consumer actually has the power.
If Steam now blocks the use of the F1 key, then how about remaking the trainers to use a different activation key instead?
its way more complicated than that.. lol
best,
Cal