It is just a table of 12 ints that contain [i]pointers[/i] to the select unit node(s). I think it was in the Maplantis topic that I posted all the addresses... (No where do you actually see a specific 0-1699 number that I am aware. It is always a pointer) Found it: http://www.staredit.net/maplantis/index.php?post=63271 And Doodle told me that they indeed are always 336 bytes.

It is just a table of 12 ints that contain pointers to the select unit node(s). I think it was in the Maplantis topic that I posted all the addresses... (No where do you actually see a specific 0-1699 number that I am aware. It is always a pointer)

Found it:
http://www.staredit.net/maplantis/index.php?post=63271
And Doodle told me that they indeed are always 336 bytes.

but if i want to know what I have to write in the trigger, what operations I have to do????

but if i want to know what I have to write in the trigger, what operations I have to do????

For units you want Exactly, unless you want a group of units to trigger it... It's the same as any other trigger.

For units you want Exactly, unless you want a group of units to trigger it... It's the same as any other trigger.

[quote=I)eathBringer]I have patched the data folder of starforge however I've made it with uberation2 :P[/quote] [quote=DT_Battlekruser] [color=#b5b5ff]Starforge is the only complete editor that [i]can[/i], in fact, be used to trigger EUDs. Please don't spread mistruths about it.[/color][/quote] Never knew that, ty for correcting me. The fact remains that MY starforge can't handle EUDs. Care to elaborate how? I don't feel like looking, and it'd be nice to have in a relevant thread. On a sidenote, I knew there was something starforge did better than SCMDraft...

Quote from I)eathBringer

I have patched the data folder of starforge
however I've made it with uberation2

Quote from DT_Battlekruser

Starforge is the only complete editor that can, in fact, be used to trigger EUDs. Please don't spread mistruths about it.

Never knew that, ty for correcting me. The fact remains that MY starforge can't handle EUDs. Care to elaborate how? I don't feel like looking, and it'd be nice to have in a relevant thread.

On a sidenote, I knew there was something starforge did better than SCMDraft...

Go into data files and edit Conditions.lst... find the line: [code]Condition Deaths(Player Player, Comparison Comparison, Number Number, Unit Unit)[/code] and make it: [code]Condition Deaths(Player Player, Comparison Comparison, Number Number, Number Unit)[/code]

Go into data files and edit Conditions.lst...
find the line:

Code

and make it:

Code

