I'm really quite surprised that apparently no one on this site (or at least interested in mapping with the skills to do this) has access to a mac computer anywhere.

Anyway, I'm going to look into this more when I get home:
http://www.redmondpie.com/how-to-install-os-x-snow-leopard-in-vmware-windows-7-9140301/
http://wiki.osx86project.org/wiki/index.php/Vmware_how_to

Seems like this should be an easy way to get it sorted quickly. I seriously have doubts that your law-school friend will be able to help us much.

Post has been edited 1 time(s), last time on Oct 17 2011, 8:54 pm by Lanthanide.

Regarding synchronization; basically a player will drop if that player's EUD conditions can be fulfilled on their client, but not others. For example: player one has screen coordinates that correspond with an EUD that the other players do not have, then, as the actions on player one's game are carried out, he will drop from the game while the other players continue playing. Correct?

Yes, he will drop from the other players, and the other players will drop from him.

If two people had their screen coordinates in the correct position for the EUD at the same time, they would drop from the other players, but they would not drop from each other. It's the same scenario as I described for the Mac vs PC players.

Oh goody. I can't wait to try it out!

If I had a mac I would be able to port BWAPI to mac.

This should be updated with Bio's discovery. Or is this thread already on the wiki?

I haven't done anything with that wiki yet. I'm kind of sick. I'm definitely getting over it, though, and should be fine tomorrow.

What should be updated, exactly? I could make an appendix, I suppose, but it seems to be quite a different sect of EUDs (in implementation and limitation), and trying to blend it in with this tutorial would just make the topic more confusing.

This is supposed to be building someone up from no knowledge of EUDs to being able to understand how they are made and how to make them. It is not documentation for every kind of implementation, application and discovery of EUDs (you may have noticed I don't really cover EUD Actions in the tutorial, either).

Amazing job
Where was this is 2003 when I needed it

1. A lot of it didn't exist.
2. Jealously guarded by mapping elitests

This is a very informative and well designed tutorial. Thanks roy!

Edit: Also, I think the new EUD actions deserve their own tutorial.

What you're referring to are known as EUPs, which are a quite different entity. It has been suggested I do the documentation, but there is a certain lack of research on the subject. If there's enough demand I would be willing to compile the information we have now.

One thing you don't make clear in the Text Detection Section is that the Row Addresses don't correspond to the in-game rows at all. The row addresses fill up in order, cycling through from 1-11 (starting on 11). If a player types "-music off", it will display on the lowest row in-game, but it could be inserted into any address row (depending on where it happens to be in the cycle).

Having said that, does anyone know the address for the pointer of which address row the next displayed message will go into next?

I think it's just before the array ... but give me one moment and I will make sure.

0x00640B58.

Yes, that's genuine.

I'll add that clarification when I get the chance. I don't know if it seems obvious, but I spent more time trying to explain why text detection is not a path the average map maker should traverse. Evidently my priorities for that section as a resource were backwards, as I've skimmed over the important detail you mention.

I'll also throw in the pointer address information as well (though its implementation will likely be omitted or skimmed, as it begins to go beyond the scope of the thread; perhaps another appendix is in order here).

In any case, thanks for letting me know. I appreciate it!

I don't have a Memory condition in the list.
Maybe it's my version of SCMDraft? (2_080)

Use the version from this thread: http://www.staredit.net/topic/8307/

EPDs also convert to regular EUDs, so you could use the plain old Deaths condition.

Thanks, got the new version...
but just asking, how do you use the Deaths condition for EUDs.
Because the Deaths condition's syntax is like this:
"Player", "# of deaths", of "unit"