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
Join a SMP using the LAN World option, not using a previously saved server name or direct connect.
Bookmark some junk.
Log out and join the same way again.
Expected Behavior
Retain bookmarks for the same server.
Actual Behavior
Doesn't reload previously saved bookmarks.
Mod Pack URL (Optional)
All 1.21 packs I've played so far (ATM10, FTB Evo, etc.)
Mod Pack Version (Optional)
No response
Extra Notes (Optional)
It appears that a new config/jei/world/server folder is created using the format [server published name]_[some chars]. Each time you connect, a new folder is created to represent the server. Previously saved bookmarks are never reused.
In contrast, joining via a dedicated connection or previously saved server in the MP selection screen, reuses the save folder correctly. Assuming this is an issue with how the folder name is generated since.
Easy workaround is to save the MP server you want to join.
latest.log
No response
The text was updated successfully, but these errors were encountered:
Steps to Reproduce the Bug
Expected Behavior
Retain bookmarks for the same server.
Actual Behavior
Doesn't reload previously saved bookmarks.
Mod Pack URL (Optional)
All 1.21 packs I've played so far (ATM10, FTB Evo, etc.)
Mod Pack Version (Optional)
No response
Extra Notes (Optional)
It appears that a new config/jei/world/server folder is created using the format [server published name]_[some chars]. Each time you connect, a new folder is created to represent the server. Previously saved bookmarks are never reused.
In contrast, joining via a dedicated connection or previously saved server in the MP selection screen, reuses the save folder correctly. Assuming this is an issue with how the folder name is generated since.
Easy workaround is to save the MP server you want to join.
latest.log
No response
The text was updated successfully, but these errors were encountered: