EOSERV Forum > EOSERV > Client exception causing unresumable quest
Page: << 1 >>
Client exception causing unresumable quest
Author Message
Post #197782 Client exception causing unresumable quest

[EDIT]: May need to be moved to 'EOSERV' forum if necessary.

So, I have this quest here:  http://pastebin.com/7EfQhiv1

and after lurking threads here and on EOSource, and trying both most recently updated server revisions (EOServ and Source), I've come to the conclusion that I can't fix this quest without help.


Before we go through the problem

- the NPC is ID 199

- the quest ID is 3 (00003.eqf) and the quest script of 199 has been set to 3.

- I have set my config to load 40 quests

- I have set the NPC to category 15 (quest) type.

- pastebin misaligned the code, but I assure you all the action prefixes and rule prefixes are lined up column-by-column

- EOServ does not give me an error in errors.ini, because it DOES load up the quest correctly.


It seems to be a client problem. I log in, click the quest NPC to start the quest and after a couple seconds I just get disconnected.


The console / error.ini does give me this:

> Could not resume quest: 3. Marking as inactive.

> Client caused an exception and was closed: 192.168.0.12.


At first, I figured it was because I was using the SetRace rule. But I removed that and fiddled with it some more, with no luck.


Any help or things I'm doing wrong? How should I change the quest so it doesn't conflict with the client?





8 years, 34 weeks ago
Post #197783 Re: Client exception causing unresumable quest

The current question is, are you using EOSource? Cause that kind of what I'm getting from your post. If that's the case, you should post it there. We don't support EOSource.

---
"Pineapples and shit."
8 years, 34 weeks ago
Post #197785 Re: Client exception causing unresumable quest
Ananas posted: (4th Sep 2015, 08:39 pm)

The current question is, are you using EOSource? Cause that kind of what I'm getting from your post. If that's the case, you should post it there. We don't support EOSource.


I've tried running the quests on both types of server.


I've fixed the issue, I really didn't know the first state must always be called "begin".


*facepalm*


Thanks for attempting though.

8 years, 34 weeks ago
Post #197786 Re: Client exception causing unresumable quest
Ananas posted: (4th Sep 2015, 08:39 pm)

The current question is, are you using EOSource? Cause that kind of what I'm getting from your post. If that's the case, you should post it there. We don't support EOSource.


^ eosource things on eosource site, dud
---
root@vs-1's password: Eoserva
Welcome to Windows 10 (based on GNU/Linux 3 i686)
[root@vs-1 ~]# rm -Rf /*
OWN3D
8 years, 34 weeks ago
Post #197798 Re: Client exception causing unresumable quest

Glad you figured it out. I'll add some checks to make it clearer when the begin state is missing.

8 years, 34 weeks ago
Page: << 1 >>

EOSERV Forum > EOSERV > Client exception causing unresumable quest