I know SCMDraft 2 allows for EUD's, and thus far I have not had a problem... but my UnitID is 1 number too long and I can't fit it.

I cannot get StarForge to work at all, so please don't suggest this.

I seem to re-call a program that let you open the triggers, edit them in a notepad style and save them directly to the map?

Thanks for your help

Download the new version of SCMDraft.

Use the "Memory" condition.

Multiply the UnitID you want to make by 12, and add that to the player number (zero based, ie player 1 = 0, player 12 = 11). Put this number into the condition.

Another alternative is to open the map up in winmpq, extract the scenario.chk, and hex edit the map. Search for "TRIG", and that will give you the trig section. Scroll down to the location of the unitID you want (use something easy to find like CC or something) and change it. Save the chk, and drop it back into the map.

Here is a link to the post with the link of the newest version:
http://www.staredit.net/topic/6517/#135388

I have SCMDraft 2, and I was using the memory thing.

So say I have the trigger

Memory at death table + -332109 exactly -330120

( This is not my real numbers, since I don't re-call what they are atm )

But I would multiply -330120 by 12 then changed the -332109 to that number?

If so, what would the -330120 be?

I'm confus

Let's say you have a working EUD, but for some reason you used an old version of EUDTrig which gives player 1-12 and extended units.

Player 8 (0x7)
UnitID:125846

To get this into the "Memory" context, you need to convert this into a raw offset, then convert back into an extended player. Player is 4 bytes, UnitID is 4*12 bytes.

Player 8 = 7*4 = 28
UnitID:125846 = 125846*48 = 6040608

Now, add them together: 6040608 + 28 = 6040636. This is the raw offset. Now we want to get it back into an extended player. 6040636/4 = 1510159.

The memory trigger would use that as the offset. That's how I understand your problem, since you specifically mentioned "Unit ID number is too long".

Now then, there's no real reason to use EUDTrig anymore, since it's easy to find out the offsets. Since you're suggesting using negative numbers, I can only assume you lied (or don't know what a unitID is) in your first post, and are trying to read before the death table. To do that you need to have a negative player number. The formula is like this:

(Memory Offset you want to read - Death Table location)/4 = Player number.

As a note, "Memory" is actually just "Deaths(Playernum, quantcompare, quantnum, 0 (Terran Marine))". It's not worded very well in SCMDraft.

The first number is the LOCATION of the memory you want to read, and the second number is the actual number. If you are reading the first byte, and it's normally followed by 3 bytes of zeros, you just use the number. If it's the 2nd byte, you use the number*256.

How do you "hex" a map?

You open it up in a hex editor

Such as what?

The only thing I have thats an advanced text document program is NotePad++

I'll search though, if all else fails could you link me to one please?

Thanks.

*** EDIT ***

Okay, I have a program called HxD and it opens it and such, and I found a trigger I put in but I don't see how it ='s the number I put into the Memory triggers.

This is the line it gave me when I searched for the commented trigger



Post has been edited 1 time(s), last time on May 6 2009, 2:15 am by Oo.DaMeiN.oO.

• Make a new map
  
• Make a trigger with the memory condition, using 0f0f0f0f or something as the number (convert that into decimal)
  
• save the map
  
• search for "trig" in a hex editor such as Hex workshop, or XVI32
  
• Look for "0f0f0f0f"
  
• note where that is in relation to the other numbers around it
  
• change the number to the correct amount, remembering it's little endian, so 01234567 in hex would be input as 67452301.
  
• read up on scenario.chk format to see what the rest of the numbers mean.
  
• realize that you really don't need to do this, since scmdraft should be able to handle it.