Users browsing this thread: 1 Guest(s)
Restoring Woolsey in credits

#1
Posts: 6
Threads: 2
Thanks Received: 0
Thanks Given: 0
Joined: Oct 2019
Reputation: 0
Status
None
So, I've been using FF3usME, spritesheets, and a series of ips patches to make a romhack for personal use; sprite edits, script edits, bug fixes, you know the drill.  So far I haven't had to use any hex editing, but somethings come up that I can't find a tutorial for.  I wanted to use yazoo's title screen restoration patch, but it also restores the credits which cuts Ted Woolsey out.  I know it's a small thing, but after poring over Legends of Localization and various other scripts I've come to a much greater appreciation for him and his 30 day marathon.   It doesn't sit well with me to leave him uncredited.  The title screen tutorial on the wiki appears to be for the splash screen immediately preceding the title screen - e.g. the one that is just a static image and not the scripted growing letters, appearing magitek walker, etc.  I'm okay with yazoo's patch cutting that out, and apparently it only takes one value change to skip it?

Anyway, I know this is probably trivial for a lot of people on this forum, but rather than being handed a .ips file I do want to experience at least a little of this part of the process.  If it's relevant, I grabbed WindHex32 to use simply because it is described as a hex editor designed for SNES rom editing.  Comparing the base ff3US 1.0 file and a patched file tells me which bytes are changed, but I can't tell what constitutes one "group" of hex values.  What I am requesting here is instructions on how to track down which byte changes alter the splash screen, the animated title screen, and the credits.  Alternatively, just following simple step by step instructions to fix it would also work so long as what the processes involved are explained.  I might wind up needing simple instructions anyway... I don't know how intuitive this task is.  Thanks for being patient with my somewhat self indulgent request.
  Find
Quote  

#2
Posts: 6
Threads: 2
Thanks Received: 0
Thanks Given: 0
Joined: Oct 2019
Reputation: 0
Status
None
Oh, I see this post went through after all. I didn't notice that new accounts should be activated before posts go through and asked this question on the Discord. I received a satisfactory reply thereply and also because of what I mentioned his account became activated. But, I don't need an answer now since I got one. This thread can be deleted.
  Find
Quote  

#3
Posts: 116
Threads: 5
Thanks Received: 8
Thanks Given: 24
Joined: May 2013
Reputation: 0
Status
None
I would not mind adding this back in if its removed. I'm curious myself.


Experience is the benchmark to maturity.

Final Fantasy VI - Ted Woolsey Uncensored Edition:
http://www.romhacking.net/hacks/1386

Final Fantasy IV - Namingway Edition:
http://www.romhacking.net/hacks/2337
  Find
Quote  

#4
Posts: 6
Threads: 2
Thanks Received: 0
Thanks Given: 0
Joined: Oct 2019
Reputation: 0
Status
None
Unfortunately I wasn't able to do this even with the discord reply, mostly on account of I don't actually know how to hack.  I've only managed changes that can be handled with FF3usME.  Sprite edits, script edits, IPS patches, etc.  It sounds like hacking this would require decompressing and compressing the japanese version of the game to compare and it seemed really daunting as a first task.  Though, I really should learn some basics, considering that I can't tell which of my ips patches are conflicting and causing problems, there all I'm using is the LSA - Patch checker.  I don't really know how I would debug throwing some patches that add new features onto the CV compilation hack, and since so MANY little things get changed by the CV Bugfix compilation I don't think I will really be able to get it working.  Ah well, I'm losing a bit of motivation for this anyways.
  Find
Quote  



Forum Jump:

Users browsing this thread: 1 Guest(s)


Theme by Madsiur2017Custom Graphics by JamesWhite