@AusRoona
If you could, it would be helpful to know which quests are resetting early - that way I can take a look at closer look at my configuration to make sure all is good there.
But based on the current reproduction steps - I haven't been able to re-create thus far.

I will put this on my to-do list to look into more in-depth on my days off.

 

I can confirm this happening with some of my daily quests. Perhaps the completion time may help narrow something down. (All times are in ET, so server time.)

• AlchemistsErrand -- completed 1:05 AM.
• GlimmerInTheDark -- completed 2:54 AM.
• BareBarkQuests -- completed 1:32 AM.
• CraftCookCreate -- completed 2:49 AM.

Unaffected are:

• EchoesOfTheAnvil -- completed 1:25 AM.
• SpectrumofShades -- completed 1:13 AM.

I don't think moving across servers affected my quest completion, but rather a server restart may have. I know reproduction was tested without success. I am not sure if only cross-server quest completion was checked, or if quest completion before and after server restart was tested as well. Perhaps something isn't being saved correctly in some process that server change and server restart share in common?

 

@ChefCraft19
@AusRoona
@RealRichNixon
@Skylexia

We've made some changes to try to narrow down the issue of the early quest resets.
Please pay close attention to your quests and reply back here if they continue resetting early.

 

@ChefCraft19
@AusRoona
@RealRichNixon
@Skylexia
@314
@tanger91

Have any of you noticed any of your quests resetting early in the last week or so?

 

I have not.

 

Speaking for myself, I have yet to experience the connection bug since the changes were made (on Oct. 24).

 

Actually, earlier today, I noticed /jobs wasn’t working at all over on MN. Wasn’t sure if that was intentional or not. I wasn’t earning any jobs XP on MN for the jobs I’m in on M either.

 

Interestingly enough, after posting my previous reply, I have experienced the disconnection just now, moving from MN -> M (approx. 5 PM, 10/31). I got the generic message "Timed out", however, so it may have been my internet connection rather than something server-side.