Upcoming Events

Collapse

There are no results that meet this criteria.

Announcement

Collapse
No announcement yet.

EffectDamageIncrease problem with 1.13

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • EffectDamageIncrease problem with 1.13

    It looks like 1.13 has a little problem of having introduced a new parameter to EffectDamageIncrease which causes any spells or abilities which boost damage to only apply the damage on a critical hit (if/when it is applied at all).

    According to this post (http://nwn2forums.bioware.com/forums...forum=109&sp=0) in the main forums, there is a workaround of changing the new parameter to 0, which then applies the damage without the 'burst' critical problem. This workaround does break damage vs. race, apparently, but fixes the damage boost problem.

    Obsidian will be releasing an override quick fix (no proper hotfix, unfortunately) in a few weeks.

    I was wondering: is possible to apply this workaround directly in a server update rather than waiting for the Obsidian override?

  • #2
    Is it possible? Yes.
    I think I can speak for everyone here, when I say this isn't going to happen.
    There's more to this story then your report is showing.


    1.) The so called workaround involves manually altering every single script that has anything to do with DamageIncreases. Its not 20 scripts as Kaedrin says, were talking near a hundred.

    2.) As you said, it will break vs races. It's not sound planning to break something to fix something else.

    3.) It will take someone hours of work to fix this. Obsidian will have it fixed in 2 weeks.
    It's a global change so all languages must be re-built. Unfortunately, it takes that long to build the full patch package and test
    Kinda seems like a waste of hours of work by someone on Sundren, that could be spent more productively.

    4.) If somone does go and modify everyone of those scripts, when the HOTFIX comes out (again in less then 2 weeks) every single one of those scripts will then be broken and someone will have to go back and FIX those scripts again. Hours MORE work.

    5.) This will not fix eveything either. This only will temporarily fix those 'soft-coded' effects. Smites will still be broken, some of the bard songs will still be broken, more stuff I'm not even thinking of I'm sure.

    6.) The 'override quick fix' idea was discarded.
    http://nwn2forums.bioware.com/forums...forum=109&sp=0 (bottom of the page)


    Taking all this into account, you come to see what a mammoth waste of time this workaround would be for any persistent world, released module, or single player campaign to adopt.

    Comment


    • #3
      Yikes!
      Thanks for your comprehensive breakdown, sharrington.
      Yeah; not worth the time at all.

      Now it makes better sense why it will take 2 weeks for Obsidian to get a fix and test it. Fair enough.

      Comment


      • #4
        Sheesh, I find it amazing how much the Obsidian guys put up with on those boards. I'd ban the lot of them. Constructive feedback should not be veiled insults.
        Lorlen Locke: "Amazing how the righteous commit acts of tyranny and terror almost as beautiful as our own under their banner of "good". We merely call a spade a spade."

        "If you can't learn to do something well, learn to enjoy doing it poorly."

        Comment

        Working...
        X