øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=33;area=showposts;start=165e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index5e11.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=33e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index5e11.html.zxßFh^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ z ·ÕOKtext/htmlISO-8859-1gzip0|Ö·ÕÿÿÿÿÿÿÿÿWed, 11 Mar 2020 02:19:35 GMT0ó°° ®0®P®€§²ð®ÞFh^ÿÿÿÿÿÿÿÿK&·Õ Show Posts - Jorgur

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 - Jorgur

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 »
166
Well if you want it to behave closely enough to the original in terms of 'level 5 can kill beast with lightning', then doesn't it need to -have- a minimum in the first place?
I don't understand this argument.

Or do you just want to make sure the fractional M never hits zero?
No, that's fine, but it shouldn't be possible. M starts out at least 128/128.
Attacking to/from back row: 128/4 = 32
Defending: 32/2 = 16
Armor status: 16/2 = 8
Using X-Fight: 8 / 2 = 4
Fractional M will normally never go any lower than 4/128.

I don't see why it should be floored at 16, it may as well go all the way down to 0.

i'm leaning towards favoring Jorgur's approach, now that i better understand his reasoning, and Square's likely motivation in "why the original minimum M value was there in the first place".

the most direct way is to change the two Minimum M checks and floors into NOPs (and the new mini-function would no longer be needed).

simply leaving the original code unaltered would have a similar effect, because M=1 with the Fractional M patch applied would be equivalent to old M=1/128.  that'd behave like M=0 in most circumstances, aside from something where M was quite low and Attack was quite high.  as rare as that is, i'm a bit of a purist, and prefer the NOP way.
I agree with this. M=1/128 and M=0/128 is essentially the same, and the unused space might come in handy.

doing away with Minimum M does raise the question of monsters who weirdly have "ATT. MULT: 0".  there are only several, and most either have Level or Attack of 0 as well, or don't even use Fight.  so really, that leaves us with the Level 52 Imp.  its Fight and Specialty will go from doing 65 damage on a Defense-less character to 0 damage.  that's a non-trivial change on paper, although most characters won't be naked at that point.

what do we suppose Square had in mind for that Imp's damage, if anything?  i'm not suggesting we bend code to remove that one case of damage plummet, but would even something as simple as editing Imp's ATT. MULT to 1 be an admission of sorts that we don't like how our damage formula works?  i.e. a cop-out?  or do we rationalize it by saying ATT. MULT of 0 was a typo?  or do we show some principle and backbone, and let that damned dirty Imp do the zero damage?
Sounds to me like a simple typo, in which case Square would be the one to blame. I think it would be out of scope to simply fix it, but if you plan to make a readme file you could describe the problem in there and tell people how to do it themselves. I'm sure anyone who goes out of their way to install a fractional M system could be bothered to do a simple hex edit.

 :edit:
An alternative would be to make a separate "Imp fix" patch.

167
I think that works for me, if you want to set a minimum. I'm thinking 128 would be fine, as it would make it match up with the original, right?
It would, but we were just discussing why the original minimum M value was there in the first place. I am suggesting that there doesn't need to be a minimum M value in a fractional M system.

168
I think my head just exploded
:tongue:

lemme run down what i think your positions are; correct me anywhere.

1) as a supporter of the Fractional M patch, you don't favor the round-downs to M that were causing "steps" in the original game's damage ascent.
2) you're not against pathetically low M values (like a hypothetical of 0.08) possibly causing 0 damage.
3) but you don't believe that all M values from 0.01 to 0.99 should result in 0 damage.
4) nor do you favor all of them having a marginally nonzero damage value like 1, because that's nearly as bad.
5) you believe that Square established a Minimum M of 1 not because they always wanted damage to be >= (Attack - Defense), but because they were trying to perform a preemptive round-up to avoid the widespread round-downs to zero damage described in #3.
6) you believe that a patch which eliminates said round-downs is no longer in need of preemptive round-ups.  and that these round-ups were essentially the other side of the same dirty coin as the step-inducing round-downs.

1) I do not favor them, but I respect the fact that they are part of the game. Because of this, I classify the Fractional M system as a game modification, not a bug fix.
2) True (but this will mainly happen in cases where defense is almost high enough to nullify damage anyway)
3) True
4) True
5) True
6) True


169
I am essentially suggesting that you make the fractional M patch without a minimum M value (you currently use 128 - see link).

http://slickproductions.org/forum/index.php?topic=1975.msg21849#msg21849

170
Are you saying the absolute minimum M must be is 1, or are you arguing a preference that it be more than 0? Because I'm unclear from what you're writing.
In what context? If there is something I wrote that seems unclear, can you quote it?

171
Quote
A patch which is willing to let new M be under 128 (or in original M terms, a fraction under 1) shouldn't rule out letting M get down to 0.
It looks like we might have a misunderstanding here.

I believe:
- In vanilla FF5, M must never be rounded down to 0 (which mean M >= 1 is the only option)
- In fractional M FF5, M can be 0 (but this will never happen)


Clarification - the following text was written with vanillla FF5 in mind:
Quote from: Me
You believe that:
1. There is a reason why the developers set the lower limit for M to be 1 when it could have been 0.
Thus implying:
2. Allowing M to be 0 is an idea at least worth considering

If "2" is false then "1" is also false. If M >= 0 is not an option, M >= 1 is the only logical choice. In this event it is safe to assume that they set the floor for M to 1 for mere technical reasons.

When I say "vanilla" FF5, I mean FF5 without any patches.

172
I feel the need to clean up the discussion a little. I fear there might have been some misunderstandings along the way.

Let me first describe the issue to everyone.
Quote from: Me
Nut Eater
Attack 5
Multiplier 2

A Nut Eater attacks a character with defense 0. Regular attacks do 10 damage. While using defend it's 5 damage. While using defend in the back row it's still 5 damage.
In my opinion, it should be 2 damage in the last case.

This is what happens (in vanilla FF5):
Code: [Select]
Attack = 5
M = 2

Defend modifier: M / 2 = 2 / 2 = 1

Back row modifier: M / 2 = 1 / 2 = 0.5
0.5 rounds down to 0

If M = 0, M is set to 1

5 * 1 = 5

The damage ends up at 5 because M cannot be lower than 1.

The player is not rewarded for using multiple defenses (Defend, Armor, back row). It becomes meaningless to use Defend or Armor buff in the back row while fighting certain monsters (especially early in the game). I believe this is a problem caused by a simple engine limitation: M can never be lower than 1.

I propose that, in your fractional M patch, you change the code so that M can be a fraction between 0 and 1, but never 0.



Now, let's see if I have understood assassin's arguments correctly. Please forgive me for any misunderstandings.


You believe that:
1. There is a reason why the developers set the lower limit for M to be 1 when it could have been 0.
Thus implying:
2. Allowing M to be 0 is an idea at least worth considering

If "2" is false then "1" is also false. If M >= 0 is not an option, M >= 1 is the only logical choice. In this event it is safe to assume that they set the floor for M to 1 for mere technical reasons.

Am I right so far?


I believe the developers set minimum M to be 1 rather than 0 to ensure that every attack does at least a little bit of significant damage (which in vanilla FF5 ends up being Attack - Defense). Attacking from back row to back row (with a decent sword) and doing 0 damage would be incredibly frustrating. Let's assume that M can be 0. You are fighting Magisa and Forza, and you use physical attacks against Magisa while she is in the back row with the Armor buff.

All your attacks would do 0 damage!

This is what I mean by "silly". Doing 4 damage, or 12 damage, or 15 damage is fine, but doing absolutely no damage would cause confusion and frustration.



I hope I'm not coming off as being offensive. My intention is to increase the quality of our hacks in any way I can. In fact, I welcome constructive criticism and counter-arguments.

Now, it is time for bed.  :sleep:

