øA slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=printpage;topic=2205.0 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index1a47.html slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&topic=2205.0 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index1a47.html.z x
1h^ ÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ €°Y Â/ OK text/html ISO-8859-1 gzip @øÕ Â/ ÿÿÿÿÿÿÿÿ Wed, 11 Mar 2020 00:46:27 GMT 0ó° ° ® 0® P® €§² ð®
1h^ ¼ Â/
Print Page - New patch: Imp's Rage Bug fix
Board of Slick
Banon's Donkey Farm => Game Modification Station => Topic started by: 13375K31C43R on April 20, 2016, 01:12:07 AM
Title: New patch: Imp's Rage Bug fix
Post by: 13375K31C43R on April 20, 2016, 01:12:07 AM
Hi everyone! Here's another patch for a bug I tried to fix a while back, and it actually ended up causing even more problems...turns out the fix I needed was even simpler than I thought, and I even managed to fix it without using any free space! So, the bug in question is with the Rage and Dance commands and the Imp status. Those two commands make the user act autonomously, repeatedly choosing moves from the selected Rage or Dance. However, neither one can be used if the party member is an Imp, so they will fight instead, but they will still be autonomous. Worse, a Rager will not receive the statuses or immunities associated with the Rage. This patch fixes all those problems.
:edit: January 29, 2018 GBA port added!
Title: Re: New patch: Imp's Rage Bug fix
Post by: C. V. Reynolds on April 21, 2016, 03:53:15 AM
Hoi. :3
Sorry for this late check. Better late than never, I guess.
Compatibility issue with this patch. As per mblock129's patch conflict program:
Patches: Auto-expiring statuses don't reset their timers with manual removal.ips Imp's Rage.ips Address: 0x24720 - 0x24720
EDIT: Confirmed. Assuming no header: HEX 24720, DEC 149280. Applying Imp's Rage first makes this byte read E5. Applying that Auto-expiring thing first makes the byte read E0. Strangely, it seems E5 is the unaltered byte for that spot. Maybe there's something wrong with the Auto-expiring statuses patch? Does it need to write to that spot? Attempts to recreate the patch are yielding no different result. Hm.
EDIT EDIT: It seems something may be wrong with Assassin's patch, but I'm unsure what. Headerizer can't process it. Still doesn't explain why attempts to remake the patch yield no different result, though.
Title: Re: New patch: Imp's Rage Bug fix
Post by: 13375K31C43R on April 21, 2016, 07:25:52 AM
Interesting. I'm busy this morning, but I'll look into this when I have the chance. You say it's the non-headered versions of both patches that are conflicting with each other (and thus the headered versions should as well)?
Title: Re: New patch: Imp's Rage Bug fix
Post by: C. V. Reynolds on April 21, 2016, 07:38:46 AM
I solved the problem of why Assassin's patch wasn't working in Headerizer. It probably should be considered a bug in Headerizer. It can't stand it if the extension is in CAPS.
As for the other issue, I've begun to think it is NOT an issue if my theory is right. I've started to believe that I've been bizarrely using the wrong patch for years. It's actually an anti-patch. Yes, that's embarrassing. Just need to confirm it now. One moment.
EDIT: Nope. That wasn't it. It's still a problem, I guess.
Kaettekita edit: WAIT. I might have it now. I don't know why it would happen, but my patcher (which I've had trouble with before) could be making a patch that writes to that byte. I know that doesn't seem to make any sense, but none of this does. I'll test that.
Final Cutter edit: Amazingly and against sense, that WORKED.
It wasn't really my patching program, per se. It patched exactly as it was supposed to. The problem was: My patch was written by Lunar IPS (because I was making a non-header version) years ago. My current patching program (flips) makes the exact same error Lunar IPS did years ago. Maybe it goes to show how insecure IPS patches can be. :bah: It would sound like a clear case for switching to BPS if that format was friendly to patch stacking... Anyway, Headerizer has solved the problem. Now I worry about other patches I have, though. How many were thrown off by whatever strange algorithm these IPS makers do?
Title: Re: New patch: Imp's Rage Bug fix
Post by: C. V. Reynolds on April 21, 2016, 08:07:11 AM
I'll attach the IPS files for study and comparison here. I don't how what good it'll do, but... who knows?
Don't use the one marked "bad" unless you're studying. It probably won't make anything explode, but whatever.
EDIT: Okay, they're up. One had its header removed through Headerizer. That's the one that works right. The other one was created by Lunar IPS back in 2009. flips does the exact same thing now. They both produce the strange conflicting patch.
EDIT 2: Removing the patches. There's no need to keep them up now.
Title: Re: New patch: Imp's Rage Bug fix
Post by: assassin on April 21, 2016, 10:42:45 AM
this patch's Readme explains why i used a specific patcher to make it. best follow suit.
Title: Re: New patch: Imp's Rage Bug fix
Post by: 13375K31C43R on April 21, 2016, 11:17:15 AM
You also use SamIPS2, huh? Yeah, it's my favourite.
So to summarize, there's no actual conflict, but Headerizer apparently has a problem with all-caps extensions?
Title: Re: New patch: Imp's Rage Bug fix
Post by: 13375K31C43R on April 21, 2016, 11:37:47 AM
OK, I found the problem. It was merely an oversight on my part. It's been fixed now.
Title: Re: New patch: Imp's Rage Bug fix
Post by: Xenovant on April 25, 2016, 07:46:26 PM
Is this really a bug? I mean, the Imp status is basically a "f*ck you" status (unless you are wearing the imp equipment). This is more of the same: "So you chose to use a rage or a dance... here I am: no benefits from now on" xD
If you can cancel a rage or a dance casting Imp, the status is something good for you, you can use it deliberately if you aren't happy with the rage/dance.
Title: Re: New patch: Imp's Rage Bug fix
Post by: 13375K31C43R on April 25, 2016, 08:10:09 PM
That's not really the point. The point is, Rage and Dance are not supposed to be applicable AT ALL when in Imp status. The autonomy is part of those commands, so it shouldn't be applicable either.
Assassin and I have already discussed this to some level, which you can read on here (http://slickproductions.org/forum/index.php?topic=2165.0). There are also some links to other hackers' discussions on it.
Title: Re: New patch: Imp's Rage Bug fix
Post by: Xenovant on April 25, 2016, 08:19:00 PM
I guess it's just my point of view. I like how Imp trolls you when you are using a rage/dance :laugh:
Title: Re: New patch: Imp's Rage Bug fix
Post by: assassin on April 25, 2016, 09:11:10 PM
or put more broadly: it's total nonsense to be part in Rage, part out. if you keep the automatic acting, you should keep the other properties.
that's just the reverse way of looking at the same contradiction. it would be put into practice in a patch where one interprets Imp status as not having the "power" to reverse a complex command that's already underway, but being able to swap out the next _action_ for Battle.
(this isn't meant to rehash the prior thread's debate, rather to concur with OP that vanilla behaves bogusly from multiple perspectives.)
Title: Re: New patch: Imp's Rage Bug fix
Post by: Xenovant on April 25, 2016, 09:38:21 PM
Don't get me wrong, from a logical thinking, I understand that, and I completely agree: all in or all out. It's just I think it's better the way it is, a trolling status trolling you. If you fix it, there are even benefits, as I said, it's way for you of cancelling a rage/dance.
Title: Re: New patch: Imp's Rage Bug fix
Post by: 13375K31C43R on February 20, 2018, 11:12:26 PM