Empty quest list

[Ghurdyl]

L2J Revision:4360
L2JDP Revision: 7604

Hello,

This is the second time I face this problem:
One of my player cannot see his quests in the quest menu (alt+u).

The fist I tried deleting all quests for this character.
As a saw that after this, new quests where visible I rolled back and tried to delete quest one by one until I find that the quest responsible of this was "War with varka silenos" (id 606).
I don't know why but deleting this quest fixed the bug.
I looked at the data stored in DB for this quest and I did not find anything special.

Today I have been reported the problem again. A player cannot see her single quests and this time I am kinda lazy to find which quest is responsible of it. (as it is not the 606)

Does anyone have an idea of what's happening ?

As we try to keep our server up to date, my first idea is that after an update of some quest, data stored in DB may be incoherent with the new script (like variable "cond").
But I am not sure of it and it's hard to demonstrate...

Thanks for any input.

[Gnacik]

Try to find quest with cond value not existing in client files.

[Ghurdyl]

That's a good idea.

But I have never tried to open client file

Could you tel me what file(s) I should check and what program should I use to read them ?

[janiii]

just check l2jdb: http://l2jdp.com/l2jdb/db_quest.php?id=606

[Ghurdyl]

thanks janiii,

did not think about the DB either.

But just a question about it, is it always kept up to date in synchronization with the datapack / gameserver updates ?

[janiii]

l2jdb is updated from l2jdp every night automatically.

could you post the values of the quest from db? what the player had in the war with varka in character_quests table.

[Ghurdyl]

Unfortunately, the problem with that quest was about 4 month ago.
And I don't remember the values they had.

This time, the problem is probably due to anther quest (as the character doesn't have it) but I don't know which.
If I find out, be sure I will update this thread.

I will compare the value that I have for the different quests of this character with the values given in the l2jdb and see if I find anything suspicious.
But as it is quite long job (about 30 quests to check), I won't do this before the week-end I think.

Thanks anyway for your invest.

[janiii]

check if he has some varka or ketra quest (war/alliance).

[Ghurdyl]

Hello,

As promised, here is my report

I found the buggy quest : 636_TruthBeyond.
For some reason, the "cond" value for this quest was "2" and only "1" is available according to the l2jdb database.

I changed the value to 1 and I could see every quest again.

I also noticed what I consider as very small incoherences : some completed quests have a "cond" value stored but are completed.

[Gnacik]

You are using custom quest scripts ? Because we don't set cond=2 in 636_TruthBeyond

[janiii]

that was fixed on 27.12.2009 . so when a player made the quest before this date, he can have cond 2 and bug his quests. maybe only this quests in a combination with other quests makes the quests disappear, not always.

[hope]

when you update quest s from timeline you need to also update then in navicat not do this will cause problems

[Ghurdyl]

@Gnacik : No I don't use custom script for this quest.

@Janiii : I have noticed indeed that 6 players had the bug.
None of them could see the list of "single" quest.
Fixing the bug solved the problem for at least 3 of them ( I did not check for the 3 left, satisfied by the result) but, as you mention it, I think so that this could be a combination of more than one quest.

@hope : I don't get your message. What do you mean by "update quest from timeline" and "update then in navicat" ? (don't event know what "navicat" means)



I have informed my players that such bug exits so if anything comes up I may update this thread.
Thank you all for your advices.

[janiii]

when you update quest s from timeline you need to also update then in navicat not do this will cause problems

he cannot check every commit. the update script for the quest cond should have been in update sql scripts.

[Gnacik]

Now it is... 7631