BEFORE opening a new feature request, please make sure that you:
- Understand the implications of your feature with the help of the Forum, OR
- Peer-reviewed it with other users on Discord,
- Consider commenting on the Feature Request Forum if something is important for you
AFTER opening the feature request, the issue will be closed by a maintainer (@4ian or someone else) and a card will be added in the public roadmap if it's relevant and does not exist yet :)
Description
Is your feature request related to a problem? Please describe.
GDevelop Electron exports embed third-party libraries (PixiJS, Howler, TweenManager, etc.). While some bundled files retain license headers, those notices are not easily visible or accessible to end users because the code is embedded inside the application package. For commercial distribution, providing an automatic way to access third-party licenses would make license compliance easier.
Solution suggested
Describe the solution
Please consider adding an automatic THIRD_PARTY_LICENSES.txt file or an in-app attribution page generated during export, containing dependency names, copyright notices, and license texts.
Add any other context or screenshots about the feature request here.
No.
Explain if you can help to implement the solution.
No.
Alternatives considered
A clear and concise description of any alternative solutions or features you've considered.
Manually gathering and packing the license files of every dependency into the output folder after each export.
BEFORE opening a new feature request, please make sure that you:
AFTER opening the feature request, the issue will be closed by a maintainer (@4ian or someone else) and a card will be added in the public roadmap if it's relevant and does not exist yet :)
Description
Is your feature request related to a problem? Please describe.
GDevelop Electron exports embed third-party libraries (PixiJS, Howler, TweenManager, etc.). While some bundled files retain license headers, those notices are not easily visible or accessible to end users because the code is embedded inside the application package. For commercial distribution, providing an automatic way to access third-party licenses would make license compliance easier.
Solution suggested
Describe the solution
Please consider adding an automatic
THIRD_PARTY_LICENSES.txtfile or an in-app attribution page generated during export, containing dependency names, copyright notices, and license texts.Add any other context or screenshots about the feature request here.
No.
Explain if you can help to implement the solution.
No.
Alternatives considered
A clear and concise description of any alternative solutions or features you've considered.
Manually gathering and packing the license files of every dependency into the output folder after each export.