PDA

View Full Version : Opcode meanings


Echo_8
03-14-2006, 5:09 AM
I've been looking at the updated IceCC instructions and I'm hoping someone can clear up the following for me. Some are described in the manual, but those ones are basically called unknown. Others are self-explanatory or can be guessed at by looking at a decompiled iscript.bin, but I want to be absolutely sure.

0x0a: imgol0a
0x0b: switchul
0x0c: __0c (I guess some are still unknowns)
0x0d: imgol0d
0x0e: imgol0e
0x11: indsprul
0x12: uflunstable
0x13: sprol13
0x14: sprol14
0x15: indsprol
0x17: setflipstate
0x23: setspawnframe
0x24: sigorder
0x2b: engframe
0x2c: engset
0x2d: __2d
0x37: changeflspeed
0x3d: sprulnextid
0x3e: __3e
0x41: orderdone
0x42: sprol42
0x43: __43
0x44: dogrddamage

StealthyDeath
03-14-2006, 9:31 AM
http://scu.logicalknot.org/index.php?title=Reference:_Iscript.bin_Commands

DiscipleOfAdun
03-14-2006, 10:06 AM
Yeah, well, as good as SCU is, a lot of the ones he's asking about are the unknown ones.

Here's a quick overview of the really new ones I wouldn't think you'd know:

__0c - hehe, not unknown, it doesn't do anything. Some of the others like this actually do something, I just don't know which ones. Others don't.

uflunstable - don't touch. If you can get it to not crash, I'll give you a cookie. It took me several hours of debugging and comparing asm to see why it crashed until I got it to not crash on me. However, since I know it crashes, that's why the 'unstable' part of the name. It deals with a unique flingy spawning. Really messed up when you attempt to use, so don't.

setspawnframe - deals with the frame the unit is playing when it is created, I think....I don't remember how to make it work, but it does do something like that.

engframe/engset - these are just somewhat nondescript names to say that they deal with engines and either a frame/set

changeflspeed - the value you put as the param will be placed in the units personal flingy.dat speed memory. Umm, there are some uses for it....

sprulnextid - spawns an dependant underlay from the next sprites.dat? Id. I don't remember whether sprites or images, but it is used for the carrier shadow.

That should help explain some of them. The rest are really just the same as they used to be. The SCU list has most of them with a basic explanation.