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

Enable Profile Icon #34

Closed
wants to merge 4 commits into from
Closed

Enable Profile Icon #34

wants to merge 4 commits into from

Conversation

Ecdcaeb
Copy link

@Ecdcaeb Ecdcaeb commented Oct 20, 2024

enable profile icon of base64

@neoforged-pr-publishing
Copy link

  • Publish PR to GitHub Packages

@shartte
Copy link
Contributor

shartte commented Oct 20, 2024

What is this trying to solve or fix?

@Ecdcaeb
Copy link
Author

Ecdcaeb commented Oct 21, 2024

What is this trying to solve or fix?

Although it is not currently required by NeoForge, this PR is still submitted for the following reasons:

  1. Support the legacy operations https://github.com/neoforged/NeoForge/blob/1.16.x/build.gradle#L669
  2. Since we are currently using entry key="installer.window.title">%s Installer</entry> instead of entry key="installer.window.title">NeoForge Installer</entry>, this means that LegacyInstaller is not only designed for NeoForge. It is also necessary to try to obtain icons from the profile instead of just hard-code them.

@shartte
Copy link
Contributor

shartte commented Oct 21, 2024

What is this trying to solve or fix?

Although it is not currently required by NeoForge, this PR is still submitted for the following reasons:

1. Support the legacy operations https://github.com/neoforged/NeoForge/blob/1.16.x/build.gradle#L669

2. Since we are currently using `entry key="installer.window.title">%s Installer</entry>` instead of `entry key="installer.window.title">NeoForge Installer</entry>`, this means that LegacyInstaller is not only designed for NeoForge. It is also necessary to try to obtain icons from the profile instead of just hard-code them.
  1. We don't do NeoForge before 1.20.1, we don't have a need for supporting installer profiles of earlier versions in the latest installer (since the old version would not use it anyway)
  2. You coud just overwrite the logo in the final jar file with another logo if you wanted to, would that solve what you want to do?

@Ecdcaeb
Copy link
Author

Ecdcaeb commented Oct 21, 2024

What is this trying to solve or fix?

Although it is not currently required by NeoForge, this PR is still submitted for the following reasons:

1. Support the legacy operations https://github.com/neoforged/NeoForge/blob/1.16.x/build.gradle#L669

2. Since we are currently using `entry key="installer.window.title">%s Installer</entry>` instead of `entry key="installer.window.title">NeoForge Installer</entry>`, this means that LegacyInstaller is not only designed for NeoForge. It is also necessary to try to obtain icons from the profile instead of just hard-code them.
  1. We don't do NeoForge before 1.20.1, we don't have a need for supporting installer profiles of earlier versions in the latest installer (since the old version would not use it anyway)
  2. You coud just overwrite the logo in the final jar file with another logo if you wanted to, would that solve what you want to do?

Thank you for your help. There is nothing other than the file name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants