Proposed2nd and Proposed3rd are using quest numbers other than 0. We cannot test those proposed quests unless the quest numbers in the header are set to 0.
Error: Not a custom quest
HELP! Proposed2nd and Proposed3rd not custom quests!
Well, you can rename them to 2nd.qst and 3rd.qst, but that kind of defeats the purpose of releasing them separately, I agree. I'll fix this in the next build, and depassword them while I'm at it.
yay, or update the example versions of the quest too thus you can have a passworded one and not a passworded one.
tho ii dont see much gain in this at the moment xD
Fixed in the next build.
Okay, I grabbed the new proposed quests from the Linux build 467 and imported into the directory of the last Windows build 461. They are now accessible. Dead bug. 😊
Don't test on builds less than 461!
Note: I cannot test on Linux, or Mac builds. My operating system is Windows Vista Home Basic and it works here without fail.
This bug is already dead. Read the post above.