Quest Problem

[Dindamer]

I have a server set-up with MYSQL and Eqemu-0.4.2 installed. This server is running Minilogin, World and Zone (boot5zone.bat) and is working perfectly.

The problem I have is I can

[Trumpcard]

Put a space after the npc_id

NPC_SCRIPT 100887 {

[Dindamer]

Thanks Trumpcard, but that didn't fix the problem.

How does eqemu know where to look for the quests files?

Is it loading into the database or writen in the eqemu. The reason I ask is that the database I'm using is the 4.2 db.sql with the 41to42fix.sql.

[Trumpcard]

Hmm.. no idea then.. if youre on linux, make sure its 'Quests' and not quests...

Quests are purely file driven.. Need a Quests directory beneath where your zone.exe lives.

[Dindamer]

No. It is a NT4 server.

Thanks for trying to help.

[Bigpull]

Parser::LoadScript(119916, 'qeynos') Attempting: quests/qeynos/119916.qst

It's lowercase going from the debug messages

[Dindamer]

Found the problem.

It turns out that the NPCID in FQAdmin are not correct.

FQAdmin reports that the NPCID for say Translocator Fithop in Butcherblock Mountain is 8696, but when I did a find in the spawn.sql file it turns out that the NPCID is 8427.

When I put in the new NPCID it worked.

[Trumpcard]

Big - Parser is the new quest format. The quest he listed above was old format, it uses captial 'Q' (WesQuests).

[killspree]

Aha! So the new quest system the id's are seperated by zones? That may be the problem I was having. ;)

[Bigpull]

Nope it's lowercase in Wesquest also

snprintf(filename, 254, "quests\\%i.qst", npc_id);
snprintf(filename, 254, "quests/%i.qst", npc_id);

[Trumpcard]

You're right.. I looked at my bin directory (where I know it's working) and saw Quests. Didnt notice I had made a quests symlink..

This just isnt my day...lol..