[DiscordArchive] This Quest is the only case? Or are other pools of your daily quests have also this doubled/race cas
[DiscordArchive] This Quest is the only case? Or are other pools of your daily quests have also this doubled/race cas
Archived author: Naddley • Posted: 2023-11-24T16:50:25.342000+00:00
Original source
This Quest is the only case? Or are other pools of your daily quests have also this doubled/race case?
Archived author: Kelpie • Posted: 2023-11-24T16:50:49.469000+00:00
Original source
Only that case
Archived author: Kelpie • Posted: 2023-11-24T16:51:53.608000+00:00
Original source
So basically, a long time ago when someone originally tried these fixes, shauren had instructed them to use a pool within a pool. But I've tested that, and it doesn't really work acceptably.
Archived author: Kelpie • Posted: 2023-11-24T16:52:28.884000+00:00
Original source
the solution I've found that seems to work is if you assign the same poolIndex value to both quests
Archived author: Kelpie • Posted: 2023-11-24T16:53:59.998000+00:00
Original source
because what happens then, is when a specific pool index is selected, both quests become 'live' (even though the max number value is 1)...because the max number value only determines how many indices are chosen, not how many quests are chosen
Archived author: Kelpie • Posted: 2023-11-24T16:55:38.481000+00:00
Original source
so, when they're both live, normal criteria rules which determine which version of a quest a character gets based on race or class work normally...so from there it's just a question of making sure the quest itself has the proper assignments to make it only visibile to specific races
Archived author: Kelpie • Posted: 2023-11-24T16:57:25.030000+00:00
Original source
but since that is a solution that has never been used in the db before, I'm reluctant to post a fix with it unless someone who's more familiar with how the core interacts with the db says it's okay...because I wouldn't want to introduce a strange undocumented edge case that could later result in crashing
Archived author: Kelpie • Posted: 2023-11-24T17:05:39.461000+00:00
Original source
I guess one of the things that makes this complicated to test is that not only would you have to manipulate the time to make sure that that index was chosen and then test it with every race after seed manipulation, but also, even if the solution works, it might not appear to work, because there are many cases even with normal quests where race/non-race flags don't seem to work properly (northshire is a good example, where the non-racial versions of the quests don't work properly, because essentially they fall into the same category we have here...because I believe that the way we've got criteria coded in the core currently, it doesn't allow for negative racemasks...(i.e. every race BUT a specific race)...
Archived author: Kelpie • Posted: 2023-11-24T17:09:16.610000+00:00
Original source
it's also possible that they could've been implemented and just don't work properly in any of the cases I've checked...because pretty much every time there's been multiple quests that are supposed to be assigned by race or gender, they seem to not assign properly in one way or another.
Archived author: Kelpie • Posted: 2023-11-24T17:12:24.991000+00:00
Original source
(mind you class is fine...quests locked to specific classes have not given me trouble...just race and gender)