øA slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=195 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexf46c-2.html slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexf46c-2.html.z x D›h^ ÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ 0Pd { OK text/html ISO-8859-1 gzip 0|Ö { ÿÿÿÿÿÿÿÿ Wed, 11 Mar 2020 08:19:40 GMT 0ó° °® 0® P® €§² ð® C›h^ ÿÿÿÿÿÿÿÿý1 {
We have EVEN MORE themes now, but some old ones are gone...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.
Sorry magitek, I hit modify instead of reply and totally botched your triple post. Feel free to modify it further and slap me with a wet trout.
)
)I was just going to say that you could always do a fix A/fix B solution if there are caveats or multiple interpretations to how it could reasonably be fixed.
I lean towards thinking it makes more sense to pause periodical damage during Freeze, too. But I'm aware that it is a contested topic and as such, strays from pure bugfix territory and will not be including that change in the patch (maybe in the .asm as an optional addon).
Quotecorrect me if i'm wrong.. this risk presents once you do the following:
1) stop clearing $3EE2
2) Function C2/0B01 handling Haste/Slow toggling
3) dropping the 2048 decrementor cap
If I understand the way you described it correctly, zeroing the low byte of$3EE2($3F30, as you posted previously) should eliminate this risk? Meanwhile, waiting to zero the supply until we stopped calling C2/0B01 should, uh, eliminate it again (or more).
Quote from: assassinbut a devil's advocate argument to fuck with myself:
if the Morph timer counts down from 65535 to 500, we don't update the Morph supply. yet when it goes from 500 to 0, updating Morph supply is now vital? while 0 is indeed a special case, is it special enough to say that a change of 500 outweighs a change of 65035?
Not trying to sound facetious, but that kind of sounds more like a devil's strawman. :P
Can you think of anything concretely screwy that can happen from not zeroing the supply right away, considering Revert will force it's way into the next available action slot? Maybe if autocast got in the way of Revert (Condemned), since those have priority? But, Terra dying doesn't thwart the supply being updated normally, does it?
I kind of agree it would make more sense to decrement the supply at the same time as decrementing the timer, kind of. But luckily, the supply stays intact for me to use as a base for the decrementor in this patch.
That sounds like a good idea, you should add that to the wiki. I noticed some descriptions where your comments add to the understanding of the bit (you have "flag target's ATB gauge to be reset?" and the RAM map has "psyche was just cleared", for example).
Quote[re CPX $3EE2 in C2/0B01:] looks like you talked yourself out of it.. but to chime in, i don't favor sacrificing capability just to save a few bytes.
More like I talked myself into it, except I still can't find a way to shrink C2/09D2 enough to fit a jump to C2/0B01.
1. There's that TYA.
2. I don't think the CLC is needed either (assuming the ATB multipliers are all even).
3. ???
I think my proposal is fairly strictly limited to the few functions already modified to create the functionality of the patch, so it creates no unexpected incompatibility. Neither should it produce any unexpected issues for users who only care about vanilla functionality. Gutting unused parts the code does make it hypothetically less robust, but not to the point of collapse under the constraints of normal gameplay.
With that being said, this is a valid point, especially in a world where it's so easy to mod the game. This is why I'm a bit gung-ho about this as long as I don't break vanilla. My idea was to provide a .ips patch that works fine within the constraints of vanilla, for people who just want to patch and play, and supplement it with an easily modifiable source file (and ample documentation) for people who want to make mods.
;(Removed code, for reference. Removes 11 bytes)
;LSR
;LSR
;CMP #$0800
[...]Quotewhen did free space become THAT scarce?If not sometime in the past ten years of bug fixes, presumably sometime not too far in the future. There are many bugs left and thrift is a virtue. :P
I apologize in advance for the short novella I'm about to produce, but I have given this topic quite some thought and I feel ready share my conclusions. You may have provoked this, Assassin, but it's not directed specifically at you, although I am grateful that your rhetorical aside gave me pause to think about this.
[snip]
Free space requirements make it more difficult to maintain patch compatibility. If something can possibly fit inline, it's pretty important to make it do so, in my opinion, especially for .ips users who can't change where extra code goes. However, the more important consideration for compatibility is avoiding reaching out of scope or modifying unrelated functions, in order to avoid potential (and unexpected) code conflicts. This requirement of modular code naturally trumps free space thrift, but if it can be fulfilled, then the next order is to make the patch fit inline if possible.
With all these considerations in mind, I believe that, for now, my list of priorities looks something like this:
1) Achieving the objective of the patch
2) Patch compatibility (modular code, free space thrift, expected behaviour etc.)
3) Ease of use for end-users (patch and go)
4) Being thrifty with free space for future patches
5) Ease of use for hackers/patch authors
6) Elegance and simplicity (for personal satisfaction and bragging rights)
That last one IS a point of pride for me but it must unfortunately fall below all the others if there is a conflict. Luckily, it more often goes hand in hand with most of the other requirements.
Finally, and most importantly, I still consider myself if not a novice, at least fresh off the boat to the world of assembly coding and patch making. Every project is a huge learning experience and so I try to push hard to work within the constraints of fulfilling all the requirements I set up for myself, or at least finding the best compromise. In most cases it would be fine to relax a little bit, if you already know what you're doing, but I'm still learning and would prefer not to afford myself the allowances that come as reward for experience just yet.
I'm sorry, what does any of this have to do with rods and spells?
I would hope any potential hack authors interested in allowing multiple Morphers and using this patch would read the documentation I intend to write (where this caveat would naturally feature) and find out how to remedy the problem (commenting/uncommenting some lines in the included .asm file).