Since my mod features Keen with pogo at the start of the game in the worldmap using a known patch, I don't need that stupid field that tells you if you've found the pogo or not.
So, any patch to avoid drawing it? Or, what else can be done with it (useless or not)?
Yet Another Patch Request: Status screen, pogo field
- Shadow Master
- Posts: 129
- Joined: Fri Oct 20, 2006 3:14 pm
- Location: Santiago, Chile
- Contact:
- Freeyorp101
- Posts: 159
- Joined: Thu Nov 24, 2005 2:12 am
- Location: New Zealand
Oh. That works also, though you do it a little differently.
These patches work with the status screen patch of Andy's, I haven't got around to figuring out the 'normal' ones, and may never do so.
These patches work with the status screen patch of Andy's, I haven't got around to figuring out the 'normal' ones, and may never do so.
Code: Select all
#With status screen patch, don't show pogo tile.
%patch $1047 $EB $26
#With status screen patch, don't show items tiles
%patch $0F07 $EB $26 #Joystick
%patch $0F2F $EB $26 #Battery
%patch $0F57 $EB $26 #Vacuum
%patch $0F7F $EB $26 #Whiskey
- Freeyorp101
- Posts: 159
- Joined: Thu Nov 24, 2005 2:12 am
- Location: New Zealand
- Shadow Master
- Posts: 129
- Joined: Fri Oct 20, 2006 3:14 pm
- Location: Santiago, Chile
- Contact:
I'll use the overwrite-it-later method. Why?Freeyorp101 wrote:With the status screen patch, it would probably be best to just change the existing bytes (the first two in the pogo section) rather than overwriting it later in the patch file.
1) I'm not very organized, so a time may come in which I might not be able to understand wtf I patched in.
2) If someone borrows a patch from the mod, he/she oughtta know what modifications were made on the same patch, so I write it a line after the main status window patch.
3) In the strange sceneario of someone running the mod on a very, very, very old machine, it shouldn't take more than 2 extra seconds to overwrite an already accessed & written memory location. :)