I cleaned whole db becouse a instantly crash when press start char, but problem stills and in gs this error appears:
Quest:RaiseEvent¿¡·¯ : ÇØ´ç Äù½ºÆ®¸¦ ãÀ» ¼ö ¾ø´Ù [2]
Quest:RaiseEvent¿¡·¯ : ÇØ´ç Äù½ºÆ®¸¦ ãÀ» ¼ö ¾ø´Ù [2]
Quest raise event CRASH
03/07/2021 20:27
Beba Army#1
03/09/2021 12:55
Piskota#2
may be a bugged quest or event, use an older backup and if you dont get crash, simply compare the db's to each other. you know only how it was messed upQuote:
I cleaned whole db becouse a instantly crash when press start char, but problem stills and in gs this error appears:
Quest:RaiseEvent¿¡·¯ : ÇØ´ç Äù½ºÆ®¸¦ ãÀ» ¼ö ¾ø´Ù [2]
03/09/2021 13:57
Callum#3
[Only registered and activated users can see links. Click Here To Register...]
03/09/2021 16:55
Devsome#4
#moved
03/10/2021 00:57
Vaasneht#5
If the text of your error is written in purple, it’s just a warning, it doesn’t cause a crash. Try using a clean client, just in case you were messing around with the files on the media.pk2. That warning can ben fixed with ollydbg, the warning refers to the chinese and european tutorial quests.
03/10/2021 10:15
OKeks#6
Could you please run this query (change charname...) and write down all quest IDs:
You can ignore all quests with status = 4 as far as I know.
After writing down every quest ID on that char please delete all quests from that char and test for crash.
If it does not crash, add them back 1 by 1 and do the test everytime.
You should get the problematic quest ID if there is any issue with a single quest.
Note: if you clean the DB and create a new char, you will receive beginner quests, thus it is not fully secure to clean the whole DB only.
With the quest ID you can start checking for lua issues, for bad entries in database/media. You do not have to check for textfiles yet, it should work with missing text entries too.
Code:
declare @cn varchar(64) set @cn = 'China' use SRO_VT_SHARD select * from _CharQuest where CharID in (select CharID from _Char where CharName16 like @cn)
After writing down every quest ID on that char please delete all quests from that char and test for crash.
If it does not crash, add them back 1 by 1 and do the test everytime.
You should get the problematic quest ID if there is any issue with a single quest.
Note: if you clean the DB and create a new char, you will receive beginner quests, thus it is not fully secure to clean the whole DB only.
With the quest ID you can start checking for lua issues, for bad entries in database/media. You do not have to check for textfiles yet, it should work with missing text entries too.