Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uber-uber two-curse variant of Impresence not in PoB #4787

Open
2 tasks done
zao opened this issue Aug 13, 2022 · 0 comments · May be fixed by #4834
Open
2 tasks done

Uber-uber two-curse variant of Impresence not in PoB #4787

zao opened this issue Aug 13, 2022 · 0 comments · May be fixed by #4834
Labels
bug Something isn't working

Comments

@zao
Copy link
Contributor

zao commented Aug 13, 2022

Check version

  • I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

  • I've checked for duplicate issues by using the search function of the issue tracker

What is the expected behaviour/value?

In 3.18 with the new pinnacle uber uber Elder a cooler version of the Impresence amulet was added that has two curse lines rather than one.
I'd expect to be able to create one of these in the Items tab.

What is the actual behaviour/value?

In the Items tab, when adding an Impresence and selecting a kind like Physical, there is no option to select the cooler version of the item, it only shows a single curse line as it's creating the regular non-Pinnacle version of the item.

How to reproduce the issue

Switch to Items tab.
Create an Impresence from the list of uniques.
Note the lack of crafting options.

Character build code

https://pobb.in/wa1FBFCJ3Nup

Screenshots

Current crafting UI:
image
Example uber-uber version:
image

@zao zao added the bug Something isn't working label Aug 13, 2022
@Sinured Sinured linked a pull request Aug 15, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant