We felt like separating it from the procedure. Making it work in the procedure would have been the same thing, but since quests are barely used. There's no problem in adding a procedure as well.Quote:
Two things:
1. Why do you use a Trigger instead of a procedure that checks every single Quest that gets inserted in table dbo.CharQuests?
2. It is a SQL based Script. So changes on Items will only appear in Game after relog.Code:DECLARE @QuestID INT = (SELECT QuestID FROM inserted)
But still nice release.
And yes, it's obvious that it will require a relog (char screen is fine).