Trouble Adding A Quest

[Herosworld]

I have a similar problem to Pdtk.
I cloned a quest, and picked and NPC that already could assign quests. I added the Quest ID to the NPC's Receive and Activate Quest list, and i can even get it to show up in game.
The Dialog for the Quest progresses as it should, but when the dialog completes, nothing happens.
The Quest isn't added into your quest list, and the quest for the NPC is still available.
The final dialog does link to the proper quest ID.
I have no idea as to what to do next.
Is there another quest Database or list or something that i need to add my Quest ID to?
I am really close to getting this to work, and i want better funner quests...
(I am aware that a thread similar to this has been posted, but the thread was too old to reply to and the discussion immediately got off topic. I want to try again at this subject.)

[MentaL]

[angelmx]

Add the ID quest in NPCs you have to do whit a elements editor looks for the npc puts the IDs and have to work

[Romulan]

Too high IDs for the quests.... 180k+ will not work.

[Herosworld]

Sorry anglemx, but i don't really know what you said...
Romulan, why does the ID size matter, is it due a memory confliction or something. Furthermore, if the Quest ID was the problem, you would think it wouldn't work at all, but it does, kinda. It shows up in the NPC's dialog, just, when you finish talking to him you never recieve the quest in your quest list.

[avalanche3]

Did you add the quest to the NPC's active and receive quests in elements.data?

[Herosworld]

I seriously thought you were wrong Romulan, with the too high IDs comment, but I tried reducing the Quest Id to 29999 instead of 189001, and it worked!!! What's the highest ID you can use?
Any idea why the ID size matters? It’s just a number to link the databases right?
Thanks Romulan.

[Romulan]

Because it's a binary logic limit. Like for the gshop, you can't have IDs higher than 32768 (65536 divide by 2).

But for tasks.data I will assume that's 65536 or 72k something.

[das7002]

Because it's a binary logic limit. Like for the gshop, you can't have IDs higher than 32768 (65536 divide by 2).

But for tasks.data I will assume that's 65536 or 72k something.

It's also possible that they just have a hard limit and aren't using shorts... (after all they did use whole ints for the zone limits on elementclient instead of bytes/bools)