Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=10287





------- Additional Comments From acedit AT armory.com  2006-01-03 16:54 -------
it must have been delve that was the problem, as thats the only way the spells
could be absent from the activity log with their triggers enabled.

So one of two things happened:
1) user used delve which continued through the succession of files, including
TRIGGERS file, then proceeded to not run spell success and probably ran
spell_failure. I vaguely recall some issue with delve not stopping after
failures. I'll look into that. Of course, this is probably easily reproducable
with delve TRIGGERS foo, but running that by itself is kind of like shooting
yourself in the foot.

2) For whatever reason one of the steps in dispel failed, causing the trigger
removal to be skipped, and subsequently also skipping the part of dispel the
activity log indicates it completed. Dispel should probably note a failure to
dispel as well, it could also put the spell in a 'dispelling' state in 
packages.
Either would help catch the bug if its this scenario.

I'll look into both. Any additional information that helps confirm or deny the
plausibility of the above two scenarios would also be helpful.

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.