Welcome to the AFK Mods bug tracker. In order to report an issue, you need to have a VALIDATED account to post one. Once you have followed the link the registration email sent you, please select a project from the drop down menu below. Select “Open New Issue” and fill out the form with as many details as possible.

Please also consider sending your bug report to Bethesda if you are reporting on an issue with Skyrim Special Edition, Fallout 4, or Starfield. Doing so will help everyone on all platforms.

Issue Data
Status: New
Issue Type: Bug Report
Project: Unofficial Skyrim Special Edition Patch
Component: Skyrim SE: Vanilla
Category: Items
Assigned To: Nobody
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By FenrirWolfiepup on Nov 29, 2024 7:04 pm

Issue #34611: TGRewardPoisonAllBest reuses shop sublists that do not pick the best Poisons available

 
TGRewardPoisonAllBest is the leveled list that Thieves Guild Fences use when they're supposed to sell a Poison.

Aside from the empty list (Drain Skill Poisons, Best), they can end up with an "LItemPoisonDamageHMSBest" (a Damage Poison that's supposed to be the highest level), or an "LItemPoisonMagicEffectsBest" (some other Poison that's supposed to be the highest level).

The problem is that both of these lists call on sublists that have the "Calculate from all levels <= PC's level" tag enabled, so they're not actually guaranteed to return the best Poison in their category for the level required.

It's easier to list the types of Poisons this leveled list returns that are guaranteed to be the best, but the following leveled lists are called instead of any "All Levels"-less ( or "Best" ) list:

All of the possible LItemPoisonDamageHMSBest results:
- LItemPoisonDamageHealth
- LItemPoisonDamageStamina
- LItemPoisonDamageMagicka

Most of the possible LItemPoisonMagicEffectsBest results:
- Every sublist that LItemPoisonWeaknessAllBest calls to:
--- LItemPoisonWeaknessFire
--- LItemPoisonWeaknessFrost
--- LItemPoisonWeaknessMagic
--- LItemPoisonWeaknessShock
- LItemPoisonParalyze

This would be resolved by reassigning lists; and, if the respective lists don't exist, by creating them.