øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=345e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index0bd6-2.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index0bd6-2.html.zxH›h^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ ,/ùüOKtext/htmlISO-8859-1gzip@øÕùüÿÿÿÿÿÿÿÿWed, 11 Mar 2020 08:19:44 GMT0ó°° ®0®P®€§²ð®G›h^ÿÿÿÿÿÿÿÿ)+ùü Show Posts - assassin

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

346
General Discussion / Re: NFL season 2014-2015 week 18 (playoffs?!)
« on: January 10, 2015, 03:27:49 PM »
RIP Stuart Scott.  he was talented, and brought life into sports recaps.

for today:

Patriots
Seahawks

tomorrow's picks will wait.

347
General Discussion / Re: NFL season 2014-2015 week 18 (playoffs?!)
« on: January 08, 2015, 06:40:51 PM »
Wild Card round results:

Lenophis = 1-3
Deathlike2 = 2-2
assassin = 3-1
JCE3000GT = 3-1

348
General Discussion / Re: NFL season 2014-2015 week 17 (playoffs?!)
« on: January 03, 2015, 11:18:37 AM »
I know I'm 17 weeks or do too late but is like to chime in.  :)

hey, that's been my style for years now.  hopefully, you stick around for the entire playoffs.

i'm echoing your picks:

Panthers
Steelers
Colts
Cowboys

as usual, those are subject to change pre-game, particularly if personnel does.

349
no, we're arguing over who Britain's best all-time Prime Ministers were.

350
Final Fantasy V Research & Development / Re: FF5 Bugs & Glitches
« on: December 31, 2014, 01:58:20 PM »
damage types that call C2/8811 to finalize damage will multiply M by 2 if "Target Can't Evade vs. Attack type".  then if the attack is found to be "Magic Sword Drain", or if "Healing?" (elemental absorb, it seems) alongside a nonzero Variable $63, this higher M is used to recalculate damage or healing.

damage types that call C2/8A05 to finalize damage do something similar.  M _can_ be multiplied by 2 if "Target Can't Evade vs. Attack type".  then if the attack is found to be "Healing?" (elemental absorb, it seems) alongside a nonzero Variable $63, this higher M is used to recalculate damage or healing.  the difference here is that M is only doubled IF it was found to be 0 and floored at 1.  so the "Target Can't Evade vs. Attack type" bonus is being applied VERY narrowly.  this makes me wonder whether the "BNE $8A26" at C2/8A0F shouldn't have been "BNE $8A13" instead.  if it's intentional, that raises the question why "REP #$20 / ASL $52 / SEP #$20" at C2/8A20 even needs the REP and SEP, if they know 16-bit $52 has to hold 0001h there.

i don't expect the answer as to whether there's a bug to come quickly, as this M bonus doesn't seem well-known to begin with (i can't find it in the Algorithms/Stats FAQ).  if we determine exactly which C2/8811-using attacks it influences and how, maybe we'll be in a better position to judge what's going on in C2/8A05.

351
- yes
- because with the Fractional M patch in place, that M = 1 is equivalent to M = 1/128.  that's why we were raising it to 128 in the Delta patch -- to maintain original functionality.
- not many come to mind, aside from that Level 52 Imp example.  however, flooring M at 1 would have pretty much the same result for it.

i had once considered attacks losing the (Attack - Defense) lower damage bound to be an issue, as a "reinterpretation" perhaps meant for an optional second patch.  however, Jorgur has largely talked me out of the concern.  see my December 28, 2014, 02:30:24 PM post and his response for a rundown of his/our/my thinking on the matter.

under the system envisioned, NOPing the "if M = 0 then M = 1" checks is more technically correct than keeping them (albeit the same result in most cases), and it'll also free up 2 bytes at C2/8A11 and 3 bytes at C2/940E.

