Opened 15 years ago

Closed 15 years ago

Last modified 2 years ago

#8446 closed patch

A couple new v6 vars for descumm

Reported by: SF/albeu Owned by: sev-
Priority: normal Component: Tools
Keywords: Cc:
Game:

Description

This patch add a couple variables used by the v6 engine. You can find some description about these variable there: http://alban.dotsec.net/Projects/Scumm6Variables (most are in the GUI section near the end).

However as most of these are arrays a small extension was need. Names will be looked up for arrays. While at it i also added a new argument type for the array ops (dim and shuffle) so that name can be printed there too. It can probably be used on some ops for the other versions but i didn't looked into that.

As a little bonus i also included a new unknow op :) Some night ago i was bored so i tried out all op code marked as invalid in scummvm. I found a couple that seems like noop (take no arg, doesn't seems to do anything), a disabled function (print that it's disabled :) and that one. With some try i found out what it take for argument (one value from the stack and a string) but i have no idea what it does.

It seems the file size check change (from yesterday's patch) was forgotten. It's mentioned on the log but no change on descumm-tool.cpp. So I resubmit it again but with a little improvement to also check the size for those blocks that need more than 9 bytes.

Ticket imported from: #1235252. Ticket imported from: patches/551.

Attachments (1)

descumm_v6vars.diff (5.0 KB ) - added by SF/albeu 15 years ago.
Patch againts anonymous cvs 2005-07-09

Download all attachments as: .zip

Change History (6)

by SF/albeu, 15 years ago

Attachment: descumm_v6vars.diff added

Patch againts anonymous cvs 2005-07-09

comment:1 by cyxx, 15 years ago

Just for information, from the HE interpreters, opcode 0xC1 is just a trace opcode. It pops from the stack a string and a trace level (the other way around than LA interpreters apparently).

comment:2 by cyxx, 15 years ago

I just had a quick look at moondemo which has been compiled with windex enabled. To complete my last comment, when the interpreter executes the opcode 0x1C, the 'trace level' is compared with an identifier which can be modified at runtime. If they are equals, the 'string' which seems to contains a list of windex commands is parsed and commands are executed.

comment:3 by sev-, 15 years ago

Commited. Thanks.

comment:4 by sev-, 15 years ago

Owner: set to sev-
Status: newclosed

comment:5 by digitall, 2 years ago

Component: Tools
Note: See TracTickets for help on using tickets.