Well here I am with yet another problem... Sorry for being such a bother

I'm trying to disassemble someone else's mod to figure out how they did something. This should just simply involve extracting the arbiter entry from their iscript.bin, but the latest IceCC fails to do so. It reports "unknown opcode 0x54 read at 0x004d (block start: 0x0000004d)". As far as I know this is a very old mod, from the days of cwads and stargraft (see my previous post ). I can probably figure out what I need to do without looking at this script, but it would definitely be helpful. I've attached the problematic iscript.bin... Thanks!

Attachments:

If it's that old, then it was probably made with ICE, which is why IceCC can't open it. I don't think there's any way to view ICE iscripts in IceCC, but I might be mistaken, as I've never tried it.

Oh right, I completely forgot about ICE. I'll see if I can open it with that. Thanks!

Interesting.... it seems this iscript uses the "Terran Lift-Off" animation set even though it's a protoss unit (not a lift-offable building afaik). Also, under that "Terran Lift-Off" header, there's a bunch of entires called "Unidentified Op > 0x41. See Readme file. Assuming len=1" as well as a couple other entries that don't make much sense. (i.e. turning the graphic 119 units clockwise and playing frame 29268.) Also, the script uses animation sets "Unknown 7" and "Unknown 8". Does anyone know what those headers are for and what they translate to in modern IceCC language?

Maybe someone more knowledgeable than I could take a look at the script and figure out exactly what's going on with that gobbledegook under the "Terran Lift-Off" header...

I'm curious as to what mod you're taking apart.

IceCC comes with some documents that you can read to identify some of the unknown headers. However, some of them truly are -- I just can't confirm if Unknown 7 and Unknown 8 are really unknown.

Sounds like your iscript.bin is corrupt.

There aren't really any unknown headers. By the way, that Lift Off animation is probably not really Lift Off. I recall that being one of the animations that was mislabeled in ICE and IceCC (could have been lift off in an older version of SC, maybe). Also, there is a certain order for the animation headers by default (though you can rearrange the order in IceCC after decompiling). The order might match up between ICE and IceCC.

Don't have anything to do with ICE. Never use ICE, and don't even bother getting close to it.
It will corrupt anything it touches including your house.

Damnit, I'm not making any changes to the script with Ice, I'm just reading an old iscript to try and recreate the usage of the frames of a unit GRP. The unit has like 300 frames so just looking at the GRP was proving a challenge. The mod is a little grp mod that turns the Protoss Arbiter into a Protoss Tripod. I seriously want to use the tripod GRP because it fits what I need. Odd that Ice would corrupt the script just by opening it... Oh well I guess I can't go that route. I'll figure the rest out by looking at the damn frames >.<

Eh, it's not necessarily even 'corrupt'. The one time I complained that ICE had corrupted a file of mine, I found out after a couple hours' work what I had fucked up. And I used ICE a lot ( doing pretty much as much as I could with it, given that it can't handle a nice assload of fun opcodes, including such things as spr/imgol/ul... )
More likely, if I understand iscript.bin and ICE/IceCC correctly ( my guesses being entirely based on inference, so I'm not gonna trust 'em much ) , there's an opcode in the script which is actually of a different bit length than ICE's reference file, so everything after it is read incorrectly.
But the end-result is the same: You can't read it, possibly unless you make some changes to opcodes.ini, though even if that works it'd probably be too much trouble. And, of course, there's always the possibility that it is, in fact, corrupt.

No, ICE definitely does corrupt files. Not only does it do what you said (incorrect opcode specs, which result in invalid loading and compiling, which results in a "corrupt" file), but it does a lot of stuff that is just retarded. Do not use ICE. Even if you "think" its not corrupting your file, it is, and it will get worse with every save you make (probably).

There's no good reason to use ICE anyways, when you have IceCC and PyICE, both of which have more functionality and don't corrupt your iscript.

Yes yes I understand that you shouldn't use Ice... Except the iscript I'm trying to view won't open with IceCC (I admit I haven't tried PyIce). I was told this was probably because the script is in some old format that was originally edited with Ice. If there's anything I can do to make Ice able to read this seemingly corrupted animation set, I'd love to hear about it.

GUI for modifying the scripts themselves. Graphic and sound previews.