173
this goes to the heart of *why* Square had Minimum M in the first place.  it's fairly obvious they were trying to avoid low M causing 0 damage.  instead, there is a floor that's usually well above that (depending on Attack and Defense values).  the question is: how averse would Square have been to values that aren't zero, but are ridiculously close to it?  if having nonzero damage were their only goal, they could simply have given the damage value itself a floor of 1 -- but they chose to modify M instead.
Some games use 1 as a damage floor (SD3, AoE2), but FF5 uses 0. If FF5 used 1, it would not be possible to nullify damage by having high defense (Bone Mail, Cursed Ring, etc.). I don't think giving the final damage a floor of 1 was ever a possibility.

(Vanilla FF5)
As for why the minimum M value is 1, is it not simply because 1 is the lowest number an integer can be? Giving it a floor of 0 would be silly; you would be able to nullify damage (high atk, low M) by simply using Defend or being in the back row.

saying an instance of Nut Eater damage "should be" lower is subjective, at the least.
It seems logical to me that both back row and Defend modifiers should come into effect when facing Goblins and Nut Eaters just like with high level monsters. When you are defending in the back row you should expect that the regular 10 damage will be reduced to 10/2/2=2. This is not possible when M is an integer, but with the fractional M system I see no reason why this shouldn't be made possible (correct me if I am wrong).

174
how would they know what level the caster of Bolt was going to be?
Simple. If you play standard FF5 without grinding or running you will hit level 5 right around the time you meet Carcursers. Once you hit level 5 you can start killing Skeletons and Carcursers in one Fire or Bolt spell. Game designers do this all the time; they have to pay attention to small details like this.

175
It seems so, but I am not sure if that is going to have a high impact on damage.
Well, Carcursers have 75 HP. If you use a Bolt spell it will do 70 damage instead of 75 because of Atk/2*2. If it did 75 damage it would always kill the Carcursers in one hit (which I think might have been the developers' intention).

I probably don't understand this as well as I should, but couldn't the fractional M system be redesigned to fix this somehow? Perhaps multiply Attack and M before applying Attack/2 modifiers?

One thing I noticed just now is that fractional M doesn't seem to apply to monsters' Fight command.
The addresses C2/8246 and C2/825A are edited by the Fractional M patch. What is the issue there?
Nut Eater
Attack 5
Multiplier 2

A Nut Eater attacks a character with defense 0. Regular attacks do 10 damage. While using defend it's 5 damage. While using defend in the back row it's still 5 damage (it should be 2).

So yeah, minimum M still seems to be 1. It would be really nifty if it could go lower, like 0.125 (1/8) in the more extreme cases (armor buff, defend, back row).

176
Ah, I see. I guess it is not a bug.

Would it be possible to use M/2 instead of Atk/2 (multitargeting/element half) if element weakness applies?

 :edit:
One thing I noticed just now is that fractional M doesn't seem to apply to monsters' Fight command. This means that if you are using Defend/back row and the monster's M is 1, you will still take full damage.

177
No, I never get 76, only 70 and 81.
Quote
******************************
6.4.1) MAGIC DAMAGE PARAMETERS
******************************

Attack = Spell Attack + (0..(Spell Attack/8))
M = (Level*Magic Power)/256 + 4
Defense = Magic Defense
With a weak spell like Fire, there should be only 2 possibilities, Attack = 15 and Attack = 16. This remains true even with fractional M. It should never be 14.

 :edit:
It turns out this also happens in vanilla FF5. It seems to be a bug in FF5 rather than in the fractional M patch.

178
Final Fantasy V Research & Development / Re: FF5 Bugs & Glitches
« on: December 26, 2014, 02:04:24 PM »
I thought the wiki would be the perfect place for this project so I created a page for it.
http://slickproductions.org/slickwiki/index.php/FF5_Bugs_and_Glitches

179
I ran into a possible bug while testing.

Galuf Black Mage
Level 5
Atk 15
Magic 55

5*55=275
275/256~=1,074
M = 5,074

15*5,074=76,11
16*5,074=81,184

Galuf attacks three Skeletons with Fire. He is expected to do 76 or 81 damage on each Skeleton. Instead I get this:

180
I did a quick test earlier today. It seems to work fine; damage steadily increases with level ups.

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 »