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

Adding {1} to a list item in every tab results in an error and no linked loadout #7790

Closed
2 tasks done
priorGuesstimator opened this issue Jul 22, 2024 · 1 comment · Fixed by #7793
Closed
2 tasks done
Labels
bug Something isn't working

Comments

@priorGuesstimator
Copy link

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 open and closed issues by using the search function of the issue tracker

What platform are you running Path of Building on?

Windows

How is Path of Building expected to behave?

By appending {1} to the end of list item names in all 4 tabs a loadout should be created

How does Path of Building behave?

изображение
I added {1} to a tree, skill setup, gear setup and config setup, on saving the last one it shows an error and does not link the loadout

How to reproduce the issue

Take a pob with multiple saved trees, skill setups, etc
Try to link a loadout by appending {1} to the end of names

Character build code

https://pobb.in/_uzI5QJEoaKh

Screenshots

No response

@priorGuesstimator priorGuesstimator added the bug Something isn't working label Jul 22, 2024
@Wires77
Copy link
Member

Wires77 commented Jul 22, 2024

Putting a space between your tree name and {1} should fix it for now

deathbeam added a commit to deathbeam/PathOfBuilding-1 that referenced this issue Jul 22, 2024
Closes PathOfBuildingCommunity#7790

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
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.

2 participants