SphereServer BugTracker - SphereServer
View Issue Details
0001804SphereServerexecutable - linux buildpublic23-08-10 16:4524-08-10 05:58
Mirravin 
khaos 
normalmajorsometimes
closedno change required 
0.56c Nightly 
0.56c Nightly 
Not Available
None
None
0001804: Spell is not in your spellbook.
New stupid problem in version #1312. Some characters can't cast spells at all, message: "Spell is not in your spellbook."(they have spells in spell, but can cast from scrolls only). But some characters can cast spells normally. I didn't find any differences in ACT type and other variables and had to return to version #1296.
No tags attached.
Issue History
23-08-10 16:45MirravinNew Issue
23-08-10 16:45MirravinNightly Version => Not Available
23-08-10 16:45MirravinExperimental Flags => None
23-08-10 16:45MirravinOption Flags => None
23-08-10 17:06jeemNote Added: 0000587
23-08-10 17:35MirravinNote Added: 0000588
24-08-10 01:20khaosStatusnew => assigned
24-08-10 01:20khaosAssigned To => khaos
24-08-10 01:25khaosNote Added: 0000592
24-08-10 01:25khaosStatusassigned => feedback
24-08-10 05:20MirravinNote Added: 0000593
24-08-10 05:24MirravinNote Edited: 0000593
24-08-10 05:55khaosNote Added: 0000594
24-08-10 05:58khaosStatusfeedback => closed
24-08-10 05:58khaosNote Added: 0000595
24-08-10 05:58khaosResolutionopen => no change required
24-08-10 05:58khaosFixed in Version => 0.56c Nightly
14-11-10 19:54MrSugarCubeCategoryexecutable - linux => executable - linux build

Notes
(0000587)
jeem   
23-08-10 17:06   
Could they be carrying more than 1 spellbook? Sphere checks the last one added to pack.
(0000588)
Mirravin   
23-08-10 17:35   
I know this. The same I said on the first complain on this problem. :) Answer - NO.
(0000592)
khaos   
24-08-10 01:25   
I have tested the spell issue. The only way I can reproduce this is via the two spell books conflicting with each other.

I am going to need more feedback, because every spell is working properly on the recent nightly releases with just a base script pack.
(0000593)
Mirravin   
24-08-10 05:20   
(edited on: 24-08-10 05:24)
I found reason. Reason is new t_spellbook_bard, which have number 193, but in my scripts type=193 is used for other thing... So for me you can close it, sorry.
But before closing 1 question: it is normally, that sphere is finding common spells on bard spellbook, its can be founded there?

(0000594)
khaos   
24-08-10 05:55   
Possibly improper morez values for your custom type affecting the book.
(0000595)
khaos   
24-08-10 05:58   
This is now a closed issue. Since it was never a bug to begin with. I hope we met with satisfactory feedback on this issue.