With regards to what I said on Page 9 in this thread:
Writing to SC's memory with extended units!, Aka neoEUDs.I am searching for the specific extended units which edit the unit ID of another unit, i.e. to create stuff like the SCV that shoots lasers (wraith weapon)
I hope that this might contribute to some kind of sticky'd Extended Unit memory writing database in the near future.
Thanks to Farty's EUD DB I have been running jjf's Eup Test.exe on this specific target.
The settings I am using in Eup Test are:
First Unit ID: 1925 (planned to go up to 13462)
Player ID Range: 223 only (223-223)
The idea is to get to the point where a large number (or at least a dozen lets say) of units in the game can be given alterations. Then some neat maps could be made
Thanks to jff28 again for this equation:
Address edited (decimal) = 48*UnitID + 4*Player + 5808992 The Unit structure is 336 bytes. It turns out that every Unit ID field in SC's memory is 336 / 48 = 7 Unit ID changes apart in memory.
Working from the known values of Uid 3900, Pid 223 for the in-game Unit ID field of Unit Index 1367, I have created a target list for use in Eup Test. (See attached spreadsheet file)
Ofcourse, since Eup Test cannot yet be told to skip certain addresses or follow some pattern, it has to do every unit ID. That's around 11K Tests. I have done 2 nights so far where I get it running and go to sleep, and I have 4500 tests done. (see attached text file)
Once I have the whole range of 1925 to 13462 tested, I intend to make a little program which will give me a revised text file containing just every 7th result, the specific targets I seek.
Attachments:
None.
I don't have a complete list yet but there doesn't seem to be much point in making one.
My findings so far have been villanously bad. Almost ever Unit ID i test is either a crash which EupTest somehow didn't pick up on, or the unit cannot die, or the unit doesn't appear in game, or the unit is a rock sprite and you crash when you try to attack it, etc.
Here's what I have so far:
Index 1367, Unit ID 3900, Player 223. Comment: The Original unit not discovered by me
Index 1368, Unit ID 3900, Player 139. Comment: Player 139 is not an Enemy. A splash damage such as Infested Terran can do the trick.
Index 1369, Unit ID 3886, Player 223.
Index 1370, Unit ID 3886, Player 139. Comment: Player 139 is not an Enemy. A splash damage such as Infested Terran can do the trick.
Index 1371, Unit ID 3872, Player 223.
Index 1372, Unit ID 1872, Player 139. Comment: Player 139 is not an Enemy. A splash damage such as Infested Terran can do the trick.
None.
My results so farEdits to EupTest will be coming after units in Chkdraft - will have the two working together for much more flexible testing options soon.
My findings so far have been villanously bad. Almost ever Unit ID i test is either a crash which EupTest somehow didn't pick up on, or the unit cannot die, or the unit doesn't appear in game, or the unit is a rock sprite and you crash when you try to attack it, etc.
The conditions in EupTest are
extremely generous, the unit is in the fog, in the exact center of a 256 by 256 map, and no attempts are made to kill or give the unit - so most of the units it picks up won't be particularly useful.
TheNitesWhoSay - Clan Aura -
githubReached the top of StarCraft theory crafting 2:12 AM CST, August 2nd, 2014.
Nice results list.. any reason you use Player 2 though? I was using Player 223 because that hits the Unit ID's in the Unit Table
EDIT: By the way not to complain about your program, it is EPIC i mean wtf, it automatically creates a map, that alone is beast, nevermind somehow detecting if the Starcraft process has ended in Task Manager or something like that.
None.