[DiscordArchive] that's good to know...I'll keep that in my toolbox...anyways...any comments about this?
[DiscordArchive] that's good to know...I'll keep that in my toolbox...anyways...any comments about this?
Archived author: Kelpie • Posted: 2024-03-07T11:18:48.202000+00:00
Original source
and that criteria for quest's status therefore should be based on its bitflag
Archived author: Kelpie • Posted: 2024-03-07T11:18:52.081000+00:00
Original source
and not questid
Archived author: Kelpie • Posted: 2024-03-07T11:18:57.015000+00:00
Original source
if not both
Archived author: Kelpie • Posted: 2024-03-07T11:19:27.224000+00:00
Original source
I'm simply saying this as someone who's been questchaining and have noticed that this seems to be the logic behind questv2
Archived author: Kelpie • Posted: 2024-03-07T11:19:42.961000+00:00
Original source
that they were trying to in some small manner futureproof their quest system
Archived author: Kelpie • Posted: 2024-03-07T11:20:01.237000+00:00
Original source
to allow a way to prevent explotation by repeating non-repeatable quests by changing the criteria
Archived author: Kelpie • Posted: 2024-03-07T11:20:50.961000+00:00
Original source
anyways, I'm just saying what I know, as I said in the beginning, sorry if I sound dumb by saying it
Archived author: Kelpie • Posted: 2024-03-07T11:21:16.909000+00:00
Original source
but I was wondering if it's worth considering that as part of the quest logic implementation
Archived author: Tea • Posted: 2024-03-07T11:22:45.388000+00:00
Original source
you know what if you use a positive value in ExclusiveGroup it already works that way? if quest X requires quests A, B and C to be completed and A, B and C all have the same ExclusiveGroup (> 0) then quest X is available to players who have completed A or B or C
Archived author: Kelpie • Posted: 2024-03-07T11:22:57.999000+00:00
Original source
Yes, but that can only be done once