Cart Quest revisited

[PurpleYouko]

OK I just went through the cart quest again

Here is what i found.
when I kill the goblin coal mine workers this is the code that gets returned

Line number On/Off | Expand/Contract | Select all

1.  
2. Trigger executed 805-31[1]
3. Condition 000 returned 5
4. Condition 010 returned 5
5. Condition 004 returned 5
6.  

The first 10 or so give nothing then I get one with this code and the first item goes away (client side)
I'm pretty sure it also takes the first item server sided at this point too but i didn't check /listquest till after they took the first one.
The result for quest 805 at this point was

Line number On/Off | Expand/Contract | Select all

1.  
2. Quest[805] 0[0] 99[1] 100[1] 0[0] 0[0]
3.  

Looks to me like item 98 (Mildun's certificate) has already been taken

Up to this point it seems to be fine but after this it gets weird.
The next 15 mobs i killed give exactly the same trigger code every time.
The 16th one gave the same code but the second item was removed at the client. It was not removed at the server.
Then I killed another 15 of the stupid annoying goblin thingies and for every single one i got that same trigger code. Absolutely identical each time. The 16th one took the final certificate from my client but nothing at the server. listquest gives the same result all the time.
After that, I got no more trigger codes, no matter how many I killed

So this time, going back to mildun i still have two items as far as the server is concerned .
I'm going to try relogging to see what comes up in my quest window.

[edit] Re-Logged and now i have two of the certificates back again.

[edit2] After re-logging and continuing with the quest, the certificates continue to be take client side but they never go bye-bye on the server no matter how many goblins i kill.

[Drakia]

I'll take a look at this. And the reason it's the same trigger every time is cause that trigger is most likely a counter of some sort until it's over a certain number, then it does something else

How do you get this quest?

[Rescudo]

By talking to Mildun above level 50, choosing option 4. (That's for Evolution, as usual I assume it's at least going to be similar in pre-Evo.)

[Arnold]

it count 15 kills and than it takes a scroll
its the same trigger every time becouse of the trigger number in the npc stb
after you lost the first scroll it should start counting for the next scroll, but the server dosn't, the sever should go to the next trigger after it fails for the first one, becouse the first scroll is already gone.

[Drakia]

Ok, the problem was with checking an item, it would return success if the quest item didn't exist, I think it should return false, hence falling to the next trigger. I'm testing this out right now, and if it works, I'll commit. I'll also test a few beginning quests to make sure it doesn't break anything else.

[Edit]
Ok, apparently it should return fail if CheckNext is true, and success if CheckNext is false, hooray *adds*

[Edit2]
Ok, there's two ways I could do this. The check is a Val1 < Val2 check, I could do the return fail if checknext is true, or I could return success if it's doing a < check or <= check and the item doesn't exist. Ideas? For now I have the first way implemented. Gonna test with a new char on n00b quests.
Great, first method screws up MJB hunt at beginning. Will try second I guess x.x

[Drakia]

Alright, I found a method that works (Treat a non-existent item as a 0 count) Uploaded to SVN. Give it a shot.

[PurpleYouko]

I will give it a try in the morning.
Nice job Drakia.
I knew you would figure it out if i gave you enough detail

[Drakia]

Haha, yeah, give me details on a bug and I can normally hunt it down I'm just hoping I didn't break any other quests in the process, haha

[PurpleYouko]

This seems to be the way we are working in the osprose team now.

Most of the time, somebody reports an error (or i find it myself) I go and test it, get as much information as possible then you come along and fix it.

Good bit of team work

[Drakia]

Lol, indeed. So tiring though So, did that fix the quest? And did it fux0r any other quests? haha