You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The list of sockets and enchants are empty whenever i open at item to change the enchants or gems. If i click directly on a enchantment, where it opens the item directly in the enchantment tab-view, the list works fine. This occurs for me for both versions, localhost-version and the github.io-hosted version. It also seems to be a special kind of bug, since no one in my guild has the this issue. I checked the web-console there is also no js-error or anything showing.
To Reproduce
Steps to reproduce the behavior:
Go to any character
Click on any item
Go to enchant or gems
No entries are there
Choose different entry in the Phase-Dropdrown / or in gems change the selection of "match socket"
Enchants are showing now / gems are showing as well (it doesnt matter in which sub-window i change the phase it always loads both of it)
Expected behavior
It should show the list of enchants and gems of the selected phase on the opening of the tab.
Sim Links and Screenshots
Desktop:
Windows
Chrome (vers. 118.0.5993.89)
Sim-Version 1.5.3
The text was updated successfully, but these errors were encountered:
Describe the bug
The list of sockets and enchants are empty whenever i open at item to change the enchants or gems. If i click directly on a enchantment, where it opens the item directly in the enchantment tab-view, the list works fine. This occurs for me for both versions, localhost-version and the github.io-hosted version. It also seems to be a special kind of bug, since no one in my guild has the this issue. I checked the web-console there is also no js-error or anything showing.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should show the list of enchants and gems of the selected phase on the opening of the tab.
Sim Links and Screenshots
Desktop:
The text was updated successfully, but these errors were encountered: