Jul 25, 2006 at 2:24 PM
Join Date: Jun 18, 2006
Location: Montreal, Canada
Posts: 581
Age: 39
(On a friend's PC; still no interweb at ye old appartment)
I found something that appears to be undocumented about MYD. After some poking through the code, I noticed it was considerably long seeing as it should only branch wether the value is 0, 1, or 2, and set a single value to Quote's direction.
Some further poking revealed it was searching through enemy structures when a value greater than 10 was passed to it. So I started poking through the code and it seemed like it would make Quote face an entity with the ID specified as MYD's parameter so long as it was greater than 10. My debug map had an enemy with ID 1001 so I gave it a shot. Nothing.
Further poking revealed that, stupidly enough, the parameter is placed in cl instead of ecx, so...
When MYD is called, if the parameter is between 10 and 255, it will make Quote face the entity with that ID.
Minor, but interesting regardless.
I found something that appears to be undocumented about MYD. After some poking through the code, I noticed it was considerably long seeing as it should only branch wether the value is 0, 1, or 2, and set a single value to Quote's direction.
Some further poking revealed it was searching through enemy structures when a value greater than 10 was passed to it. So I started poking through the code and it seemed like it would make Quote face an entity with the ID specified as MYD's parameter so long as it was greater than 10. My debug map had an enemy with ID 1001 so I gave it a shot. Nothing.
Further poking revealed that, stupidly enough, the parameter is placed in cl instead of ecx, so...
When MYD is called, if the parameter is between 10 and 255, it will make Quote face the entity with that ID.
Minor, but interesting regardless.