Broken: Jeets on Korthos

[Evean]

1. Signed in after character creation.

2. Spoke to Jeets (“Can you talk? Speak to me.”)

3. Accidentally selected “Do the quest” instead of “Skip.”

4. Jeets runs up the hill, to where you’re supposed to speak to him for a weapon.

5. Logged out, intending to delete, reroll, and skip the starting quest. Decided “eff it, it’ll take longer to reroll than to do the stupid quest.”

6. Logged back in, Jeets is now back in his starting location. (“Can you talk? Speak to me.”)

7. Selected “Skip”

8. Nothing.

Looks like I’m forever trapped on baby island.



Preemptively: Yes, I can select “Do the quest,” or delete and reroll. That’s not the issue. It’s still janky af, Jeets is changing locations between relogs, offering choices that can’t be made &c.

[rabidfox]

Did you wait at least 5 minutes for the old quest to fully despawn? I assume it's shoving you back into the existing instance.

[Evean]

Did you wait at least 5 minutes for the old quest to fully despawn? I assume it's shoving you back into the existing instance.

I’m not certain I understand what you mean by “despawn,” but I think it’s a moot point. If it were in fact putting me back into a existing instance;

a) it’s doing so after a manual relog

b) npcs are changing location, and offering impossible choices

[rabidfox]

I’m not certain I understand what you mean by “despawn,” but I think it’s a moot point. If it were in fact putting me back into a existing instance;

a) it’s doing so after a manual relog

b) npcs are changing location, and offering impossible choices

Instanced zones (quests, airship, etc.) take 5 min (some people have reported seeing things despawn faster lately) for an instance to despawn(reset - same thing manually resetting an instance does, no longer exist, etc.) after no humans are left in the instanced area. Quitting the app and relaunching doesn't change the timer for that(it's server side, not local); so if you're re-entering the same instanced area over again faster than it despawns then it'll likely keep bugging out. Now if it's completely still bugged after it's fully reset that's a different issue, just checking to make sure it's a fresh instance that you're actually in that's bugging out (and not just stepping back into the same one over and over).

[Evean]

Instanced zones (quests, airship, etc.) take 5 min (some people have reported seeing things despawn faster lately) for an instance to despawn(reset - same thing manually resetting an instance does, no longer exist, etc.) after no humans are left in the instanced area. Quitting the app and relaunching doesn't change the timer for that(it's server side, not local); so if you're re-entering the same instanced area over again faster than it despawns then it'll likely keep bugging out. Now if it's completely still bugged after it's fully reset that's a different issue, just checking to make sure it's a fresh instance that you're actually in that's bugging out (and not just stepping back into the same one over and over).

Then I correctly guessed what you meant, my previous points still apply, and our conversation is orthogonal to the topic at hand.

[acemonkey]

I’m not certain I understand what you mean by “despawn,” but I think it’s a moot point. If it were in fact putting me back into a existing instance;

a) it’s doing so after a manual relog

b) npcs are changing location, and offering impossible choices

It's pointless for the devs to code every single thing in game to react well to a player trying to exploit break it by relogging midscript

[Dragavon]

Things that stop working when you use them in a way they are not intended to be used are not broken.

User error.

[Evean]

It's pointless for the devs to code every single thing in game to react well to a player trying to exploit break it by relogging midscript


Things that stop working when you use them in a way they are not intended to be used are not broken.

User error.

You’re both incorrect, and neither of you understand the situation. There’s no exploit here. I’ll try to simplify it for you:

Between relogs, Jeets on Korthos changed locations, and his dialogue menu options no longer function properly.

[Targal]

If you decided to try the tutorial on the jeets dialogue option, then you can't skip it any longer. the dialogue only shows the options which don't work.

[Lonnbeimnech]

>hey guys, I found a cool way to break a quest.

Oh it's not broken you just have to...

>T-THAT'S NOT THE POINT!

[WhateverDisplay]

a.)
The behaviour is clearly a bug. All that OP has done report a bug. It doesnt matter whats causing it, its a bug.
If a dev allow users an action resulting in a bug, its the developers fault and not the users. Read up on "lil bobby tables" for illustrated instructions.


b.) Is this a severe bug, causing issues?
Probably not, though I do understand, as I hate those quests myself.


Dont blame the user for showing the problem (no matter how possibly stupid the behaviour might have been),
but either address the problem with a fix or explain, why its staying like that.

[J1NG]

