Forum :: EOSERV :: EO+ Quest Guide

Sacred Phoenix posted: (31st Aug 2010 07:44 am)

Im sorry for posting in a Dead topic but i thought it would be better to post it here instead of making another topic over it.

I tried making a quest and i get to State KillRats and when ever i kill the 5 rats i needed to, it still just says Kill 5 Rats and never continues to the Reward. I know this quest is bad but its just a test for me.

Can anyone see why its not going to Reward? I read Apollo's guide which helped alot but cant seem to get it to complete the whole quest and i dont want to do    SetState Reward.

Main

{

questname "Test Quest"

version 1.1

}

State Begin

{

desc "Talk to Susan"

action  AddNpcText(1, "Hey there this is a Test Quest.");

rule TalkedToNpc(1) goto KillRats1

}

State KillRats1

{

desc "Agree to kill the rats"

action AddNpcText(1, "Could you kill 5 rats for me?");

action AddNpcInput(1, "Ok");

rule InputNpc(1) goto KillRats2

}

State KillRats2

{

desc "kill 5 rats"

action AddNpcText(1, "Return to me for the reward when your done");

rule KilledNpcs(2, 5) goto Reward

}

State Reward

{

action GiveExp(100);

action GiveItem(1, 500);

action End();

}

it is because you put in an InputNpc and never ruled it lol

---
Qbot/null

I did your way and it still only gets to the "Kill 5 rats" and never goes past it.

---
Owner of Endless Online Insanity
Looking for: 2 Artists
Darkrulerjoe

did you even kill 5 rats? cause it's kinda weird lol

---
Qbot/null

It is most likely the fault of the quest reader. Your code looks fine.

Sacred Phoenix posted: (31st Aug 2010 07:16 pm)

I did your way and it still only gets to the "Kill 5 rats" and never goes past it.

Could be that your NPC "Rat" has an other NPC ID?

---
"Pineapples and shit."

There was a legit problem with Addison's release. To my knowledge this has never been fixed. The problem is file read size vs. file actual size. What happens is even a simple quest can utterly fail at a given state without warning via error message. It is nothing to worry about at this time.

Ok thanks apollo. Will this problem be fixed when you release the Main server version? If so then i guess i can just work on Pub/Maps intil you release it. So your release will still be using EO+ Quest right?

---
Owner of Endless Online Insanity
Looking for: 2 Artists
Darkrulerjoe

Yes, my server will use a hybrid version of the Quest reader. The original EO+ reader written by Sausage + a few fixes Bart helped with will be replacing quest.cpp, quest.hpp, and Quest.cpp. I have tested this code against all 13 EO main quests handed to me from Vult-r himself. All quests are working nicely and I have played through each and every one to ensure there are no  breakpoints. A notable change is in this new version there is no need for the escape character "\" to precede an apostophe. Including one will consider this a comment and cause a problem. Other than that, you will have no problem using my guide and making a nice quest. I may even include a model quest or two that I have written as an example.

Is there a working quest code now were is it id like to be on testing

always playing with the code lol

I had another question about the quests. Is it possible now and if not, will it be possible to make a quest have a requirement of a certain Class/Lvl to do it? I was going to make quests that are only for certain classes and have some quests only for high lvls etc.

---
Owner of Endless Online Insanity
Looking for: 2 Artists
Darkrulerjoe

To begin the quest, maybe not. It would in fact be ugly and hard coding to restrict. To meet a rule requirement that would work, but you may want to force the quest onto a set of maps where no "wise man" type character resides. It seems very easy to go change back once a rule is met, right? Also, you may want a "Lost Class" rule as well to revert back in case the class has changed before you speak to the quest NPC.

A friend of mines has a test server and it's funny to test these quests on.
In any case I don't really understand some things.

The getting started part of the guide, organizing the quest IDs/Npcs.
Can someone explain me that in a more uh, easier way.
I don't know if it's just me, but I don't really get it.
And I'm sorry for bumping this old topic, but I think it's better then making a whole new one.

Thanks in advance.

roefl posted: (28th Apr 2011 12:43 pm)

A friend of mines has a test server and it's funny to test these quests on.
In any case I don't really understand some things.

The getting started part of the guide, organizing the quest IDs/Npcs.
Can someone explain me that in a more uh, easier way.
I don't know if it's just me, but I don't really get it.
And I'm sorry for bumping this old topic, but I think it's better then making a whole new one.

Thanks in advance.

Its simple. The quest always must start with talking to an npc. That npc take a quest id inside the quest. Lets say the number 1. So the first command to start your quest is: action  AddNpcText(1, "put thext here"). You put that id number there. That same number you add it on pub files. You find the npc that you want to start that quest with, you change the type of npc to type "15.quest" and you type that id number in there. In your example is the id =1. You save that quest with the same name as your first npc id. 0001.eqf
The quide means that your Npc might have npc number like 100, 101, 200 etc. That is the pub number and dont related with any way with quest id. You are the one that connect each npc with the quest by adding the quest id number inside the pubs.