Something more useful for you guys?

[Xarg0]

This Thread is epic, I'd rly like to use these structures but first I've got to learn more c++, since autoit sucks (it's just too slow to build a real bot wiht it).
Btw does someone have nice tuts on memory read/writing in c++ with the stupid winapi, the microsoft reference is too confusing.

[Whalemarte]

This Thread is epic, I'd rly like to use these structures but first I've got to learn more c++, since autoit sucks (it's just too slow to build a real bot wiht it).
Btw does someone have nice tuts on memory read/writing in c++ with the stupid winapi, the microsoft reference is too confusing.

You are wrong about autoit being too slow

[suicidity]

autoit sucks especially for memory reading.

[Xarg0]

The reason that I prefer c++ over autoit is very simple, with autoit you'll be never able to provide uptodate data to your bot without stopping the main procesdure, this means, while you are retreving the new data from the memory your bot is unable to do anything. If you are trying to write a human like bot, autoit just wont be fast enough to react to movements of npcs and the like.
MfG Xarg0

[Cypher]

The reason that I prefer c++ over autoit is very simple, with autoit you'll be never able to provide uptodate data to your bot without stopping the main procesdure, this means, while you are retreving the new data from the memory your bot is unable to do anything. If you are trying to write a human like bot, autoit just wont be fast enough to react to movements of npcs and the like.
MfG Xarg0

Did someone say...... THREADING??

[Zephir]

The reason that I prefer c++ over autoit is very simple, with autoit you'll be never able to provide uptodate data to your bot without stopping the main procesdure, this means, while you are retreving the new data from the memory your bot is unable to do anything. If you are trying to write a human like bot, autoit just wont be fast enough to react to movements of npcs and the like.
MfG Xarg0

It takes me 1,98 seconds to read 0x1000 ( its 4096 in decimal) from WoW Memory, checking the information and storing it into a plane .txt file. Now your telling me this is not enough? Sure C++ is way faster. But AutoIt is still way faster than a human being will ever be.

[robotkid]

It takes me 1,98 seconds to read 0x1000 ( its 4096 in decimal) from WoW Memory, checking the information and storing it into a plane .txt file. Now your telling me this is not enough? Sure C++ is way faster. But AutoIt is still way faster than a human being will ever be.

What you mean "Human Being" can you read WoW's memory with your mind???
Just j/k XD, well each one of us needs to read this information for different
porpuses and reasons so you can use either way (or more) it's not THAT much
of a difference..by means of speed i mean.

[Cypher]

It takes me 1,98 seconds to read 0x1000 ( its 4096 in decimal) from WoW Memory, checking the information and storing it into a plane .txt file. Now your telling me this is not enough? Sure C++ is way faster. But AutoIt is still way faster than a human being will ever be.

I don't think his point was about how long it takes to read a memory offset. I think his point was that AutoIt doesn't contain support for threading. With threading you can do multiple things simultaneously, you could have one thread handling movement while another makes sure that you're not going to aggro a mob, etc.

With autoit these checks would have to be done seperately, but with a language like C# or C++ you can use threads for a much better end result.