Fixing the quest party repeat bug
Fixing the quest party repeat bug
All we need to do is add a switch to check for all party members to the acr_quest_progress script, right?
-
ç i p h é r
- Retired
- Posts: 2904
- Joined: Fri Oct 21, 2005 4:12 pm
- Location: US Central (GMT - 6)
There's a parameter in acr_quest_update (3rd parameter called bAllPartyMembers). It defaults to TRUE so any time a PC accepts a quest, all party members are assigned that quest. For now, please set this to FALSE in your conversations while we figure out the best way to handle quest assignments to party members. At the moment, there are no restrictions whatsoever.
The quickest/easiest/dirtiest solution to party assignment is to have a radius limit. Any party member beyond a certain distance from the quest giver is ignored (out of earshot).
A more elegant solution would be to allow PC's to "invite" other PCs into their quests (I think we've talked about this before). If the player accepts, they can be assigned that quest. This keeps things more IC and could add a roleplay dimension to static quests.
I think we can start with the quick fix and improve it as we get time. I can get the quick fix for this committed by tomorrow (well, today ... where does the time go?).
If there are other suggestions, feel free to post them.
The quickest/easiest/dirtiest solution to party assignment is to have a radius limit. Any party member beyond a certain distance from the quest giver is ignored (out of earshot).
A more elegant solution would be to allow PC's to "invite" other PCs into their quests (I think we've talked about this before). If the player accepts, they can be assigned that quest. This keeps things more IC and could add a roleplay dimension to static quests.
I think we can start with the quick fix and improve it as we get time. I can get the quick fix for this committed by tomorrow (well, today ... where does the time go?).
If there are other suggestions, feel free to post them.