Screenshot Thread

[luciferc]

Like the idea of giving people who dont know about sigs etc. a little updater so they spam less asking for it if no one is on. XD

[Robske]

Nothing really special here.

It's a pvp 'tool' I wrote for my arena parter (spriest) who just can't be arsed to dispel magical CC of me. I play casually with him on live servers and don't need this crap when I'm playing with decent people on tournys.

When the user of this tool recieves a whisper containing a certain keyword - Dispel in this case - it will attempt to cast Dispel Magic on that person on the next free global cooldown (which is always within less than ~1.5 seconds seeing as it's evaluated every frame). The user is also alerted through a text message center screen. A colored line will be drawn from the user to the person who requested the dispel. The color of this line indicates the Line Of Sight status. This allows the tunnel visioning priest to adjust his position accordingly.

What is visible on this screenshot: Me whispering myself with the word Dispel, but instead of dispelling the following command got executed (testing purposes): /cast [target=nameoftheguywhowhispered] Fan of Knives
Oh and Player Name is obviously evaluated in the real version, I didn't want to black out the pretty font



See this as an advanced form of multi-boxing instead of cheating

[DrakeFish]

It's a good idea but.. Why not using AddonsChannel which wouldn't show/send any real whispers?

[Robske]

It's a good idea but.. Why not using AddonsChannel which wouldn't show/send any real whispers?

Simple, I don't know how to use that channel, which will now change.

[DrakeFish]

That link could probly help you:
API SendAddonMessage - WoWWiki - Your guide to the World of Warcraft

I never used it since I'm not working on addons but it looks great.

[Cypher]

My Addresses updater, made in C#. The patterns list is very easy to modify.
Here's an example of a pattern:

AddToList("ZoneID", // Name of the address
	"00 8B 15 ?? ?? ?? ?? 89 45 D4 A1 ?? ?? ?? ?? 3B C1", // Pattern (?? can be anything)
	0xB, // How much bytes away from the address do we find that pattern
	false, // true if we have to substract to get to the address, false to add
	2); // type: 1 will return the address found, 2 will return the constant at this address.

Probly gonna make one with public addresses to post it on new patches.

Just fyi, your pattern scanner looks very slow. Mine suffered the same problem at first, however once I started caching large blocks of data rather than reading byte-by-byte is became a LOT faster.

ReadProcessMemory is a huge bottleneck. Check out my implementation in HadesMem if you want.

[UnknOwned]

Just fyi, your pattern scanner looks very slow. Mine suffered the same problem at first, however once I started caching large blocks of data rather than reading byte-by-byte is became a LOT faster.

ReadProcessMemory is a huge bottleneck. Check out my implementation in HadesMem if you want.

Hehe, i told him the same thing.

[-Ryuk-]

Oh the joys of debugging, I was looking what gets accessed when I fall, Well I found 00411c89 which led me to 00411ce4 which when I changed 75 to 74. The sky became a very flashy critter which a huge level ^^ Screen shot below for proof.

[Zantas]

Haha that's pure winfail

[flo8464]

Just fyi, your pattern scanner looks very slow. Mine suffered the same problem at first, however once I started caching large blocks of data rather than reading byte-by-byte is became a LOT faster.

ReadProcessMemory is a huge bottleneck. Check out my implementation in HadesMem if you want.

Don't you think I/O is the bottleneck here? I doubt he scans and saves the timestamps before he does any output.

[Cypher]

Don't you think I/O is the bottleneck here? I doubt he scans and saves the timestamps before he does any output.

If he's doing what I think he's doing (scanning byte-by-byte using ReadProcessMemory) then it's definitely the memory reading that's the bottleneck. Console output is nothing in comparison.

[DrakeFish]

I do read byte-by-byte, what do you suggest me to do for it to be faster then?

[Cypher]

I do read byte-by-byte, what do you suggest me to do for it to be faster then?

I already told you, cache the memory locally in large chunks (I think I use like 0x5000 or some other equally large -- and totally arbitrary -- number), then work on those chunks.

Check my implementation in HadesMem if you want a code example.

[flo8464]

I do read byte-by-byte, what do you suggest me to do for it to be faster then?

Read bigger chunks of data and work on them.
I used to read 16kb + size of the pattern.

My implementation is just a translation of BlackMagic's FindPattern from C# to C++, and I increased the chunksize from 1kb bytes to 16kb.

Maybe Cypher's implementation is better, don't know how he did it, just take a look at his thread.

[DrakeFish]

I already told you, cache the memory locally in large chunks (I think I use like 0x5000 or some other equally large -- and totally arbitrary -- number), then work on those chunks.

Check my implementation in HadesMem if you want a code example.

Oh kk didn't see the other post