Hello folks, UMS mappers, map tool makers, EUD nerds!


I've tried and research about the status of EUDs in newer versions that 1.16.1 but couldn't find out what people mean with EUD being broken. It is understandable enough that the addresses change and you have to find the death table offsets all over again. So I've tried to use CheatEngine to do it myself.

I experimented with supply values of all three races:
1. There are values in Starcraft's memory I found that equal to the shown supply values in the in-game interface that change accordingly.
2. But these values have different addresses each game so it's impossible to use them as a reference in UMS mapping.
3. As it is stated in the SAN wiki, the in-game shown supply values are actually the internal values divided by 2, but I could not find any addresses with this pattern (I checked every value type and all races/supply values).
4. Assuming that the values I DID find (see my 1st point) are still calculated from the real internal supply values (I guess for String formatting or whatever) I can only deduct that these values I got are pretty useless.
5. So I've tried to track what writes to the addresses I found via Debugger in CheatEngine but then Starcraft crashes immediately - I suppose as a security measure against hacks.

So what gives? Is there now no actual way of accessing the memory through EUDs? Or did I do something wrong and the values I tried to find are out there but you "just" need to do some trick to find them?


Cheers!

I haven't delved into post-1.16.1 overflows at all, but a couple points about them in general.

EUD as a concept is a very hacky thing. The two main reasons they ever gained any popularity was 1) a client that did not change for a long time (i.e. no patches) and 2) the use of static memory addresses.

So even if one persisted enough to recalculate offsets for each patch, there's nothing one could do about the code changing to use dynamic memory addresses. A lot of effort for naught.

This is for EUD Conditions, not Actions. Actions will never be enabled on mainstream StarCraft.

So in your particular case, supply values they may or may not be held statically somewhere, but the motivation for investigating is pretty low.

Yes, I should have specified that I was talking about EUD Conditions to use in unaltered SC.

So I've found some addresses with Roy's tutorial that have supply values, but they behave like dynamic addresses. As I see it, there is no way to predict what specific address will be used for these values. A shame

Not to mention maps created with EUD are not player-centric at all.
1. EUD maps will not be playable on other versions.
2. EUD maps will not be playable on Mac.

These are not good experiences from a player's perspective.

To be fair, we had at least 2 cross-platformed EUD maps (EUD conditions->global actions) in 1.16

Can you still display leaderboard deaths for units by displaying kills of extended units (leaderboard kills of unit 229 should be deaths of terran marine, etc...)?

I don't think many useful EUDs change from version to version, as long as they keep the same structure.

The gas counters were broken in desert strike, so I assume they were changed if not restricted.

Good news it still works with the latest (1.20.3.2678 as of now) patch. Terran Marine deaths are UnitID:228 in Classic Trigedit, probably because of 0-based?

Post has been edited 1 time(s), last time on Aug 27 2017, 3:06 pm by Wormer.