Cart Quest revisited

[PurpleYouko]

Apparently the quest is still not working.

It is interesting though that this time the sequence of monsters that I killed was totally different.

I initially killed 21 then the 22nd generated the 508-31 trigger and took the first certificate at both server and client.

The next 17 of them generated the 508-31 trigger but none of them took the certificate.
After that the next 8 did nothing. No trigger or anything.
The 9th one generated the 508-31 trigger again and took a certificate from the client. Nothing at the server.
The next few also generated the trigger but i stopped at that point.

I'm pretty sure that in the past on the official server i have had two almost in a row take the certificate after about 30 that didn't.
There doesn't appear to be any kind of pattern here. it is more or less random.

The only thing i am sure of is that the certificate is always taken when a block of triggers starts but not if the previous one generated the trigger.

21 kills with no trigger
18 kills with triggers
first one takes the certificate
8 kills no trigger
15 kills with triggers
first one takes certificate
14 kills with no trigger and so on.........

You should probably test this quest for yourself. it might make it easier
You need to be level 50+ then talk to mildun about carts
After talking to some other people, go back to mildun and he will tell you to get goblin workers to bury the certificates for you.
Although he says 'Goblin workers' he is an idiot and actually means 'Goblin Coal Mine Workers'
Just spawn a few of them and kill them to see what happens.

[Drakia]

I did test the quest, and it worked o.O I'll give it another shot.
Also, the initial amount that don't trigger anything before it starts counting the 15 is a random number. There's a % chance of it triggering the quest (3% for the first one, 7% for the next two I think it was)

Oh wait, had that wrong. It's actually

What should happen is
x kills with no trigger
Kill takes certificate
Triggers counter - 15
15 kills with trigger
x kills with no trigger
Kill takes certificate
Triggers counter - 15
15 kills with trigger
x Kills with no trigger
Kill takes certificate

[lmame]

Yeah the way it's working is a pain no matter they coded those kind of quests with their feet.
They changed the way they worked with quests a bit later, it's much better though on some quests (like red paper in main quest or even second job) you have to count each trigger and after the 15th you can only imagine the paper is gone (for example) as there is no different trigger to tell "ok it's done".

[Drakia]

Bah, had how it works wrong (Doing the quest now).
And yeah, the fact that you have a 3% chance of triggering the quest is a real pain in the ass :/

[PurpleYouko]

Maybe I'm being stupid here or something then.

Which files did you change for the mod?

The only changes i saw are in questconditions.cpp.

Also it definitely worked completely different today than it did yesterday at the client side.

Yesterday I had 15 kills with triggers after the first one took the certificate then only one without

Today there were 17 triggers after the first then 9 without

I don't see any regular pattern coming through. It just seems random

It kind of seems that it needs a non-trigger to reset it to look for the next trigger then after that just keep going till you get a trigger with that 3% chance again.
Possibly it switches from trigger mode to non trigger mode with the 3% chance and only takes the item on the first kill of each trigger block

Does that make sense?

And more to the point is it codeable?

[Drakia]

Alright, I just did the quest and it works. As I said, the order is

Kill x mobs with no trigger (3% chance of losing first item)
Kill takes first item
Kill 15 mobs with trigger (This is a counter to make sure you don't lose all the items one after another)
Kill x mobs with no trigger (7% chance of losing second item)
kill takes second item
Kill 15 mobs with trigger (Again, counter to stop insta-winningness)
Kill x mobs with no trigger (7% chance of losing third item)
Kill takes third item

Wow, I have no clue what you just said there PY o.O All I know is it's coded how it should be, and the only change as far as I remember was questcondition, yeah.

[Drakia]

The reason it works differently today than yesterday is because yesterday, if the item didn't exist, it would just return QUEST_SUCCESS, which was screwing things up badly. I changed it so it actually does the proper checks and returns fail or success based on them.

[PurpleYouko]

The reason it works differently today than yesterday is because yesterday, if the item didn't exist, it would just return QUEST_SUCCESS, which was screwing things up badly. I changed it so it actually does the proper checks and returns fail or success based on them.

I mean it worked differently at the client, not the server.
Over the last few weeks i have done this quest at least 5 times and every time it is totally different.
A totally different number of kills for each trigger block returned

[Drakia]

Me, ingame, after doing the quest. You can see the skill, no quest in my window, and the last check the server did in my chat window.

Well of course, it's a "Random" quest, you have a 3% chance for the first block of kills, then there's a 15 kill buffer, 7% chance for the next, another 15 kill buffer, and 7% chance for the last one.

[PurpleYouko]

Wow, I have no clue what you just said there PY o.O All I know is it's coded how it should be, and the only change as far as I remember was questcondition, yeah.

Hmm... Thinking out loud was I?

Here it is in a more coherent form
imagine that this is what is happening at the client. Don't worry about the server for now

1) trigger mode set OFF. (no kills give trigger response. Default start mode)
2) start killing mobs. 3% chance of changing trigger mode.
3) if 2 is successful then mode changes to trigger mode
4) on the first trigger take the item
5) trigger mode is set to ON still so keep generating a trigger with each kill indefinitely. 3% chance of switching back to trigger mode OFF
6) if 5 is succussful (turned off trigger mode) then no more triggers... indefinately go back to step 1 but with a 7% chance instead of 3%
loop till all 3 are taken

This seems more consistent with what i have recorded.
15 triggers in a row one day
19 triggers in a row the next day
5 triggers in a row last week

and so on

It does not appear to be fixed to a 15 length buffer