[QUOTE](No where do you actually see a specific 0-1699 number that I am aware.[/QUOTE] [color=#b5b5ff]Then how does Starcraft get unit-specific data, such as current health percentage or kill count?[/color]

Pointers. You may be able to find a specific ID by subtracting the pointer from the top of the pointer table and then dividing that by 366... but SC uses pointers all over the place. (You even have pointers that point to even [i]more[/i] pointers!)

Pointers. You may be able to find a specific ID by subtracting the pointer from the top of the pointer table and then dividing that by 366... but SC uses pointers all over the place. (You even have pointers that point to even more pointers!)

[color=#b5b5ff]If the pointer is to the units table (DAT data), how do you get the local ID reference? You just said that the local ID is not the pointer..[/color]

I said there is no real 0-1699 number... "DAT data"? You mean .dat files? I am talking about the unitnode where all the unit information is stored. And doing that math stuff I posted is useless, I was just saying if you REALLY wanted a 0-1699 pointer. :P If you want to find a pointer to a unit, find its current HP and then subtract 9 from that address. If you want to explore it first hand, you can play with the selection addresses I linked to a few posts back... You can look at what it uses for unit references.

I said there is no real 0-1699 number... "DAT data"? You mean .dat files? I am talking about the unitnode where all the unit information is stored.
And doing that math stuff I posted is useless, I was just saying if you REALLY wanted a 0-1699 pointer.
If you want to find a pointer to a unit, find its current HP and then subtract 9 from that address. If you want to explore it first hand, you can play with the selection addresses I linked to a few posts back... You can look at what it uses for unit references.

[color=#b5b5ff]So it points to the ith index of the local-ID table, where i is the localID of the selected unit, no?[/color]

I suppose... as long as [i]i[/i] is in increments of 336... It points to the atual unit node (which contains all the unit information).

I suppose... as long as i is in increments of 336... It points to the atual unit node (which contains all the unit information).

[color=#b5b5ff]The indexes of the local-ID table can be whatever memory offsets - but my point is the pointer is to the local, not unit ID table.[/color]

EDIT -Nevermind.

EDIT -Nevermind.

I have always the smae problem: how to detect selected units I have memory offset, unit ID and player but how can I find the value for a specific unit like a firebat(ID=32)?

I have always the smae problem: how to detect selected units
I have memory offset, unit ID and player but how can I find the value for a specific unit like a firebat(ID=32)?

Where are the red 0s when you put it into eudtrig?

Where are the red 0s when you put it into eudtrig?

There are 4 series of red 0s (4 bytes)

There are 4 series of red 0s (4 bytes)

Oh jesus, this just got harder. Read the page again, you'll note that farty and DT are talking about what number you need to use (the local ID). Study Doodle77's map some more.

Oh jesus, this just got harder. Read the page again, you'll note that farty and DT are talking about what number you need to use (the local ID). Study Doodle77's map some more.

[quote=DT_Battlekruser][color=#b5b5ff]The indexes of the local-ID table can be whatever memory offsets - but my point is the pointer is to the local, not unit ID table.[/color][/quote]I'm getting really confused now... what the hell is a local-ID table or a unit ID table? [quote=I)eathBringer]I have always the smae problem: how to detect selected units I have memory offset, unit ID and player but how can I find the value for a specific unit like a firebat(ID=32)?[/quote]You can check to see what [i]unit ID[/i] is selected, but if you have a mixed group it will show 244. I can't remember the offset off the top of my head, but it is not shared (go look in the changing unit portrait topic for the map that I have it in.) Also the number of red 00s in EUDTrig is for when you use Object ID/Len. It shows you how the bytes appear in the int.

Quote from DT_Battlekruser

The indexes of the local-ID table can be whatever memory offsets - but my point is the pointer is to the local, not unit ID table.

I'm getting really confused now... what the hell is a local-ID table or a unit ID table?

Quote from I)eathBringer

I have always the smae problem: how to detect selected units
I have memory offset, unit ID and player but how can I find the value for a specific unit like a firebat(ID=32)?

You can check to see what unit ID is selected, but if you have a mixed group it will show 244. I can't remember the offset off the top of my head, but it is not shared (go look in the changing unit portrait topic for the map that I have it in.)

Also the number of red 00s in EUDTrig is for when you use Object ID/Len. It shows you how the bytes appear in the int.

Alls I know is that in Doodle's map, he's got 5885072 deaths for the marine, 6455936 deaths for the firebat, 6455600 for the ghost, 6455264 for the zealot, and 6454928 for the civilian. Considering the ghost is unitid 1, marine is unitid 0, and firebat is unitid 32, it wouldn't make much sense to go specifically by unitid. The ghost/bat/zeal are all off by 336, but the civ and rine are way off, and I think it's because of the way they were placed on the map. I know that when I was checking unit hp, there was also a huge difference in the units' EUD.

Alls I know is that in Doodle's map, he's got 5885072 deaths for the marine, 6455936 deaths for the firebat, 6455600 for the ghost, 6455264 for the zealot, and 6454928 for the civilian. Considering the ghost is unitid 1, marine is unitid 0, and firebat is unitid 32, it wouldn't make much sense to go specifically by unitid. The ghost/bat/zeal are all off by 336, but the civ and rine are way off, and I think it's because of the way they were placed on the map. I know that when I was checking unit hp, there was also a huge difference in the units' EUD.

[quote]I'm getting really confused now... what the hell is a local-ID table or a unit ID table?[/quote] [color=#b5b5ff]A local-ID table will contain up to 1700 entries pertaining to individual instances of a unit. The data local to a unit's instance includes such things as its current HP percentage, current shield percentage, and so on. The Unit ID table holds all the data loaded from the units.dat file, and essentially contains unit data (think [font=courier][b]static[/b][/font] fields of a class). Unit data would include total HP count, weapon ID, and such. I don't actually know the bit-structure of Starcraft's RAM, but all of that data must be stored somewhere, and I know from the offsets I have seen that there exists a table solely of unit (static) data, because that was what everyone was editing with EUD actions. [quote]Considering the ghost is unitid 1, marine is unitid 0, and firebat is unitid 32, it wouldn't make much sense to go specifically by unitid. The ghost/bat/zeal are all off by 336, but the civ and rine are way off[/quote] Anything you are finding should be in the local ID table, which has [i]no relation[/i] to the unit's Unit ID. The position of a instantiated unit within the local ID table will depend on its Local ID, assigned at creation based on when the unit is created.[/color]

Quote

I'm getting really confused now... what the hell is a local-ID table or a unit ID table?

A local-ID table will contain up to 1700 entries pertaining to individual instances of a unit. The data local to a unit's instance includes such things as its current HP percentage, current shield percentage, and so on.

The Unit ID table holds all the data loaded from the units.dat file, and essentially contains unit data (think static fields of a class). Unit data would include total HP count, weapon ID, and such.

I don't actually know the bit-structure of Starcraft's RAM, but all of that data must be stored somewhere, and I know from the offsets I have seen that there exists a table solely of unit (static) data, because that was what everyone was editing with EUD actions.

Quote

Considering the ghost is unitid 1, marine is unitid 0, and firebat is unitid 32, it wouldn't make much sense to go specifically by unitid. The ghost/bat/zeal are all off by 336, but the civ and rine are way off

Anything you are finding should be in the local ID table, which has no relation to the unit's Unit ID. The position of a instantiated unit within the local ID table will depend on its Local ID, assigned at creation based on when the unit is created.