I have another post in win32 server support, describing this problem, here I am quoting myself.
"It happens to my 5.1 server and most 5.1 server I have tried to connect to.
I have seen dozens of posts regarding this issue, and sounds like it is because some old scrolls in the item table that pointed to wrong spells. But after I checked the item table (from tcsmyworld's latest database), take minor shielding scroll for example, both the nodrop one with a star in the name and the normal one, they both point to spell 288. And I checked spell_en.txt, it is indeed spell 288. And I can also use #cast 288 to cast this spell in game. So I dont understand where does the mismatch come to play? Is it because of the level requirement of that spell? then which field has that information in which table, and how can I correct this problem without having to manually correct them one by one? "
Regarding the level requirement, I just checked myself, clearly not in the item table. Is there another table which describes spell level requirement?
The symptom? when you tried to scribe a spell, it says "error scribing spells because you can not use spell at that level" or something like that. And then the client input is frozen. THen if you are a GM, sometimes you can get around this by giving yourself a few levels up, then you can scribe the spell into your book, but when you tried to memorize this spell, you got same error. Then if you port an old character in who already got that spell memorized, and you tried to cast it, you will get same error again. So in these three different instances I observed this error.
I know it may has nothing to do with codes like the developers has repeatedly said that, but when I use tcsmyworld's lastest database, it works fine with 5.0 but not with 5.1, it make you think something has been changed in 5.1 that contributed to this problem. Clearly it wasnt the Renaming of the two fields in item table. Then it must be something else.
Anyway, I hope someone who knows can help. Because I saw in some 5.2 servers they dont have this problems any more. They are still using tcsmyworld's db I am pretty sure, did they change something in their database, or the 5.2 code is changed, that, I know nothing of.
|