From: tvw@cray.com (Tom Van Wormer)
Subject: Re: Ultima 7 walkthrough/hint sheet wanted.....
Organization: Cray Research Superservers Inc., San Diego CA, USA
Date: Sat, 9 Jan 1993 07:21:55 GMT

	Wiz 7 bash-thru.

	For those of you who have greater interest
in hacking/exploring the Dark Savant vs. enduring
the relentless combat, the following is offered.

	I recommend that devout RPGr's avoid it,
because it can strongly diminish game satisfaction.

	Do not read beyond here, if you desire to
slug it out.  STOP.  

	Fine.

	Archive the saved game that you wish with to
tamper with if you're going to try this stuff.  Think
again about what you want from this RPG.  Once you are
into this, the color of the game changes significantly.
Your original game will not be lost, but it might as
well be.

	You'll need a sector editor.

	In a saved game file, the hex information 
regarding the first equipped or held item starts at 40
(hex) bytes after the beginning byte of each character's
name, and the information regarding this item comprises
0x0C (hex) bytes per item.  Succeedingly held items use
an additional 0x0C bytes per item.  The items are in the
same order as the game display.  The beginning two bytes
of each item's 12 byte field spell out the look-up
location (in scenario.dbs) of the characteristics of that
item that the character holds.  These two bytes are a hex
pointer into scenario.dbs.
	Scenario.dbs contains all the power/goodies.
	If one wishes to enhance one's material, then one
should examine scenario.dbs with a sector editor; see the
ASCII goody of interest, and note it's hex byte displacement
from the beginning of the scenario.dbs file.  When the item
of interest is found in scenario.dbs, then, the procedure for
equipping a character with that item in a speculatively
modified game save file is as follows:  If the character's
(game save file)) first item, (presumably the one you want
to replace) as displayed under the sector editor, has a
beginning two bytes of 'I', then 'I'can be replaced with
something better from scenario.dbs...

	1.  Using sector editor, find the hex displacement
of 1st character of desired item in scenario.dbs.  This is
'x'.

	2.  Subtract 0x380 hex from 'x', yielding 'y'.

	3.  Divide 'y' by 0x48 hex, yielding 'z'.

	4.  Using sector editor, modify first two bytes of
twelve byte field of 'I' in speculative game save file to
incorporate hex number 'z' just computed.  First byte is
lsbyte, second byte is msbyte.

	Now, then, your saved game character has the item.
The item is not equipped; this can be done via game software.
You do not yet have item's video image.  A little bit more
figuring will net one the video image bytes in the 12-byte
field.

	Traits may be augmented by subjecting bytes 0x170
hex through 0x177 hex of a character's saved game file data
space with the experimental value 0x13 hex.  This mod yields
a strength of 19 for all 8 mains; sufficient in party mode
to bash down any standardly keyed door.  In New City, this
method opened -ALL- keyed doors for me; no keys required.
More strength is available (run the values up to 0xFF, see
what happens) but my characters didn't need such.

	Skills may be boosted by modifying 32 bytes starting
at 0x178 hex in the character image.  If these bytes are
taken to 0x64 hex, (the maximum value) then one's party
ends up hauling balls in an 18-wheeler.  Few monsters,
even those of great power, can see, let alone hit a
member of the party in combat.  Swim, climb, etc. are
cleaned going away.  One can roam with impunity.  One
or two monsters out there might still cause a problem,
though.

	The best thing I found is this: the mana stone
(magic recharger), when first encountered, has but few
charges, and then dies.  A mana stone with infinite
recharges is available... use the following 12-byte hex
code: 22-01-1E-00-0E-74-00-80-00-00-00-00 to modify an
item in a spell-caster's area in the speculative game
save file..  This item speeds up the game.


Disclaimers:  My grandson voted against this while he
was cleaning super mario bros, in 3 hours, again.
tvw@cray.com