Once you have spoken to Jeets, the "Speak with the Rogue, Jeets Shimis" quest is ticked off. That area is an explorer area, so it's really more like the quests that ask you to get to the Spirit Binder and bind yourself that you get when first reaching Eveningstar or to the Harbor. This tick is not removed on waiting 15 minutes because it can only be fully completed one way. It's more like a "state". This state controls what Jeets will do or speak and the skip option is really only offered at the start before it is ticked off, as the skip dialogue then completes the rest of the quest objectives for you.

I imagine this is done this way because this is to allow normal first time players a proper guide to show them where to go, etc. and if they log off/DC and return, they need a proper continuation, which is what this state offers to them.

I am unsure what would happen if this state is altered for the benefit of veteran and experienced DDO players at the sake of new players, but I doubt it would be good. Since it would mean players who DC'd inside the first area, may get stuck since they can't talk to Jeets, Talbron or Cellimas to continue at the various waypoints inside the grotto quest, which would have been the fail safe option that's offered by this state that is set for this initial area by performing an automatic reset to the default "Speak with Jeets" part again.

No change is really needed, because it would mean changes to stuff that isn't broken (code wise) to be messed with (to potentially introduce something that could be broken).

If you have done this mistake, simply take a course of action; complete the grotto asap, or delete and restart. It's much faster and is known how to be resolved, rather than get the Devs to work on something that could introduce other points of failure here or elsewhere, at the same time taking away from other more essential bug fixes or features.

J1NG

[Tist]

Yes, it's broken, and it's been like it for years. I experienced it a couple times, over 3y ago. Probably just always been coded in a janky way.
The only scenario I can see that delete and rebuild doesn't really help is when you are on a first toon on server, and have first toon rewards that any subsequent toons won't get. This was what happened to me. I decided screw that server and picked another one. Alternatives are accept the loss and move on, or contact support and ask for the items to be restored to this new second toon. Don't bother asking them to fix the instance, you won't have that happen, days later you'd still be standing there doing nothing.

[Mindos]

Did you wait at least 5 minutes for the old quest to fully despawn? I assume it's shoving you back into the existing instance.

Anyone test this? Does the grotto intro reset? I don't eve n know.

[Cordovan]

I think Jeets goes back to the beach if you log out after selecting to do the quest so that a new player who didn't know to go up to the camp site would be able to follow Jeets again upon subsequent log-in. You are correct that the NPC dialog should either no longer give you the option to skip the story if you can't or allow you to skip. Thank you for the report!

[rabidfox]

Anyone test this? Does the grotto intro reset? I don't eve n know.

I don't know either; which is why I tried asking the op if they'd let it sit for longer than 5 minutes to see if it made a difference but I never got a response about them trying it. It might do nothing but that was only possible option for trying to deal with it I could think of (outside of waiting for a bug fix).

[J1NG]

I don't know either; which is why I tried asking the op if they'd let it sit for longer than 5 minutes to see if it made a difference but I never got a response about them trying it. It might do nothing but that was only possible option for trying to deal with it I could think of (outside of waiting for a bug fix).

Not sure if they tested, but I already did here.

Once you trigger the talk state and chose anything other than "Skip" option, it progresses the state of the "quest" to the normal Grotto quests. No matter how long you wait, 5 minutes, 15 minutes, it'll stay at that state until you complete the Grotto. No amount of waiting will help.

On the other hand, if you chose the skip option, it'll complete all the optionals and give you the option to pick your reward. At any point here, you can still do the Grotto quest, again also after any waiting and reset of instance, but the moment you pick up the reward (available anywhere when you log in) you will automatically skip the Grotto quests, even if you end up going through and are in the middle of it (like the key in the water), just pick reward and skip.

J1NG

[Enoach]

I think Jeets goes back to the beach if you log out after selecting to do the quest so that a new player who didn't know to go up to the camp site would be able to follow Jeets again upon subsequent log-in. You are correct that the NPC dialog should either no longer give you the option to skip the story if you can't or allow you to skip. Thank you for the report!


Not sure if they tested, but I already did here.

Once you trigger the talk state and chose anything other than "Skip" option, it progresses the state of the "quest" to the normal Grotto quests. No matter how long you wait, 5 minutes, 15 minutes, it'll stay at that state until you complete the Grotto. No amount of waiting will help.

On the other hand, if you chose the skip option, it'll complete all the optionals and give you the option to pick your reward. At any point here, you can still do the Grotto quest, again also after any waiting and reset of instance, but the moment you pick up the reward (available anywhere when you log in) you will automatically skip the Grotto quests, even if you end up going through and are in the middle of it (like the key in the water), just pick reward and skip.

J1NG

Based on this, it seems the more straightforward course of action would be to exclude the 'skip' option from the dialog when the 'skip' option was not chosen initially. This goes with the theory of UI design that you should not offer an option to your user that you don't want them to take.