Heh-heh... uhh.. actually I was having it screendump the information to the client.
Which, yes, was messy... and extremely slow.
How can I do a memory dump of what (mp.dll? my_hack.dll?) is doing? (Sorry, I'm new
to this). I'm guessing that I would also need to know what was contained at the
beginning of pvPrivateData in order to tell where the relative location is.
I guess my question really is what tool(s)/method(s) do I need to do this?
Thank you very much for your help so far!
-----David "BAILOPAN" Anderson
> Okay, I'm amazed that mess actually works... I'll follow up with the
> obvious next question. What's the easiest way of finding the correct
> offset, knowing that there is one number somewhere in there
> (pvPrivateData) that's correct?
>
> Is there something better than going from 0 to sizeof() and logging
> the output?
> That's about the best way. Dump memory, do something that causes a
> change to the entity. Dump memory again.
--
Jeffrey "botman" Broome
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
