GameBanshee Forums

Hi there. I've finished the first Kilpatrick quest, which was setting Carson free from Gimble.

I did, and so says my quest log, advising me to go back to Kilpatrick and tell him the good news.

Problem is, the dialog option doesn't show up, and all I can tell Kilpatrick is something like "I'm still chasing after Carson". Consequently, the quest doesn't end, and I don't get the next one, which, if I remember well, leads to a cool series of werewolf-hunting sidequests I'd really love to play once more.

Unfortunately, I realized a bit too late that the quest was crashed to simply reload - I'm in Hollywood now and it would be a real pain in the arse to have to reload. And err, I'm pretty sure I erased the save anyway.

I saw, in another topic here about Kilpatrick getting stuck, that there's a console command that could, maybe, fix this kind of glitch :

__main__.FindPlayer().SetQuest("Questname", queststate)

I tried every possible way of typing the quest name, and every possible "queststate" like Complete, Done, Finished, whatever. No way, it doesn't work, telling me that my command line is wrong.

Can any of you tell me what I'm doing wrong? That would be really great.

Thanks in advance...

Alchemica wrote: __main__.FindPlayer().SetQuest("Questname", queststate)

You can find the questnames in vampire/vdata/system/quests_* and the queststate is a simple number also found in those files. In case of your problem the questname would be "Arthur Knox" and the queststate 5.

wow gold

Cheapest Gold @ WOW Gold,Buy WOW Gold,Cheap WOW Gold,World of Warcraft Gold
10kGold for 75usd ! Secure Manual Powerlevel + Cheap Accounts Too !
While Stock Last ^^
Paypal World Seller + Macfee Secured Site ^^
USE WOW GOLD COUPON CODE for 5% Bonus : WOW2200

Wesp5 wrote:You can find the questnames in vampire/vdata/system/quests_* and the queststate is a simple number also found in those files. In case of your problem the questname would be "Arthur Knox" and the queststate 5.

Thanks a lot! Now let's go hunting...