øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=363;area=showposts;start=660e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index3428-2.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=363e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index3428-2.html.zxJ–h^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈà•¤köOKtext/htmlISO-8859-1gzip@øÕköÿÿÿÿÿÿÿÿWed, 11 Mar 2020 07:58:27 GMT0ó°° ®0®P®€§²ð®H–h^ÿÿÿÿÿÿÿÿ(3kö Show Posts - 13375K31C43R

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - 13375K31C43R

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
661
Game Modification Station / Re: New patch: Dead in the Air Bug fix
« on: May 11, 2015, 02:17:27 PM »
When Banon is in the party, your game ends immediately if he dies. However, normally, for this purpose, the game does not consider being Petrified or Zombified as "dead". The Petrified Rebel patch fixes this. This info is included in the readme file.

The reason for multiple patches here is because the normal patch conflicts with the Petrified Rebel patch. Therefore, I have four patches which set some combination of Petrified Rebel and Dead in the Air, all of which can be applied at any time. One patch includes Petrified Rebel, but not Dead in the Air; one patch includes Dead in the Air, but not Petrified Rebel; one patch includes both; the last patch includes neither.

662
Game Modification Station / Re: New patch: Zombie/Rippler Bug fix
« on: May 11, 2015, 01:41:04 PM »
Aha! You were right, it did update Near Fatal status! I'll upload a patch as soon as possible.

663
Game Modification Station / Re: New patch: Zombie/Rippler Bug fix
« on: May 11, 2015, 01:28:35 PM »
Like I say, I haven't actually tested adding 1 HP to see if Near Fatal status is set, so I don't know. The algorithms I've actually added don't have this problem because they set the healing variable, rather than the HP variable. When a character's HP is modified through healing or damage, the game updates the Near Fatal status; what I don't know is if the same is true for manually setting HP. I'm pretty sure that even "weakening" spells, such as Cyclonic and W Wind, update Near Fatal status because they damage entities to within an inch of their lives. Remember, I said I would want to implement the 1 HP solution without actually showing the number "1" for healing. I figure that, when Rippler is called, it would look a little strange to occasionally just see a "1" healing an entity, whereas with the other algorithms that heal more than 1 HP, it actually makes it look more like the entity is being healed for a reason.

664
Game Modification Station / New patch: Dead in the Air Bug fix
« on: May 11, 2015, 01:18:24 PM »
Hi! So, this is another bug fix patch for the 0 HP Character Bug, this one addressing the case where a character succumbs to Condemned status while Jumping, but the resulting Wound status is replaced with Air Anchor status. This leads to that character potentially still being alive at the end of the battle, but they will still have 0 HP. This fixes the problem by delaying Doom until the character has landed. There are also some patches included to allow this fix to mingle with Novalia Spirit's "Petrified Rebel" fix.

I chose this solution under the principle that a character in mid-Jump is, for all intents and purposes, untouchable. Thus, it seemed logical to delay Doom itself, as opposed to just the Wound status, while the character is in the air. But now that I think about it, the intent may have been to have Doom work on a Jumping character, but the oversight lay in the possibility of the battle ending while the character was in midair. For this reason, perhaps it would have been preferred to modify the battle ending function to check if a character has "died" in this specific way. Either that, or somehow modify the Jump function to ignore Wound status until landing. I'll investigate this at some point, but for now, this is the fix I've settled on.

EDIT: A bug was recently reported that was traced back to this patch, whereby a character with Life 3 that is killed by a Countdown dies again after being revived. This has now been fixed, so anyone who has already downloaded this patch will have to download it again.

EDIT 2: I wasn't entirely satisfied with the previous version of the patch, which fixed the bug described by the above edit. I was a little put off by the fact that, with that version of the patch, the Countdown timer would always disappear immediately as soon as it ran out (though Doom would still be cast). I felt that this might confuse some people, so I decided to make some more changes to make sure the timer does not disappear until Doom is cast (though it does disappear immediately beforehand, which is fine by me). Re-downloading this version of the patch is optional if you downloaded the previous version, although the previous version is now unavailable.

EDIT 3: As of July 20, 2015, for each version of this patch for the US version of the ROM, the attached archives now also include a corresponding patch for the Japanese version.

EDIT 4: As of August 20, 2015, there is now a second fix available. Instead of delaying Doom, it allows Doom to be cast, but doesn't set the entity's HP to 0 until they land. I have also fixed a problem with the original fix, whereby if a Condemned entity was killed by other means, the Countdown timer would disappear while being attacked, which, depending on the attack, might give players enough time to realize that the entity was about to die and plan accordingly. This is an unintentional consequence that has now been remedied. The two fixes can be interchanged without using the reverse patch. The only gameplay-related difference I can see is that if the Condemned entity deals the final blow by landing, they'll die right before the battle ends.

EDIT 5: *sigh* Found and fixed ANOTHER problem. Fortunately, this time it was just a bad branch exclusive to Fix B that caused Zombie status to not set HP to 0.

EDIT 6: Fixed a possible logic error in Fix B. I don't know what the significance of it is, maybe nil, but it is now fixed for the sake of correctness. The game automatically clears Wound status on Zombie characters, but in Fix B the Wound check is potentially skewed for characters that actually were Wounded before being Zombified. I think there's an enemy skill called ChokeSmoke that turns Wounded characters into Zombie characters. The Wound check after the Zombie check was supposed to affect Life 3, which should have been cast by now in that situation, so I don't think it's likely to really screw up anything, unless there's a skill that Wounds and Zombifies a character at the same time...like perhaps Overcast.

EDIT 7: Fixed the "remove Control links" function in Fix B and the reverse patches. The function wasn't being reversed properly.

EDIT 8: Version 2.0 now removes both of the previous fixes and replaces them with a new fix, which reinstates Wound states in Wounded mid-air Jumpers at end of battle. It also makes a minor adjustment to the "+30% HP/MP" Esper bonuses, which add a little bit too much. The actual adjustment is 78/256, which is roughly 30.5%; this adjustment changes it to 77/256, which is roughly 30.08%.

EDIT 9: *sigh* Fixed a bad byte that causes the game to put you inside the Zone Eater Cave instead of giving you a Game Over.

EDIT 10: Fixed a bug that caused Esper Level Up bonuses on Vigor, Stamina, MagPwr and Speed to not work on certain characters.

EDIT 11: Adding yet another log entry to my most revised patch. This patch now fixes the update issue with nonstandard battle endings that allows things to happen like losing unused items.

EDIT 12: Fixed a couple of indexing bugs that affect the HP and MP Esper bonuses. This one is weird because it was correct in a previous version. I think I got a bit sloppy with optimization, not realizing that the X register was 16-bit and that the accumulator needed to be fully cleared to correctly set up the index. Anyway, now it's fixed, and I've also ported the patches to GBA!

665
Game Modification Station / Re: New patch: Zombie/Rippler Bug fix
« on: May 11, 2015, 12:58:54 PM »
The reason I worry about Near Fatal status is that, when a character is alive with 0 HP, they don't enter Near Fatal status immediately. Eventually, yes they do, but as far as I recall, not until someone else makes some other move. So, for instance, if the former Zombie is next to make a move, a Fight move, and they are no longer a Zombie but are not in Near Fatal status, it removes any chance they have of performing a DA. But I'll test to make sure.

I actually wasn't planning on Zombie/Tapir, I haven't tried fixing it in my own ROM yet. For that, I'd have to actually look into the Tapir function that gets called. For now, I want to address the bugs that I've already mentioned (this one notwithstanding), and then maybe later I'll try fixing Zombie/Tapir.

The next patch I plan to upload is Doom/Jump. And I am aware that it conflicts with Novalia Spirit's Petrified Rebel patch, which I am addressing.

666
Game Modification Station / Re: New patch: Zombie/Rippler Bug fix
« on: May 11, 2015, 11:24:29 AM »
I had thought about healing 1 HP, but I decided not to because I figured there wouldn't be enough difference between 1 HP and 0 HP other than "legality". Also, I feel like it would look a little bit unnecessary to actually show the number 1 in the healing process, so I would have actually made the algorithm increment the HP value itself by 1 instead. I actually stopped when I realized I'd have to check for Near Fatal status, which I wasn't sure I could do without breaking the game; the easiest way would be to jump to the place in code that handles it, but in my ROM that's been moved from its usual spot, so I'd have to make an extra patch for that. Although maybe it would have been sufficient to just set Near Fatal status anyway, under the assumption that the entity's max HP is at least 8.

A proportional HP transfer is also a neat idea. For that I'd have to look into how the game handles multiplication and division. It's also plausible that this algorithm would use even more free space than algorithm B, so that's also something to be wary of. The free space used by algorithm B perfectly fits a gap between Imzogelmo's "MP Digits" patch and another patch at C2/65D8.

667
Game Modification Station / Re: New patch: Zombie/Rippler Bug fix
« on: May 11, 2015, 01:01:49 AM »
Quote
that's spell data, done to fix "Rippler missed... but it worked?" , as seen in Master ZED's Glitches & Bugs guide.

Yeah, I knew it had to have something to do with Rippler. I figured it was different than the event code I was editing. I could probably have looked it up easily, but I was just too lazy. The bottom line was just, if it's required to fix what Terii Senshi fixed, I'm keeping it.

668
Game Modification Station / New patch: Zombie/Rippler Bug fix
« on: May 10, 2015, 11:02:44 PM »
Hi! So, even though I downloaded Terii Senshi's Rippler fix patch, assassin pointed out a bug concerning the Zombie status that wasn't fixed by the patch like I thought. Terii Senshi's patch prevents Rippler from exchanging statuses such as Morph and Dog Block, but I assumed it also prevented the Zombie status from being exchanged. It turns out that Zombie being exchanged is intended; the problem is that Rippler does nothing to handle the former Zombie, now alive, but still having 0 HP.

The included patches remedy this by adding a call to a new healing function that only heals an entity if the entity is either the caster or the target of Rippler AND the entity has 0 HP AND the other entity involved in Rippler does not have 0 HP. There are two different healing algorithms used, with a separate patch for each; the first algorithm transfers all HP from the former non-Zombie to the former Zombie, and the second restores 1/8 of the former Zombie's HP. The included reverse patch is applicable to either fix patch.

Personally, I'm not sure if either algorithm is the "correct" algorithm to apply for correcting the 0 HP problem in this case. On the one hand, algorithm A seems more realistic because, viewing the Zombie status as a state of "lifelessness", it makes sense that the same exchange of "lifelessness" would also exchange "life" by extension. On the other hand, algorithm B is more rational because it's the same algorithm as the Revivify item, the only other method of curing Zombie status.

Both patches also apply the same improved Rippler algorithm seen in Terii Senshi's patch (with appropriate modifications to accommodate the healing algorithm). In other words, I only recommend downloading Terii Senshi's patch if you're one of the rare few who care about Rippler mishandling Morph and Dog Block but not Zombie. All patches use free space bytes C2/65BE-C2/65CE, but patch B also uses bytes C2/65CF-C2/65D5.

UPDATE: I've now attached a third fix algorithm, which sets the former Zombie's HP to 1. It can be reversed using the same reverse patch.

UPDATE 2 (August 2, 2015): I've just found and fixed a potential logical issue with fix B, whereby if someone with the wrong number of max HP gets healed, it might possibly screw up the Rippler function. I don't know if it's really a problem, but this fixed version now ensures that it isn't. It also cuts down on the free space used.

UPDATE 3: I've now included a patch for a Japanese ROM.

UPDATE 4: Found a bug! The status exchange algorithm only worked halfway in the previous versions! This is now fixed. Also, I've done some shrinking of the B and C patches. Now in order to apply your desired fix algorithm, you'll have to apply the A patch and then the appropriate patch. Finally, added patches for GBA!

669
Game Modification Station / Patch update: Stone Zombie Bug fix
« on: May 09, 2015, 03:51:12 AM »
So, as assassin ever so helpfully pointed out, the former version of this patch conflicts with one of their own creation, so after scrutinizing the free space used by the patches that I am positive I never downloaded, I believe the new chunk of allocated free space to be unused by any other patch. It's also a bit smaller, thanks to some optimization suggestions from assassin.

For anyone who wants to upgrade, I suggest you use the reverse patch on the old version before applying this patch. Then, if you had previously used assassin's "If the Force Overrunneth" patch, reapply it.

FYI, assassin, I also fixed the non-headered version of the patch.

Free space used: C2/64CE-C2/64DE.

EDIT: Just as a precaution, if you want to apply this to a non-headered ROM, the fix patch and the reverse patch have their names swapped. Therefore, you'll need to use the "NR" patch to fix and "N" to reverse the fix, contrary to what the readme says.

EDIT 2: I've now included a patch for the Japanese version of the ROM. I've also fixed the non-headered patches for the US version.

670
Game Modification Station / Re: New patch: Stone Zombie Bug fix
« on: May 08, 2015, 01:34:26 AM »
OK, thanks for the info, I'll update this patch as soon as possible.

671
Game Modification Station / Re: New patch: Stone Zombie Bug fix
« on: May 07, 2015, 07:31:29 PM »
Quote
that said, maybe there is an advantage to explicitly checking for "Removes Zombie" in the attack stats.

and as i acknowledged in the prior message, dealing with a hypothetical case isn't exactly urgent.

Yeah, evidently you read the documentation, so you'd know that what the function does (exactly) is:
1. check if we're removing a status (obviously)
2. check if that status is Zombie (obviously)
3. check if Zombie status is there to be removed (because Revivify will still heal you otherwise)

Because this (at least at the time) was the only case I knew of where a status could be removed improperly. The only case I see where the Zombie status can be toggled is with Rippler, which I won't worry about because it's a bug anyway and there's already a patch for it.

Quote
your best bet is to download every patch, put them in the same directory as yours, and use the great Patch Conflict Finder:

I'm not entirely sure about doing that. I'm positive it will work...if I can find all the same patches that affect the free space in bank C2. I know that none of Novalia Spirit's patches are accessible anymore because his site's been archived, so if I find that any of them affect that free space, I'm sort of out of luck. The reason I chose C2/65FC specifically is because, despite that document listing 110 contiguous bytes of free space, that address in my ROM happened to be the location of a free space gap that was EXACTLY the length I needed.

672
Game Modification Station / New patch: Stone Zombie Bug fix
« on: May 06, 2015, 08:31:28 PM »
Hi again! This is the second of my recent patches, which fixes a bug that occurs when a Revivify is used in battle on a Zombified character that is also Petrified. The character in question will no longer be Zombified, but will still have 0 HP. This patch allows the character to gain HP when Zombie status is removed, even if they are still Petrified. This method was chosen because the resulting behaviour matches what would happen if the Revivify was used in these circumstances in the Main Menu.

EDIT: As of May 13, 2015, the attached archives no longer contain the actual fix patches, only the reverse patches. As the replies explain, the fix patches conflicted with Assassin's "If the Force Overrunneth" patch. An updated version of these patches has since been posted that has no reported conflicts with any other patch. Anyone who downloaded this version of the patch should download and apply the reverse patch, then apply the new version. If you had applied "If the Force Overrunneth", reapply it after reversing this patch.

673
Game Modification Station / Re: New patch: Save Point Glitch fix
« on: May 06, 2015, 03:18:29 PM »
Quote
http://www.romhacking.net/hacks/303/  OR
http://slickproductions.org/ff6patch.php?id=Fix%20-%20Anchors%20Aweigh

Lenophis is in the process of catching other non-action turns with that.

Oh, right, I think I actually did apply that patch at one point. The only one I remember that I never applied was Genjioff, which was a game-breaker. Anyway, if that's all covered, then I might as well skip posting that patch. To be honest, I haven't yet been in a position to test my fix, because I haven't acquired the Air Anchor.

Quote
I realized it would be an issue instead with Party Character 1 (second spot), or possibly Party Characters 1-3, since for Sabin there it's using an NPC of him on the map. But yeah I can't seem to trigger it, did you do any event work to your ROM by any chance? Or any patches applied maybe that edit event code around there?

I only recently started making manual mods to the event code in my game, and nothing I can remember other than the change I made to fix the problem had anything to do with that particular event. I know there are some other patches that alter event code, such as the "Shadow Leaves One-Man Party" patch, which I have applied, but again, I can't recall any that are relevant to my problem. I don't think there were any modifications to the event functions in bank C0, either, apart from some optimization-related shifting of code that I did as part of a previous failed attempt to fix the Save Point Glitch. I still have those changes, so I might try reverting them. Meanwhile, I guess I'll forgo uploading a patch for this until someone else confirms it's a real problem.

I do know that I once had a problem at the Floating Continent where my character couldn't leave the Save Point area because every time they tried, they'd just fall back in instead of walking forward. I have no idea what the cause was because all I did to fix it was just manually reapply the changes I'd made to an older version of the mega-patched ROM and somehow the problem went away. I also noticed Celes gliding on the airship instead of walking during the scene right before the Floating Continent emerged. I don't think anyone will have problems like this just by uploading any of my patches, though. I think it's just a problem with my ROM as the result of some outstanding change.

674
Game Modification Station / Re: New patch: Save Point Glitch fix
« on: May 06, 2015, 10:21:18 AM »
I was playing through the game, went to Tzen with Celes after leaving the Solitary Island, went through the collapsing house, saved the child inside, and recruited Sabin as usual. Celes was the lead character in the party the whole time. Subsequently, there were several scenes where Sabin was made visible, but his sprite moved by gliding instead of walking. This included:
- Staying at an Inn
- Greeting "Gerad" at Jidoor
- Greeting Edgar in the Figaro Castle basement

I found I was able to correct this behaviour by making Sabin the lead character. If you don't see this, if his movement seems correct to you, then it may be that somehow there is something wrong with my ROM file...I'm pretty sure his behaviour used to be correct...but all I know is that for my ROM, it wasn't. And you're right, in the event code it's supposed to set him to walk when moving, so I'm not sure why it doesn't seem to be the case for me. Needless to say, I have fixed the problem, though maybe not in the correct way.

675
Game Modification Station / New patch: Save Point Glitch fix
« on: May 05, 2015, 11:16:34 PM »
Hi! I'm new to this site, so I don't know if there's any easier way to get attention for new patches...

Anyway, ever since I first discovered that there were bugfix patches for my FF3 SNES ROM, I've been applying patch after patch to iron out as many as possible. I know darkmage has a project dedicated to it, but I don't think there's a single patch on his list I haven't applied, so I won't bother with it (sorry, darkmage). But in light of that, if he's interested in applying Imzogelmo's broken "Gogo cannot uncurse Cursed Shield" patch, I've discovered the reason it's broken: a byte at C2/5FE5 was accidentally left out. Adding that byte back in as per the included documentation will fix the patch. (Imzogelmo, I hope you see this too.)

But I digress. I added all those patches to my ROM a LONG time ago...and also made some other changes on top (mostly dialogue improvements). I won't make my super-patched ROM available to you, unfortunately, nor will I upload a patch for it, the reason being that I'd feel compelled to list all of the changes, but it's been so long that I don't remember all of them, and some of the patches are now unavailable to access, making it impossible to re-find all of the information. There are probably even some changes that people might find...questionable. But they made sense in my mind, and I'm still proud of them.

However, lately I've discovered documentation on other parts of the code, and subsequently realized that there were some other bugs that I was able to fix, but not to find a pre-existing patch for them. I think it's time to remedy that atrocity, so I've included a patch for the first of those bugs, the Save Point Glitch. This happens when you switch from a party on the Save Point to a party not on a Save Point, but still remain able to save and use Tents/Sleeping Bags. There are some people who think it's not necessarily a bug, partly because it was never fixed in any other version of the game, but I see it as one. So... if you're a purist, this patch is for you! If you'd rather not remove this unspecified, likely unintended "feature" that lets you save and heal using an item you rarely use, feel free to ignore it.


:edit:
Up until this point, the patches I've released to this forum have only been intended to be used on the US version of the ROM. However, I can now confirm that this patch is usable on the Japanese version as well.

:edit:
Minor update, slightly reduces the size of the patch. No functional changes whatsoever.

:edit:
Took me long enough...I FINALLY managed to port this patch to GBA!

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45