SWU question

[Nyamaiku]

maybe its just some bad luck i guess...or it could have been that i wrote next: 100 during that time.

[Silverthorn]

Actually last time I tried that state to delete something it didn't do anything, never tried/used it again - I still don't know how it ended up on the main site.

No idea either, but it does delete objects. Slapped 9998 into Davis's last standing frame and gone he was.

For the record, though, this state does exist in the exe:

ASM-Code: Address Hex dump Command Comments 0041E66D . 81BC02 AC0700 CMP DWORD PTR DS:[EAX+EDX+7AC],270E 0041E678 . 75 05 JNE SHORT 0041E67F 0041E67A . C6443B 04 00 MOV BYTE PTR DS:[EDI+EBX+4],0

The last line is only called if a frame is at state 9998 (or 270e in hex). Then, much magic happens, with many loops running from 0 to 400 and (after about 8k steps), the procedure returns and the character is gone. Somebody who is more bored may find out the exact logic behind it :p

[YinYin]

I'd be more interested whether an undefined next or next: 1000 goes through the same process or not.

[Silverthorn]

"next: 1000" doesn't seem to be explicitly listed. A different value inside the DC-code (i.e. 998) does not make a difference -- it deletes the characters as well.

Something strange is that the invisibility-nexts cannot be found either. I expected the range-values to be findable but they seem to be actually calculated somewhat dynamically...

[Azriel]

"next: 1000" doesn't seem to be explicitly listed. A different value inside the DC-code (i.e. 998) does not make a difference -- it deletes the characters as well.

Something strange is that the invisibility-nexts cannot be found either. I expected the range-values to be findable but they seem to be actually calculated somewhat dynamically...

Perhaps search for 199 or 200 (<= 199 or < 200) - could be a subtraction before comparison. But tangential to original question



Azriel~