[DiscordArchive] but isn't the entire reason for uniquebitflag being contained in questv2.dbc, because blizz uses it
[DiscordArchive] but isn't the entire reason for uniquebitflag being contained in questv2.dbc, because blizz uses it
Archived author: Kelpie • Posted: 2024-03-07T09:54:07.477000+00:00
Original source
but isn't the entire reason for uniquebitflag being contained in questv2.dbc, because blizz uses it (among other things) sorta like how we use exclusivegroup?
Archived author: Kelpie • Posted: 2024-03-07T09:54:39.904000+00:00
Original source
for instance, like I notice that in places where the same quest has multiple quest ids with different race/classmasks, they all have the same uniquebitflag generally
Archived author: Kelpie • Posted: 2024-03-07T09:54:55.160000+00:00
Original source
so that say you change classes
Archived author: Telegrill • Posted: 2024-03-07T09:55:06.269000+00:00
Original source
as far as I know, they use that field to save current done quests
Archived author: Kelpie • Posted: 2024-03-07T09:55:07.405000+00:00
Original source
you don't suddenly get to redo quests you already completed as another class
Archived author: Telegrill • Posted: 2024-03-07T09:55:52.722000+00:00
Original source
or more like current quests with X status, unsure atm
Archived author: Kelpie • Posted: 2024-03-07T09:56:03.012000+00:00
Original source
and part of that is what we use exclusivegroup for...to prevent you from taking and completing the same quest multiple times under different criteria
Archived author: Kelpie • Posted: 2024-03-07T09:56:18.172000+00:00
Original source
basically it creates an XOR relation
Archived author: Kelpie • Posted: 2024-03-07T09:56:24.054000+00:00
Original source
(or an AND relation if negative)
Archived author: Telegrill • Posted: 2024-03-07T09:56:39.219000+00:00
Original source
well exclusive group is not exactly for that matter, if you've done a quest which isn't repeteable, there's no need for exclusiveGroup itself