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
It's mostly just for aesthetics and easier sorting of icons in the selection menu
Suggestion
When downloading a modpack, take the pack name and use that as the name of the icon if it's from a platform which doesn't keep icon name metadata
Benefit
Again mostly just aesthetic and sorting benefits, not having a bunch of icons named "curseforge_[string_of_numbers]" everywhere
This suggestion is unique
I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.
You may use the editor below to elaborate further.
When downloading a modpack via the various website and launcher sections in the import menu, Prism Launcher imports the icon for the pack automatically. In many cases this works fine, specifically with FTB, FTB Legacy, and ATLauncher packs. But when installing packs from Curseforge or Technic, the icons will have unreadable names consisting of either:
curseforge_XXXXXXXXXXXXXXXXXX or technic_XXXXXXX (where any "X" is a number)
Modrinth has a lesser version of this where every icon is labelled as modrinth_name (where "name" is a lowercase representation of the pack, either an acronym or the name itself)
Given that Prism Launcher already generates a valid name for the pack at around the same time it grabs the icon (when the pack is first selected in the menu), I feel it wouldn't be too hard to save the icon with the name of the pack instead in cases where it would look better than the messy ID's used by Curseforge, Technic, and Modrinth.
I know this is an extremely minor complaint, but I feel like it wouldn't be too hard to do and would greatly improve the appearance of the Icon menu and folder after you've downloaded several packs from these places.
No change:
Where it would get the name:
After the change (With characters that can't be used by the filesystem removed/replaced):
(Note: File Explorer examples have had .png added at the end so the icon is visible in File Explorer)
The text was updated successfully, but these errors were encountered:
Role
It's mostly just for aesthetics and easier sorting of icons in the selection menu
Suggestion
When downloading a modpack, take the pack name and use that as the name of the icon if it's from a platform which doesn't keep icon name metadata
Benefit
Again mostly just aesthetic and sorting benefits, not having a bunch of icons named "curseforge_[string_of_numbers]" everywhere
This suggestion is unique
You may use the editor below to elaborate further.
When downloading a modpack via the various website and launcher sections in the import menu, Prism Launcher imports the icon for the pack automatically. In many cases this works fine, specifically with FTB, FTB Legacy, and ATLauncher packs. But when installing packs from Curseforge or Technic, the icons will have unreadable names consisting of either:
curseforge_XXXXXXXXXXXXXXXXXX or technic_XXXXXXX (where any "X" is a number)
Modrinth has a lesser version of this where every icon is labelled as modrinth_name (where "name" is a lowercase representation of the pack, either an acronym or the name itself)
Given that Prism Launcher already generates a valid name for the pack at around the same time it grabs the icon (when the pack is first selected in the menu), I feel it wouldn't be too hard to save the icon with the name of the pack instead in cases where it would look better than the messy ID's used by Curseforge, Technic, and Modrinth.
I know this is an extremely minor complaint, but I feel like it wouldn't be too hard to do and would greatly improve the appearance of the Icon menu and folder after you've downloaded several packs from these places.
No change:
Where it would get the name:
After the change (With characters that can't be used by the filesystem removed/replaced):
(Note: File Explorer examples have had .png added at the end so the icon is visible in File Explorer)
The text was updated successfully, but these errors were encountered: