So I'm asking how to give help in mapmaking, specifically on EUDs, and hopefully we can bend the rules just a little to keep this in this forum rather than General Starcraft/T&I.

Loveless requested I make a second EUD Video Tutorial, and since my first video wasn't that great (movie maker sucks), I'm looking for input. I can redo the Health Detection, or I can do something like cooldown detection, a combination of the two, or something completely different.

Teaching EUDs is hard, and a lot of times you just have to learn by example (that's how I learned). Is there anything in particular YOU would like to see, or anything you didn't like about my first video that I can omit (already planning on getting rid of the long ass triggering).

Quote from rockz

So I'm asking how to give help in mapmaking, specifically on EUDs, and hopefully we can bend the rules just a little to keep this in this forum rather than General Starcraft/T&I.

Loveless requested I make a second EUD Video Tutorial, and since my first video wasn't that great (movie maker sucks), I'm looking for input. I can redo the Health Detection, or I can do something like cooldown detection, a combination of the two, or something completely different.

Teaching EUDs is hard, and a lot of times you just have to learn by example (that's how I learned). Is there anything in particular YOU would like to see, or anything you didn't like about my first video that I can omit (already planning on getting rid of the long ass triggering).

It was more of a suggestion, but okay. Anyway, the only reason I said anything about it even though I'm not that interested, is because you seem to be the only one willing to devote your time to make these videos. Your original was very beneficial and I believe that there should be many more videos like it on several other aspects. I have even considered making my own videos on FAQs people have.

I am going to make a list of things people would want video tutorials for in the Ideas section.

Wow that makes so much sense now... I mainly learn by examples, and videos are the best type of them. But I thought everything in that tutorial was great and needed.

I actually learned most of what I know currently by understanding that EUD conditions just use a general formula for reading RAM. Once I could do the math by hand, I felt a lot more confident in writing conditions.

Although, I don't understand how to use this at all: http://farty1billion.dyndns.org/EUDDB/?pg=ref&a=unitnode

Those look like values that you use to read what is happening to a specific units. I assume that for say kill count, you can use this line: +0x8F - BYTE bKillCount. Seems like you'll be adding whatever value 8F is to something and subtracting the kill count. I'm assuming that the -BYTE bKillCount means that KillCount is in the first BYTE which explains why it has a maximum of 255.

Although, I don't know how to construct a condition with this info.

Maybe you could run through using the unitnode table in this video? As for your last video, I thought it was fine. It did a great job of explaining everything. I think the Wiki should be re-written to allow for a more coherent understanding of how to construct EUD conditions, like unit HP.

Also, I've always wondered how you all find these address and label them. How would someone go about finding the address to unit-cooldowns? Would they turn their game speed to slowest, then use ArtMoney? I've never understood how all the addresses we have documented were documented in the first place.

I was thinking I could attempt to describe the unitnode table in a short amount of time, including the HP detection (I use HP detection to know where the unit is anyway).

Loveless, I know it was a suggestion, but I didn't like my first video. it's too long, has terrible graphics, and was sort of thrown together. Hopefully this one will be better.

Oh ya—forgot to mention— it would be very very nice if you made a mobile grid video and a unit direction video. I absolutely do not get those and I would bet many others are the same way.

I too thought that first video was good maybe not "professional" but it definitely helped me out a ton cuz i cud see what u were doing step by step. Maybe a video on unit selection or when a certain unit casts a spell, also is there some type of EUD to detect when a unit casts a spell but it fails to come out because the weapon sprite limit is being reached? If so then that wud be cool.

BTW rockz in ur video whats that first track that plays its really cool

Chekan Winter from Kong in Concert (amazing what he did with such a shitty original) then e3m8 Iron Cathedral.

Imo what's turning a lot of people away from EUDs is just the technicality of it. If you can explain how to get the values to put into SCMD's memory condition without confusion on the part of those whose heads hurt when they try to think about binary, your video will help more.

That said, I need some terms explained to me - mostly having to do with byte offsets (whatever those are) - before I'll really, truly understand how to get the values I need.

I could not agree more on this. I've been pulling out my hair for hours and hours in the passed couple of months trying to figure out how location grid systems work so I can implement it in a game of mine. With 65% of earth's population being visual learners... I think that we could use a few more videos on the topic of EUDs because of their usefulness in map making. (source: http://www.phschool.com/eteach/social_studies/2003_05/essay.html)

GREAT FIRST VIDEO! Altho you may not have liked the appearance of the video and it wasn't exactly aesthetically pleasing, it did however get its point across! Good work, but we need more! Location Grid Systems!


Source: http://en.wikipedia.org/wiki/Offset_(computer_science) ... and yes... I know it's wikipedia... but it's an explanation nonetheless.

In computer science, an offset within an array or other data structure object is an integer indicating the distance (displacement) from the beginning of the object up until a given element or point, presumably within the same object. The concept of a distance is valid only if all elements of the object are the same size (typically given in bytes or words).

For example, given an array of characters A, containing abcdef, one can say that the element containing the letter 'c' has an offset of 2 from the start of A.

In computer engineering and low-level programming (such as assembly language), an offset usually denotes the number of address locations added to a base address in order to get to a specific absolute address. In this (original) meaning of offset, only the basic address unit, usually the 8-bit byte, is used to specify the offset's size. In this context an offset is sometimes called a relative address.

Post has been edited 3 time(s), last time on Apr 16 2010, 9:32 pm by atto. Reason: colour coordination