Save Para?
Save Para?
Can somebody look into how sv_para interacts with things like para ray from pris? I've heard a lot of people say that its 'broken' because they don't notice a differance in resisting pris para even with -15par. This is particularly noteworthy when it comes to shaman, as they are always getting parad when pris para ray fires. Brought this up because I saw people getting paras left and right last night in seelie, regardless of their sv_par stat.
Maybe pris is busted and ignores save modifiers?
Maybe pris is busted and ignores save modifiers?
OK. I bit, and spent about 30 minutes studying and testing the code. As far as I can tell (and I used debug lines to test the values) there's nothing broken with the para either for major paralysis or prism.
Shamans do have a worse save than some other classes on that particular save, but that's not a bug, it's a um... well, you get it. :)
Actually, I'm gonna try one more thing. Will have to get back to you on this. Tracking down something that may be causing it.
Shamans do have a worse save than some other classes on that particular save, but that's not a bug, it's a um... well, you get it. :)
Actually, I'm gonna try one more thing. Will have to get back to you on this. Tracking down something that may be causing it.
OK, here's the situation:
Deep in the bowels of the code, there's a check that pulls what the save value for the different classes and races should be. In that check, someone put in a few nice little tweaks for classes and races at the end that subtracted (think of it as wearing more - sv_whatever) from the value that was being returned. These were intended to be a boon. One of those situations was barbarians and para. They were SUPPOSED to be better at sv_para.
However, if you set the numbers up JUST right... it created a situation that mimicked what happens if it couldn't find the numbers. The value returned was identical.
The most glaring, obvious example of this was Barbarian Shamans that are 50th level. They get EXACTLY that value returned which says 'I couldn't get save info, so they fail.'
Anyway, found, squished, hopefully will be moved in soon. Thank you, please drive through, and oh, by the way...
We DO read the BBS, if that was ever a question. :roll:
Deep in the bowels of the code, there's a check that pulls what the save value for the different classes and races should be. In that check, someone put in a few nice little tweaks for classes and races at the end that subtracted (think of it as wearing more - sv_whatever) from the value that was being returned. These were intended to be a boon. One of those situations was barbarians and para. They were SUPPOSED to be better at sv_para.
However, if you set the numbers up JUST right... it created a situation that mimicked what happens if it couldn't find the numbers. The value returned was identical.
The most glaring, obvious example of this was Barbarian Shamans that are 50th level. They get EXACTLY that value returned which says 'I couldn't get save info, so they fail.'
Anyway, found, squished, hopefully will be moved in soon. Thank you, please drive through, and oh, by the way...
We DO read the BBS, if that was ever a question. :roll:
Wow... a bug report, an explanation, and a bug fix all in the same calendar year?
Are you sure the Toril gods came from Sojourn?
Are you sure the Toril gods came from Sojourn?
- Ragorn
Shar: Leave the moaning to the people who have real issues to moan about like rangers or newbies.
Corth: Go ask out a chick that doesn't wiggle her poon in people's faces for a living.
Shar: Leave the moaning to the people who have real issues to moan about like rangers or newbies.
Corth: Go ask out a chick that doesn't wiggle her poon in people's faces for a living.
Return to “T2 Gameplay Discussion Archive”
Who is online
Users browsing this forum: No registered users and 20 guests