View Issue Details

IDProjectCategoryView StatusLast Update
0015954Return of ReckoningGeneralpublic2024-06-21 01:14
ReporterReturnOfReckoning Assigned ToEmissary  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Summary0015954: Needs coding, but critical bug solved: Why many PvE quests do not grant credit
DescriptionReporter: juliettestray

<!--
Issues should be unique. Check if someone else reported
the issue first, and please don't report duplicates.
Only ONE issue in a report. Don't forget screens or a video.
-->

**Expected behavior and actual behavior:**

Many PvE quests do not grant credit, or grant credit only sporadically (the Altdorf sewers being a notorious recent example). I previously assumed this was just some quirk of the emulation or some other kink that needed ironing out -- but in fact it's related to bolstering and quest completion rules for level disparity when quest steps are taken.

Ex: Many players who engage in the Altdorf Sewers quests complete only some quests in there on a full run, but others wind up completing them all.

This is because the quests that do complete 100% of the time are elite party quests, which have special rules for always granting completion. The other quests are not flagged this way.

What happens is someone who is bolstered is in the party -- this makes sense, it's why you can't powerlevel friends -- however, this means that if someone enters the dungeon when bolstered, like if they just finished a scenario or came in from elsewhere and it hasn't yet dropped off, _nobody in the party gets completion because the game thinks the player is too high of a level._

Some quests out in the world also require passing through RvR areas that apply bolstered status, or are located in areas of the world that apply it, and if the npc is too low level, you won't complete anything. Consequently, a great many PvE quests appear "broken," a problem that manifests more as you level and move to zones with more and more PVP that winds up bolstering you.

**Steps to reproduce the problem:**

Methodology:
In High Pass, there is a quest, "Sigmar's Comet," that requires killing an NPC for a quest completion item. In attempting to do this quest several times, I noticed that the quest npc is level 26, and since he is in the RvR section, we are bolstered to level 48.

This NPC just so happens to be located on the mountain border of the RvR section and regular section, JUST northwest of Ogrund's Tavern, but cannot be reached from the latter. You can, however, station two people: one near the NPC (Cultist Barnard) and one on the mountain ledge above. The player bolstered in RvR then tags the mob and kites it backward closer to the mountain road so that the non-bolstered player can pull it off and kill it.

Results:
Both players are bolstered: No credit
Tagging player is bolstered but killing player is not and they are partied: No credit
Tagging player is bolstered but killing player is not and they are NOT partied: Killer gets quest completion credit

Tested twice; verified both times.

**Testing Screenshots/Videos/Evidences (always needed):**
<!-- Drag and drop an image file here to include it directly in the bug report,
     no need to upload it to another site -->
![bugtest](https://user-images.githubusercontent.com/30501156/76467657-554cb480-63a7-11ea-98ac-91a56a4060b0.png)



<!--
Note that game critical and game breaking bugs may award a manticore/griffon (realm specific) at the leads discretion however, asking for one instantly disqualifies you from this reward.
-->
TagsQuests, Sourcecode

Activities

ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:06

reporter   ~0029223

Commenter: juliettestray

To be crystal clear, this doesn't involve the bolster buff -- it involves the artificial boost to Battle Rank.

Issue History

Date Modified Username Field Change
2023-08-13 04:06 ReturnOfReckoning New Issue
2023-08-13 04:06 ReturnOfReckoning Tag Attached: Quests
2023-08-13 04:06 ReturnOfReckoning Tag Attached: Sourcecode
2023-08-13 04:06 ReturnOfReckoning Note Added: 0029223
2024-06-21 01:14 Emissary Assigned To => Emissary
2024-06-21 01:14 Emissary Status new => closed
2024-06-21 01:14 Emissary Resolution open => no change required