Which address detects rally points? From a barracks, if that matters any.

Also, is it easily possible to find EUDs myself, for future reference? I saw in Brontobyte's topic below to use ArtMoney, but where do I get ArtMoney? It's not in the DB.

Post has been edited 1 time(s), last time on May 3 2008, 10:09 pm by Impeached.

You can download it off the internet. Search google. It's free. Go to farty's website for eud trig.

I searched google for 'ArtMoney starcraft' and it came up with a bunch of Starcraft hacks.

Also, I've seen people talk about modifying StarForge to support EUD writing..How do I do this?

Artmoney is not for starcraft specifically, it is for many games.

Also you can check out the EUD Database for unitnode reference, or to find addresses.

For the unitnode:

Read farty's latest post in Bronto's topic as well for info on how to use StarForge.

I checked the EUD database, and it doesn't have rally points.
Could you expand on those addresses? They aren't the full ones.

It's in the unitnode (which is in the DB.) You must locate the address in which the unit is stored, and then it will be +(whatever I said) from that. You can do a few things to locate it: trudge through the memory and see if you can identify it (doubt it... I'd even be too lazy to do that), put the current selection group offset into ArtMoney and then read the value when the unit is selected, or you can search for HP and subtract 0x09 from that. Also, this means that the unit must always exist in the same memory (preplaced or placed before anything could differ game-to-game.) For future reference, pretty much anything is in the unitnode that is unit-related. The structure is in the Reference tab.

Just in case you don't know this, these values are 2 bytes and (thankfully) are both in the same Death value. To get the value to test, you do PixelY * 65536 + PixelX. I don't know what you plan on using this for, but you will have to be rather tricky to detect variations in Y without doing ENTIRE pixel rows.

Hey, why not, for a 256x256 map you would just need 67.1 million triggers to cover every pixel.

No, you can detect ranges of X coords on one Y axis.

So.. wouldn't you need around 16,000 triggers?

Well, if you have an "Exact" condition for every 1 pixel, it would be 65536 triggers.
But if you were checking like an (anything) by 8, it'd be 8 triggers if you did At Least/At Most.

Ah right, I missed the Reference button on the menu.

"put the current selection group offset" what's the current selection group offset? I tried the UnitNode number ( +0xF8 & +0xFA), and it came up with nothing.

"Search for HP"? How do I do this? Sorry if I sound like an idiot, but I am completely new to EUDs.

Post has been edited 2 time(s), last time on May 5 2008, 1:26 am by Impeached.

Impeached. For god's sake, look at Brontobyte's topic. It goes into EXTREME DETAIL on how to search for HP. Once you find the offset for the building, subtract 0x09 from it.

Oh god, I am an idiot. I never got your guide, Rockz, because I didn't realize (until now) you have to be in an SC game while doing what it says.

Feel free to shun me. I finally get it (Sort of). haha


*Edit: Starforge doesn't seem to be accepting the EUD condition Unit IDs. I changed conditions.lst, as shown:


For now, I'll just use import .trg.


*Edit2: What do you mean, subtract 0x09? The address I got is 005D36B9, or in EUDTrig 0x5D36B9.

Post has been edited 11 time(s), last time on May 5 2008, 6:30 am by Impeached.

lol.... 0x09h = 9 decimal so don't tell me you're not able to subtract 9 from a large (hex) number that ends with 9 O.o
Use Windows calculator in scientific mode (for hex support) if you're ever unsure. Just keep in mind that 0x is only to show it's a hex number. DON'T try to input it into the calculator. and forget about leading 0s.

Ah, subtracting hex works the same as anything else.

And Starforge not working right?

Did you save the .lst file and restart StarForge? Oh, and make sure that EUDTrig is set to Signed.

Yes to all the above.

Just try inputting any int for the unit ID field. Otherwise I think you can manually edit the LST file.

Quote from O)FaRTy1billion[MM]

Well, if you have an "Exact" condition for every 1 pixel, it would be 65536 triggers.
But if you were checking like an (anything) by 8, it'd be 8 triggers if you did At Least/At Most.

You can't get a square without one condition per pixel-row though. That's the shortcoming of only being able to check the long.