Yeah, a log file should even be append only not just write only.
And yeah, a bot would have an add on pump out info to a file, and in effect 'tail -f' it... of course not doing this does not stop botting, just takes away an easy route to sync it with the game, so a delayed write should take care of that concern. Next of course you can write something to sniff the ram/cache, but then you can also just sniff the game if you are going that far.
Yeah, a log file should even be append only not just write only.
And yeah, a bot would have an add on pump out info to a file, and in effect 'tail -f' it... of course not doing this does not stop botting, just takes away an easy route to sync it with the game, so a delayed write should take care of that concern. Next of course you can write something to sniff the ram/cache, but then you can also just sniff the game if you are going that far.
Personally I put things in two baskets; reading and writing. Append falls into the writing category although it's obviously a different flag. Either way, it's definitely not reading, and a delayed write renders the botting argument useless.
I'm guessing this would-be bot is actually a third party application, which can read files and push buttons.
Yup. It makes half the job of writing a bot much easier, as the game could write any info the bot needs out to a file. The other half, actually taking action in the game based on that info, would still require more work. But anything that makes botting easier won't make it into WoW.
Personally I put things in two baskets; reading and writing. Append falls into the writing category although it's obviously a different flag. Either way, it's definitely not reading, and a delayed write renders the botting argument useless.
I think Blizzard has proven to be more paranoid, and they drew the line at certain things. This is one of them.
See the thing is , the OS does that, not the WoW client. The WoW client asked the OS to read the file into ram and the the WoW client asks the OS to dump the file to disk....
so.. umm. not really a logical difference we already have abstractiion layers.... and this point is not for any file writing anywhere on the system, it can be sandboxed .
A split hair is still a hair. My point was that the author does not have real-time access to files.
Yup. It makes half the job of writing a bot much easier, as the game could write any info the bot needs out to a file. The other half, actually taking action in the game based on that info, would still require more work. But anything that makes botting easier won't make it into WoW.
I think Blizzard has proven to be more paranoid, and they drew the line at certain things. This is one of them.
Not really sure they did not already draw the line exactly here though, since you can turn on combat logging to disk....
You could join a custom chat channel and output your log information to that channel. By enabling chat logging, you get a file with all your chat activity (and therefore also your log-channel). That log is written during gameplay.
Sorry for bumping an old thread but I believe that log files aren't written during gameplay, for me WoWChatLog.txt only updates when I shut down wow ( not on ui-reload or in real-time).
And yeah, a bot would have an add on pump out info to a file, and in effect 'tail -f' it... of course not doing this does not stop botting, just takes away an easy route to sync it with the game, so a delayed write should take care of that concern. Next of course you can write something to sniff the ram/cache, but then you can also just sniff the game if you are going that far.
Personally I put things in two baskets; reading and writing. Append falls into the writing category although it's obviously a different flag. Either way, it's definitely not reading, and a delayed write renders the botting argument useless.
Yup. It makes half the job of writing a bot much easier, as the game could write any info the bot needs out to a file. The other half, actually taking action in the game based on that info, would still require more work. But anything that makes botting easier won't make it into WoW.
I think Blizzard has proven to be more paranoid, and they drew the line at certain things. This is one of them.
A split hair is still a hair. My point was that the author does not have real-time access to files.
Ah good, cause that point was not made in what you said, so I rephrased it to show it was not really saying anything by itself.
And, a logger still would not need to give them this is my point.
Not really sure they did not already draw the line exactly here though, since you can turn on combat logging to disk....
The contents of of the combat log are controlled by Blizzard.
If what galmok says it true, no more or less so then a log file could/would be so what is your point?