8 réponses à ce sujet

[xorbaxian]

i seem to remember reading a few posts about nwn crashing if a character has more than 255 spells in his spellbook. however, this thread seems to imply that bioware programmer craig welburn noted the problem was fixed in release 1.69. does anyone know definitively if there really is a limit to the number of spells a builder can add to a module and make available for a specific class to learn?

thanks

[FunkySwerve]

The limit you're referring to was for memorized spells, not spells available or known - despite what it says in that link. Characters with a crapton of spellslot gear would cause crashes, and we had code in place to block equipping of gear that would put them over..

I'm not aware of any limit to spells known; we've added quite a few arcane spells without any issues. Granted, we only have 236 arcane spells at the moment, so it's possible that's an issue.

Funky

[Shadooow]

the limit was indeed related to number of known spells (wizard), and I also heard its fixed but afaik noone ever confirmed it, i abadoned PRC long time ago, but I guess it would nt be that hard to proof it...

Modifié par ShaDoOoW, 27 septembre 2013 - 09:37 .

[FunkySwerve]

No, it was definitely memorized spells, though as I said, it might have been the other as well - it stands to reason. I can post the code we were using to circumvent it pre-patch, if I really have to.

Funky

[Shadooow]

FunkySwerve wrote...

No, it was definitely memorized spells, though as I said, it might have been the other as well - it stands to reason. I can post the code we were using to circumvent it pre-patch, if I really have to.

Funky

No, it was definitely known spells what was problem before, what he is asking and what is supposed to be fixed in 1.69. I know that absolutely sure because my PW had PRC in that time and some wizards were crashing a game because of it. That your PW didnt encountered this issue doesnt mean that its not there.

[FunkySwerve]

ShaDoOoW wrote...

FunkySwerve wrote...

No, it was definitely memorized spells, though as I said, it might have been the other as well - it stands to reason. I can post the code we were using to circumvent it pre-patch, if I really have to.

Funky

No, it was definitely known spells what was problem before, what he is asking and what is supposed to be fixed in 1.69. I know that absolutely sure because my PW had PRC in that time and some wizards were crashing a game because of it. That your PW didnt encountered this issue doesnt mean that its not there.

No need to get snarky. If you actually read what I wrote, I specifically acknowledge that known spells could've also been an issue - I in no way claim that 'it's not there' because HG didn't hit that limit. See specifically: 'it might have been the other as well - it stands to reason.'

However, I'm quite certain that memorized spells was the source of crashes for us. The corrollary to your logic above is of course that if it WAS an issue for us, it was obviously a bug.

I also exchanged pms with Biowareans about it while I was pelting them with every possible bug report under the sun, trying to get everything fixed before the last patch (and trying to get them to add things like the ability to add new weapon vfx). I even included our code, which counted up added spellslot props and blocked the equipping of items with more spellslots if it'd take them over the limit. I actually just looked for a module rar that still had it, but it looks like we ditched most of the rars after our last move - I have a complete chain back to 2010, then nothing till a legacy rar from 2006, which was well before we had enough spellslot gear in the game for this to have become an issue.

Should neither of those points convince you, I'll fall back on the words of a not-so-wise-man: 'that your PW didn't encountered (sic) this issue doesnt (sic) mean that its (sic) not there.' 

Funky

[Shadooow]

I guess I didn't understood then, are you saying that crashing due to the too many memorized spells have been fixed in 1.69?

Still that doesn't mean the Craig Welburn or whoever wrote that list meant this. The known spells crash might have been also fixed. Nevermind, I guess its up to the OP to test it, test requires server running with dozens new spells for wizard and scrolls to allow wizard learn them and a client wizard that will teach them and try to relog.

[WhiZard]

I do recall pre 1.69 discussions on crashes when a character had too many spells known. I do not remember the circumstances, but the NWN wiki has a comment concerning crashes for too many spells in a spell book. Apparently this bug was reported before the 1.69. It is possible that the 1.69 fixed both the memorized and known spell issue, or the two issues were inherently linked the way the data was stored. On the other hand, 1.69 also has points of misdocumentation, so fixing one problem while describing another could be a possibility (e.g. look at the 1.69 added notes for AdjustAlignment()).

Modifié par WhiZard, 28 septembre 2013 - 05:04 .

[FunkySwerve]

ShaDoOoW wrote...

I guess I didn't understood then, are you saying that crashing due to the too many memorized spells have been fixed in 1.69?

Yup. It's possible, however, that I'm remembering a patch before 1.69, which is why I was quick to yeild on your suggestion that the other was an issue as well. I'm pretty sure it was actually 1.69, but this was years and years ago, so...

Still that doesn't mean the Craig Welburn or whoever wrote that list meant this. The known spells crash might have been also fixed. Nevermind, I guess its up to the OP to test it, test requires server running with dozens new spells for wizard and scrolls to allow wizard learn them and a client wizard that will teach them and try to relog.

I agree. I was more focused on answering the OP to the best of my knowledge, as were you. At this point I think we've both done that, and are just hashing out our respective recollections.

Despite not being able to find the old code, I did find a reference to it, and the issue on our forums, in 2007:
Link

Funky