Hello MMOwned!
Loving the new site ^^
Ok, to my question.
How can I check if a mining/herbing node is underground/underwater?
Im not asking to code, juts asking how I could!
Hello MMOwned!
Loving the new site ^^
Ok, to my question.
How can I check if a mining/herbing node is underground/underwater?
Im not asking to code, juts asking how I could!
|Leacher:11/2009|Donor:02/2010|Established Member:09/2010|Contributor:09/2010|Elite:08/2013|
I'm not aware of an easy way to do this. You'd probably have to parse the ADT in question to see if there is water above it (but no terrain between it and the water).
There has to be a better way than that =/
|Leacher:11/2009|Donor:02/2010|Established Member:09/2010|Contributor:09/2010|Elite:08/2013|
You can call TraceLine with the correct flags to 'hit' on water.
There was a CC for glider named FarmPlix - flying bot based on glider api. If you look at its code you'll find interesting function:
So [[NodeBaseAddr + 0xD0] + 0x84] - node flags.Code:public bool IsNodeUnderground(GNode node) { int _offset = Context.Memory.ReadInt(node.BaseAddress + 0xD0, "IsNodeUnderground - Offset 1"); int _value = Context.Memory.ReadByte(_offset + 0x84, "IsNodeUnderground - Offset 2"); return (_value & 0x3) == 3; }
These offsets are outdated.
Isn't 0xD0 the descriptors (for now, atleast)?
[16:15:41] Cypher: caus the CPU is a dick
[16:16:07] kynox: CPU is mad
[16:16:15] Cypher: CPU is all like
[16:16:16] Cypher: whatever, i do what i want
I had it down as 0x8.
Thanks Millionarie.
Now to find the 0x84
|Leacher:11/2009|Donor:02/2010|Established Member:09/2010|Contributor:09/2010|Elite:08/2013|
I think the best way is to track code ref to [[Base+0xD0]+0x84]] in debugger for wow 3.0.9, then to find this code in the current wow.
However I was unable to find private wow 3.0.9 server on the web.
Its not what it used to be, Ive tried
So I need wow 3.0.9?
|Leacher:11/2009|Donor:02/2010|Established Member:09/2010|Contributor:09/2010|Elite:08/2013|
i think that's the easier way:
find an object which is underwater and get it's descriptor address. view this memory region in cheatengine. we should be looking for "int". now look at the descriptor fields of an object which is not underwater in cheatengine
compare these two... we are looking for a value which does return 3 if we use a "bitwise and" with a 3 on it at the undewater object (that means we are looking for a value like 3/7/11/15 and so on...) and a value which does not return this on the not underwater object