OK sorry i missed that bit. So what does halloween priest use to detect firing? Like what did the maker search for with artmoney?

Would it have been something at CWEAPON?

Post has been edited 1 time(s), last time on Jul 11 2009, 8:11 am by zany_001.

I believe he searched for the cooldown timer(55-57). Do what I suggested to toothfairy and look at the memory map. get a unit to attack something and see how the numbers change when the player moves/attacks.

So im still a little confused on how you actually locate the unit

I've been searching for the unit, but i cant seem to find it exactly

and when i do find it, how will i know its the unit?

all the information for the units on the map are likely stored in a fixed size blocks starting with the unitid and ordered by creation time if you can find the unit id then each bit of information should be at some offset from the unitid
simple example of map with 3 units (3 bytes for the data of each unit)

-- start units (assume units are represented by 3 bytes of data and consist of an id(1 byte long) current hp(1 byte long) and max hp(1 byte long)) --
byte 1 UNITID1
byte 2 first_unit_current_hp
byte 3 first_unit_max_hp
byte 4 UNITID2
byte 5 second_unit_current_hp
byte 6 second_unit_max_hp
byte 7 UNITID3
byte 8 third_unit_current_hp
byte 9 third_unit_max_hp

I don't know if this is actually how it works but I imagine something like that.

edit:
I guess the unit blocks look like this http://farty1billion.dyndns.org/EUDDB/?pg=ref&a=unitnode

okay... so how do u actually locate the unit id in the first place

Same way you found the hp. Look for some unique value you can use as an identifier to trace it in the memory. Looks like hp is (begginningofunitinfo+0x8). So the start of the unit is the address you found the hp at -0x8. Or the ground cooldown is (the address you found the hp at + 0x55 - 0x8) = (the address you found the hp at + 0x4D)

But you have to realize that the EUD condition reads a certain number of bytes at a time(i'm not sure but probably 4 bytes), the type of each data is by the name such as DWORD. DWORD is 4 bytes long. So you have to make sure you have aligned your shit right otherwise you will be maybe reading into values that you don't care about.

You don't actually need the unitid to check if it has stim though only find the location of his respective cooldown bits.

Post has been edited 4 time(s), last time on Jul 11 2009, 7:40 pm by crutex.

I thought i was looking for the locationthe units death?

? You are taking advantage of the unit death's condition to cause a buffer overflow so you can read other parts of memory that you shouldn't be able to. You find the offset of what you are looking for, and convert it into a trigger condition that will cause the proper overflow.

I made this example that will detect your shots with the Marine. I simply added 0x4C to the offset that I found by searching the marine's hp before using EUDTrig. This let me read the Marine's ground weapon cooldown. If it's greater than 1 you are shooting. I added a dc delay so that it will only trigger when he actually shoots (on average). And it doesn't count correctly if you use stimpack.

You can make this into an ammo system by changing the conditions so that IF (player has 0 minerals) AND (ground weapon eud trigger) it moves you immediately to a location centered on top of yourself. This will stop him from getting his shot off.

Attachments:

Or you could just trigger an ally with the enemy and use hypers.
Do you think you could make a quick step by step tute of how you found the required trigger?

Maybe later because I'd want to take screenshots and stuff if I will bother typing out a tutorial. Also I'm not sure if some other conditions in the game will trigger this (for instance bMainOrderTimer. bAirWeaponCooldown, SpellCooldown are all near the groundweaponcooldown so one of these occurring will likely cause same trigger to be detected). Also if you attack and then instantly move it will not actually fire but still count as a shot xD so the trigger needs to be looking for some value bigger than 256.

Post has been edited 2 time(s), last time on Jul 11 2009, 8:54 pm by crutex.

Step 1:
Find health of unit you want to know EVERYTHING about.
See the tutorial for help on that.
This will give you an address, for example the first unit's health is 0x59ccb1. This is the whole number, the actual unit health is 0x59ccb0, with 256 "extra precision" making 1 whole life we can see in the game. Zerg units will heal by adding 4 to this number every frame. Once it reaches 256, it rolls over and becomes 1 hp.
Step 2:
Open up the unitnode reference and locate exactly where hp is. Notice that hp is +0x08. What I do is have an excel sheet which automatically lets me input "0x59ccb0" into the hp slot, and it will fill out the rest of the memory map for me. Alternatively, simply add the address of the location you're trying to read to the hp address, then subtract 8. For example, stim timer is +0x115 - BYTE bStimTimer. Add 0x115 to 0x59ccb0 and subtract out 0x08. The stim timer location for the first unit is at 0x59cdbd.
Step 3:
Locate the byte required to read. Deaths reads 4 bytes, on every 0, 4, 8, and C. This means you just have to search for the number if it's on one of these and is a dword. 1, 5, 9, and D are on the second byte, and you have to search for the number*2^8. 2, 6, A, and E are on the third byte, and you have to search for the number*2^16. 3, 7, B, and F are on the fourth byte, and you have to search for the number*2^24.

yeah and here's the map updated with stim detection on the marine

thanks for clarification on step 3 rockz i was wondering about it

Attachments:

I assume you have to convert to decimal for the actual trigger.

yes.

edit: attached map. leech mana from enemy player with dt strikes
make leveling by killing 2x unit with dt
detect storming on the dt

Attachments:

Post has been edited 7 time(s), last time on Jul 12 2009, 5:11 am by crutex.

You know, you could make a stim detection system without using EUDS. Using a DD system, you can have, for example, an 11 HP rine, and always be doing 1 damage to it, and then healing it right after. That way, if the user decides to stim, the rine will die.
It may provide some interference, and the user will likely have to stim more than once for it to go through, but it would work on a decent average basis.

o_O then you would have a dead rine

Right, but you'd be able to detect the dead rine, (aka the rine stimming) correct?
hahaha

OLOL I GOT AN IDEA!!

For burrow detection, wouldn't it make sense to run EUDs off of this, instead of the detection-by-attempting-to-move system? Or is it too complex for that, and I just don't know it?