[DiscordArchive] You should post a screenshot in a language people have a chance to understand, like for example Engl
[DiscordArchive] You should post a screenshot in a language people have a chance to understand, like for example Engl
Original source
it happens when the quest giver you turned in the last quest at gives you the next quest in a chain
rektbyfaith
04-05-2024, 05:22 AM #31Archived author: Kelpie • Posted: 2024-04-05T05:22:10.867000+00:00
Original source
it happens when the quest giver you turned in the last quest at gives you the next quest in a chain
Original source
so, the way the core handles it, it sends a packet to automatically open the quest accept dialogue
rektbyfaith
04-05-2024, 05:22 AM #32Archived author: Kelpie • Posted: 2024-04-05T05:22:30.106000+00:00
Original source
so, the way the core handles it, it sends a packet to automatically open the quest accept dialogue
Original source
however
rektbyfaith
04-05-2024, 05:22 AM #33Archived author: Kelpie • Posted: 2024-04-05T05:22:35.421000+00:00
Original source
however
Original source
when you click on a questgiver with a quest that has the 'autoaccept' specialflag (SpecialFlag 4)
rektbyfaith
04-05-2024, 05:22 AM #34Archived author: Kelpie • Posted: 2024-04-05T05:22:57.821000+00:00
Original source
when you click on a questgiver with a quest that has the 'autoaccept' specialflag (SpecialFlag 4)
Original source
if that quest is available, the dialogue window is ALSO automatically opened and automatically accepted
rektbyfaith
04-05-2024, 05:23 AM #35Archived author: Kelpie • Posted: 2024-04-05T05:23:25.550000+00:00
Original source
if that quest is available, the dialogue window is ALSO automatically opened and automatically accepted
Original source
in all starter subzones, this flag is enabled for all quests
rektbyfaith
04-05-2024, 05:23 AM #36Archived author: Kelpie • Posted: 2024-04-05T05:23:38.700000+00:00
Original source
in all starter subzones, this flag is enabled for all quests
Original source
so what tends to happen is if these two opcodes are received within the same tick by the client, it seems that the window opens twice, but since it can only be accepted once (by the specialflag 4), the window cannot be closed, as that would require accepting a quest that was already accepted
rektbyfaith
04-05-2024, 05:25 AM #37Archived author: Kelpie • Posted: 2024-04-05T05:25:15.607000+00:00
Original source
so what tends to happen is if these two opcodes are received within the same tick by the client, it seems that the window opens twice, but since it can only be accepted once (by the specialflag 4), the window cannot be closed, as that would require accepting a quest that was already accepted
Original source
(hence why the accept button doesn't work)
rektbyfaith
04-05-2024, 05:25 AM #38Archived author: Kelpie • Posted: 2024-04-05T05:25:22.214000+00:00
Original source
(hence why the accept button doesn't work)
Original source
Similar processes do not seem to have this issue in 335
rektbyfaith
04-05-2024, 05:26 AM #39Archived author: wolone • Posted: 2024-04-05T05:26:32.744000+00:00
Original source
Similar processes do not seem to have this issue in 335
Original source
so basically you will find this issue you describe 'tends' to happen when these two cases are true...there are however other circumstances I've found that can cause it (for instance, if a quest has conditions in the 'conditions' table as well as rewardnextquest or nextquestid in quest_template_addon)
rektbyfaith
04-05-2024, 05:27 AM #40Archived author: Kelpie • Posted: 2024-04-05T05:27:09.653000+00:00
Original source
so basically you will find this issue you describe 'tends' to happen when these two cases are true...there are however other circumstances I've found that can cause it (for instance, if a quest has conditions in the 'conditions' table as well as rewardnextquest or nextquestid in quest_template_addon)
1 Guest(s)
1 Guest(s)