(for the former, i was gonna say 6 bytes at C2/8A0D, but Square apparently has "Check Target Can't Evade vs. Attack" contingent upon M having been 0 ==> 1.  that raises the question why "REP #$20 / ASL $52 / SEP #$20" even needs the REP and SEP, if they know 16-bit $52 has to hold 1.  i'm leery of this stretch of code's narrow usage, and how it differs from that at C2/881D.  the branch at C2/8A0F spanning so far seems odd in particular.  but i'm willing to respect it for time being, which is why i said only NOP 2 bytes at C2/8A11.)

352
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.

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?

353
General Discussion / Re: NFL season 2014-2015 week 15
« on: December 29, 2014, 08:07:14 AM »
Cardinals at Panthers is only available on cable/satellite unless you live in one of those teams' markets?!  fuck that.  the NFL isn't the NHL, NBA, or MLB, where there's 5+ games per playoff round; it's just the 1.  nor does this sport have the niche interest of hockey, or slowly falling interest of baseball.  i hope the ratings are horrible by broadcast network standards (they might've been anyways, given the teams playing: the tallest sad midget against a determined, cactus-eating, survivalist cripple), and that this experiment blows up in the NFL's face.

354
General Discussion / Re: NFL season 2014-2015 week 15
« on: December 29, 2014, 04:52:37 AM »
^ the fans are gonna be hard to distinguish if i watch this on an SD set; same color schemes and all. :)  anyway, congrats to the Cowboys.  a very formidable team.

my message to each team's defensive coordinator would be: doubleteam Calvin Johnson.  doubleteam Dez Bryant.  Stafford and Romo are talented quarterbacks, and they don't mindlessly lock in to a certain receiver, but they do have their favorites, who score a disproportionate share of the teams' receiving touchdowns.  make the QBs go out of their comfort zones and have to beat you with other weapons.  maybe a drive or two will end early in a punt, or maybe they'll have to settle for a field goal or two inside the red zone.

-----------------------

Week 17 totals:

Deathlike2 = 11-5
assassin = 13-3

355
Quote
It looks like we might have a misunderstanding here.

yes, there was some.  i thought you were fixated on avoiding 0 damage, but fine with everything else down to that, and that you considered Square to have the same motives.

your 09:38:34 AM post clears things up a bit.

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.

356
General Discussion / Re: NFL season 2014-2015 week 15
« on: December 28, 2014, 12:17:42 PM »
after several minutes of careful consideration, i am parroting Steelers over Bengals .

357
General Discussion / Re: NFL season 2014-2015 week 15
« on: December 28, 2014, 12:05:39 PM »
keep in mind the clock on this server is 2+ minutes fast, not that anybody was moving to disqualify my picks anyway.

358
General Discussion / Re: NFL season 2014-2015 week 15
« on: December 28, 2014, 12:03:06 PM »
mostly same, except i'll say:

Eagles over Giants
Bills over Pats

to mix things up.  i'll post my pick for Bengals/Steelers later.

359
Quote
Am I right so far?

not really. :P 


I 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.  Namely, it's very likely that they wanted to make a lower damage limit of (Attack - Defense).  If their only goal was to avoid 0 damage, they could simply have floored the damage value at 1 whenever Attack exceeds Defense.

Thus implying:

2. A patch that puts off the divide by 128 should set the lower limit for M to be 128, to behave equivalently to the original game.  If someone wants to expand the patch to not just change the smoothness of damage _progression_ but also to move the lower damage bound, they should realize the patch has taken on a second purpose, and label it accordingly.  (But only after some soul searching over how they're desecrating the original designers' balance. :P)

And that:

3. 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.  Why should somebody who's stripped off most of their clothes suddenly become self-conscious about removing their socks?

--------

Quote
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.

whoa, i don't agree with any of this series of deductions.  for one, "mere technical reasons" may well be balance reasons.  secondly, proving that M can't be > 0 and < 1 in the original game does *not* prove that Square was forced into damage being at least (Attack - Defense).  i've already spelled out a simple alternative that they could have used, yet didn't.

to be sure, i understand your point that Square couldn't readily divide M any further, short of making their own Fractional M patch.  i just disagree with the various things you're extrapolating from that.

anyhow, ditto on the  :sleep:  why do i feel like my eyes are trying to pull my screen towards me?

360
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.

good points.. but they don't change the fact that in cases where Attack is notably above Defense, Minimum M serves to elevate damage well above 1.  (e.g. 30 Attack - 0 Defense gets a damage of at least 30.)  and the patch changes you propose would eliminate much of that elevation.

let me amend my statement from the last post (italics for added part):

Quote from: assassin
If having nonzero damage were their only goal, they could simply have given the damage value itself a floor of 1 whenever Attack exceeds Defense -- but they chose to modify M instead.

Quote from: Jorgur
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.

if the math causes the damage in these cases to round down to zero, what's so silly about it being kept as zero?  you seem to be arguing that it's not silly to bring Minimum M down from 1 to 1/8, but suddenly it's an issue when it goes from 1/8 to 0?  why?!  arithmetically, 1/8 is closer to 0 than it is to 1.

and that was the main point of my last post: if Square's Minimum M established a damage floor well above zero (for cases of reduced M, not the high Defense >= Attack example), how sane is it to assume that throwing out a majority of this floor is in keeping with Square's intentions?


Quote
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.

but it didn't necessarily seem logical to Square.  which is why they do the following:

1) M = some term (e.g. (Level * Strength)/128) + constant.  That last term is evidence that they wanted nonzero M, even for wimpy attackers.
2) Various M or Attack modifiers, including division of M by 2.
3) If M is 0, set it to 1.  Evidence that they were serious about that nonzero M.
4) Damage = (Attack - Defense) * M

Quote
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).

it's possible, but like i said in the last message, it's a bit of a reinterpretation.

what you haven't really answered from my last post is: Do you think Square set Minimum M to 1 because they wanted to ensure damage of at least (Attack - Defense), or do you think they did it because they wanted to ensure Damage was merely >= 1?  if your answer is the latter, then tell me:

1) what's so significant about the change from 0 to 1 that it's worth the effort?
2) why M was used to try and achieve the goal.  Square could have floored the damage value at 1 whenever Attack exceeds Defense, but instead opted to put a lower bound on M instead, knowing that would result in considerably higher damage.

as your position stands now, you're asserting that most of Square's Minimum M is expendable, yet expending all of it is "silly".  what makes you so confident in both stances?

my position is that a plummet from 1 to 1/8 is at least as silly as that from 1/8 to 0.