Information

Minecraft version: 1.21.1
Modloader: NeoForge 21.1.172
Environment: Multiplayer

Mod name: Daily Quests
Mod version: 1.21.1-2.2

Description

My mod has remained on the opening day information (i.e. intro/letting me know my first X quests will be rolled the next morning). This has persisted despite sleeping multiple times, uninstalling/reinstalling the mod, and having the server owner use commands to manually reassign me new quests. The last did make one change (the box initially stated I'd receive my "first 0 quests" the next in-game morning, and doing this command changed it to my "first 3 quests"), but did not solve the issue. There are 2 other players in the server, neither of whom are experiencing this issue with their daily quests.

(Hopefully I've filled this out correctly, but please redirect me if I need to go elsewhere!)

Hi @bagofmilkyways. My small clan has been having the same issue on Fabric and here is how we've been getting past this so far.

Whether the "Introduction" says I have either "0" or "3" quests, if I use the command "/dq quests", it seems to respond "To see your quest stats, use /dq info" without listing any specific quests.

Next an OP should use the command:

/dq debug {PlayerName} generate 3

Replace "{PlayerName}" with the affected player name without the brackets.

At this point, if the Introduction previously said "0", it should now say "3" or however many designated in the command used.

Next, the player should be able to use "/dq quests" and see the appropriate number of quests listed in chat. Have the player pick the easiest quest and work to complete it.

After completing a quest, the player has to go to bed to sleep through the night. If the player doesn't sleep through the night and just stays up, or in multiplayer if not everyone has to sleep, the Introduction window may not change. But if the player does sleep through the night, my experience so far, shows that the Introduction window changes to list quests properly.

If you get this info and try it, reply back to let everyone know if this works or not. If not, I'll see if I missed anything. Best of luck.

Still happens despite using debug commands, seems to be an issue with the actual UI. My friend on the same server has it functioning properly, I don't. Maybe it's because I disabled the UI for a moment?