Incorrect caching behavior in `ForgeFinder: Export` when the caching character does not have Dragonflight professions
tharakadesilva opened this issue ยท 2 comments
When transitioning from a character WITHOUT dragonflight profession to another character WITH dragonflight profession, the cached data from the prior character is incorrectly utilized, leading to an erroneous Created 0 RecipeData
.
This is an extremely niche case and would probably not happen to a lot of folks, but it happened to me, so here I am..
Prerequisites:
- Possess two characters with the same profession (I used blacksmithing).
- One character should specialize in dragonflight blacksmithing, and the other should not (for reproducibility, the second character in my test had only MoP blacksmithing for mage tower crafts).
Steps to Reproduce
- Log into the character that DOESN'T possess dragonflight blacksmithing.
- Click ForgeFinder export.
- Transition to the character that DOES specialize in dragonflight blacksmithing.
- Click ForgeFinder export again.
Expected Behavior:
- The outcome of step 2 should return
Created 0 RecipeData
. - Step 4 should yield the corresponding recipe data for the dragonflight blacksmithing character.
Observed Behavior:
- In both steps 2 and 4, the system returns Created 0 RecipeData.
- Debugging the second character reveals that ForgeFinder still uses the cached data from the character without dragonflight blacksmithing.
Temporary Fix / Workaround:
- On the character specializing in dragonflight blacksmithing, clear the cache.
- Reload.
- Trigger ForgeFinder export again.
Potential Fix
Don't cache data if the character hasn't learned the dragonflight version of the profession.
I recently changed what cache is used for that, could you test if this is still occuring?
Sorry for not verifying earlier @derfloh205. I missed the previous notification and I don't play as much anymore.
Thanks for the fix though!! ๐