You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently only tested in the worgen area. Quest Royal orders when clicked auto accepts the quest and gives you no additional quest text and no way to close it other than using esc. I abandoned the quest and then tried to retake it again but when abandoning it my character phased over as if I did complete it. Leaving me stuck in a space I couldn't do anything since I couldn't retake the quest.
Expected Blizzlike Behaviour
Not have missing info and for phasing to only apply when quest has completed.
[00:36:44] Firelands rev. 5f28ff0 2023-09-18 23:44:16 -0500 (master branch) (Win64, Release, Static)
[00:36:44] Using SSL version: OpenSSL 1.1.1v 1 Aug 2023 (library: OpenSSL 1.1.1v 1 Aug 2023)
[00:36:44] Using Boost version: 1.83.0
[00:36:44] Using MySQL version: 80034
[00:36:44] Using CMake version: 3.27.5
[00:36:44] Compiled on: Windows 10.0.22621
[00:36:44] Automatic database updates are enabled for the following databases: Auth, Characters, World
[00:36:44] Worldserver listening connections on port 18085
[00:36:44] Realmlist (Realm Id: 1) configured in port 18085
[00:36:44] VMAPs status: Enabled. LineOfSight: 1, getHeight: 1, indoorCheck: 1
[00:36:44] MMAPs status: Enabled
[00:36:44] maps directory located in ./maps. Total size: 409779433 bytes
[00:36:45] vmaps directory located in ./vmaps. Total size: 881241574 bytes
[00:36:45] mmaps directory located in ./mmaps. Total size: 2942701088 bytes
[00:36:45] Using enUS DBC Locale as default. All available DBC locales: enUS frFR none
[00:36:45] Using World DB: FDB 434.22012
Operating system
Windows 11
Custom changes or Modules
No response
The text was updated successfully, but these errors were encountered:
I checked the quest data within the quest template table and related tables for quests and see all the fields that are required, are filled in. I think either wrong packets are being sent or there is a bug within the quest system.
Honestly I have not played much in the Worgen starting zone, but resetting back to the initial start phase is a bug for sure. I'll review the code core side and see what is going on there.
Current Behaviour
Currently only tested in the worgen area. Quest Royal orders when clicked auto accepts the quest and gives you no additional quest text and no way to close it other than using esc. I abandoned the quest and then tried to retake it again but when abandoning it my character phased over as if I did complete it. Leaving me stuck in a space I couldn't do anything since I couldn't retake the quest.
Expected Blizzlike Behaviour
Not have missing info and for phasing to only apply when quest has completed.
Source
No response
Steps to reproduce the problem
https://youtu.be/ml8KUWntWds
(video showing the glitch)
Extra Notes
No response
FC rev. hash/commit
[00:36:44] Firelands rev. 5f28ff0 2023-09-18 23:44:16 -0500 (master branch) (Win64, Release, Static)
[00:36:44] Using SSL version: OpenSSL 1.1.1v 1 Aug 2023 (library: OpenSSL 1.1.1v 1 Aug 2023)
[00:36:44] Using Boost version: 1.83.0
[00:36:44] Using MySQL version: 80034
[00:36:44] Using CMake version: 3.27.5
[00:36:44] Compiled on: Windows 10.0.22621
[00:36:44] Automatic database updates are enabled for the following databases: Auth, Characters, World
[00:36:44] Worldserver listening connections on port 18085
[00:36:44] Realmlist (Realm Id: 1) configured in port 18085
[00:36:44] VMAPs status: Enabled. LineOfSight: 1, getHeight: 1, indoorCheck: 1
[00:36:44] MMAPs status: Enabled
[00:36:44] maps directory located in ./maps. Total size: 409779433 bytes
[00:36:45] vmaps directory located in ./vmaps. Total size: 881241574 bytes
[00:36:45] mmaps directory located in ./mmaps. Total size: 2942701088 bytes
[00:36:45] Using enUS DBC Locale as default. All available DBC locales: enUS frFR none
[00:36:45] Using World DB: FDB 434.22012
Operating system
Windows 11
Custom changes or Modules
No response
The text was updated successfully, but these errors were encountered: