Repository navigation
Description
Planned license change
Adopt the Phalcode Source-Available License 1.0 for designated future GameVault software releases, replacing the current CC BY-NC-SA 4.0 terms for those releases where Phalcode has sufficient rights to do so.
The complete planned license text is included below. Adoption is pending verification of contributor and third-party rights and selection of the affected releases. Posting the proposal here does not change the license of an existing release.
Purpose and change from the original proposal
The original proposal considered a software license with Commons Clause. The current plan is a dedicated source-available software license that defines noncommercial use and requires distributed forks to provide corresponding source under the same license version.
The personal paywall exception is deliberately narrow: a user may modify their own installation to use paid features solely for themselves, but may not supply that modification to others or let other people use the functionality enabled by it.
This is a restriction compared with the earlier statement in this issue that users may change GameVault, including bypassing paywalls, without stating this additional limit on onward supply and shared use. The new rule is planned for material governed by the new license. It does not withdraw permissions already granted under earlier licenses.
What the planned license allows
| Activity | Permission and conditions |
|---|---|
| Use and study GameVault | Allowed for noncommercial purposes. |
| Make ordinary modifications or develop a fork | Allowed for noncommercial purposes. Private modifications do not have to be published. |
| Share an unmodified copy or an ordinary modified fork | Allowed noncommercially. Supply the full license and required attribution and modification notices, as well as corresponding source for the exact distributed version. A distributed copy must not contain a restricted paywall-bypassing modification. |
| License a distributed fork's covered modifications | Those modifications must be offered to recipients under this exact license version. Phalcode-covered material cannot be moved to different terms by a downstream distributor. |
| Supply executable builds | Allowed with the corresponding source supplied alongside them or through the compliant free download option described in Section 4. A source download location must remain available for at least three years after the last distribution of that copy. |
| Bypass paid-feature checks on one's own installation | Expressly allowed only for a natural person's own personal, noncommercial use. This creates no entitlement to Phalcode-hosted services or third-party resources. |
| Run that personal installation on a VPS | Allowed under the infrastructure-provider conditions in Section 5.2. Personally enabled functions must remain exclusively for that individual. |
| Use a normal installation with friends or household members | Allowed noncommercially, subject to applicable feature entitlements. They may use unaffected functions of a personally modified installation if the personally enabled functions remain inaccessible to them. |
| Remove a premium feature entirely | Allowed if doing so does not make paid functionality available without the required entitlement. Isolated automated test fixtures have a separate, limited exception. |
| Discuss technical behavior or report a defect | General technical discussion and lawful security research remain permitted. Relevant material may be sent privately to Phalcode for confidential review, including a proposed fix or contribution. |
| Receive genuine voluntary donations | Permitted for an otherwise noncommercial activity when the donation purchases no access, feature, copy, hosting, support, or other benefit. |
What the planned license prohibits without separate permission
- Commercial exploitation, including selling Software copies, charging for its functions, or providing a commercial hosted service. An activity can be commercial even if it makes no profit. A GameVault+ subscription does not automatically grant commercial distribution or hosting rights.
- Supplying a paywall-bypassing modification or a copy containing one to another person, even for free or privately to a single friend. The restriction covers source, builds, containers, patches, and relevant configuration files.
- Providing other people with access to personally enabled paid functions through a shared server, account, API, or any other service. Household members are not included in the personal exception.
- Supplying targeted executable tools intended to let others bypass GameVault's paid-feature checks, subject to the contractual and mandatory-law limits in the full text. Embedding a targeted patch in a discussion post does not create a distribution exception.
- Redistributing covered Software without the required source access and notices, applying different terms to covered material, or imposing additional contractual restrictions on recipients' licensed rights.
- Presenting an unofficial fork as an official or endorsed Phalcode product. The license supplies no general trademark permission.
The personal exception grants no permission to access another person's account or an external service without authorization, use leaked secrets, or circumvent protection of third-party works.
Legal boundaries and existing rights
- Existing CC BY-NC-SA releases and material retain the permissions already granted under that license. The new restrictions do not apply retroactively. Older forks may continue under their existing terms; the change does not establish exclusive control over material previously offered under CC. CC BY-NC-SA 4.0
- Third-party components retain their own licenses and required notices. The new license cannot override their permissions or resolve an incompatible dependency license.
- Mandatory statutory rights remain unaffected, including applicable software exceptions. Section 69g of the German Copyright Act
- The CLA is separate from this public license. Its revised wording does not automatically establish retroactive permission for older contributions.
- The proposed license is source-available and contains noncommercial restrictions. It is not presented as an OSI-approved open-source license.
Adoption checklist
- Define how the new license will be presented to users before acceptance.
- Verify the rights needed to relicense existing contributions and offer commercial licenses.
- Review dependencies and preserve their separate licenses and notices.
- Identify the first affected releases and the exact material covered; clearly distinguish older CC material and separately licensed content.
- Update repository license files and package metadata. Align download notices and user documentation.
- Explain the personal-only paywall exception and its difference from the earlier statement in this issue.
- Provide a reliable way to match distributed builds to their corresponding source.
Full planned license text
Read the complete Phalcode Source-Available License 1.0
Phalcode Source-Available License 1.0
1. Parties, scope, and acceptance
This license is offered by Alkan Alper, Schäfer Philip GbR, operating as Phalcode ("Phalcode").
"You" means the person or legal entity exercising rights under this license. A person acting for a legal entity must be authorized to do so.
"Software" means material that Phalcode expressly designates as covered by this version of this license, including GameVault source code and executable code. It includes modifications of that material, subject to the limits of the rights Phalcode is authorized to grant. Separately licensed third-party components are governed by Section 7.
Your games, media, save files, credentials, and other user-supplied content are outside the scope of this license. This license grants no rights in that content.
After receiving clear notice of these terms and an opportunity to review them, exercising rights granted only by this license indicates acceptance through conduct where applicable law recognizes that form of acceptance. You may also accept expressly. If You do not accept, this license grants You no permission. Rights available without this license remain governed by Section 11.
2. Rights granted
Phalcode grants You a non-exclusive, worldwide, royalty-free copyright license for the duration of the applicable copyright, subject to these terms, to:
- Run and study the Software for Noncommercial Purposes.
- Copy the Software and make backup copies for permitted uses.
- Modify the Software and create works derived from it for Noncommercial Purposes.
- Distribute permitted copies and modifications under Section 4.
- Provide noncommercial remote access under Section 6.
These permissions cover source code and executable code. Section 5 specifically governs modifications that bypass Paid Feature Controls and takes precedence over the general modification and distribution permissions.
Phalcode may not withdraw these permissions for compliant use of a copy already licensed under these terms. Termination is governed by Section 10. No right to sublicense Phalcode's material under different terms is granted.
3. Noncommercial purposes and separate commercial permission
"Noncommercial Purpose" means a purpose that is not primarily intended for commercial advantage or monetary compensation. The nature of the activity determines whether it is noncommercial; the operator's legal form does not decide the question by itself. An activity may be commercial even if it makes no profit.
Noncommercial Purposes include private entertainment and personal study. Hobby development also qualifies if it has no intended commercial application.
You need separate permission from Phalcode for activities primarily intended for commercial advantage or monetary compensation. Examples include selling Software copies, charging for access to its functions, operating an advertising-funded Software service, and supplying the Software as a material part of a paid product or service. The same rule applies to commercial use of modified versions.
Receiving a genuinely voluntary donation does not by itself make an otherwise noncommercial activity commercial, provided that the donation purchases no Software access, feature, copy, hosting, support, or other benefit. A payment described as a donation does not qualify for this exception if it is consideration for such a benefit.
Commercial activities require a separate agreement covering the activity concerned. A GameVault+ subscription or other feature entitlement does not by itself grant permission for commercial distribution, hosting, or exploitation of the Software. Its separately agreed terms continue to apply.
4. Distribution, source code, and ShareAlike
You may distribute unmodified or modified copies of the Software for Noncommercial Purposes only if all of the following requirements are met:
- The copy contains no Restricted Modification as defined in Section 5, and its distribution does not otherwise violate that section.
- Each recipient receives this complete license text with the copy. You must retain supplied copyright notices, attribution notices, disclaimers, and relevant third-party license notices. You must identify Phalcode as the developer of the original GameVault material in a reasonable and accessible manner.
- You identify Your modifications and state that the distributed version is unofficial unless Phalcode has expressly authorized an official release. A change record supplied with the Software may satisfy this requirement.
- You license Your copyright in modifications and derivative portions of the Software to each recipient under this exact version of this license. Those recipients must receive the same permissions and restrictions for those portions. You may not substitute a different license for the covered material.
- Every recipient can obtain the Corresponding Source for the exact copy distributed, without charge beyond an ordinary network connection. You must either supply that source with the copy or provide a working download location in the accompanying materials. If You use a download location, You must maintain access for at least three years after Your last distribution of that copy. You may require proof of receipt of the copy but no additional payment or acceptance of additional restrictive terms.
- You impose no additional contractual restrictions on recipients' exercise of the rights this license grants.
"Corresponding Source" means the preferred form for making changes to the covered Software, including Your changes, together with the build and installation scripts and instructions reasonably needed to reproduce and install the distributed version. It includes code and configuration that implement the version's feature-entitlement checks. It does not require disclosure of private keys, passwords, personal data, third-party account credentials, or general-purpose tools available separately to the public. Separately licensed components remain subject to Section 7.
You need not distribute private modifications or disclose source merely because You make or run them. In particular, Section 4 never requires publication of a Restricted Modification that Section 5 requires You to keep private.
Independent programs and user content do not become subject to this license solely because they communicate with the Software through an interface or are distributed alongside it. This exception does not permit relabeling covered modifications or derivative portions as independent material.
Every recipient receives permission from Phalcode directly for Phalcode-controlled material under this license, and from the relevant modifier for that modifier's covered contributions under this same license. You must not represent that You own or can grant rights belonging to others.
5. Paid features and the personal modification exception
5.1 Definitions
"Paid Feature Controls" means code or mechanisms in the Software that determine whether a user has a valid GameVault+ subscription, license key, payment-based entitlement, or other authorization that Phalcode requires for designated paid features in the applicable release as supplied by Phalcode. A later decision to charge for a previously free feature does not retroactively change permissions for an earlier release.
"Restricted Modification" means a change to the Software, its configuration, or its operating environment that removes, disables, bypasses, substitutes for, or falsifies Paid Feature Controls so that paid features can be used without the entitlement Phalcode normally requires. The definition also covers a version redesigned or repackaged to provide those same covered paid features without the required entitlement.
A change is not a Restricted Modification merely because it corrects a defect while preserving the required entitlement checks, changes unrelated functionality, or removes a paid feature entirely without making it available without the required entitlement. Isolated test doubles and fixtures are also excluded if they operate only in automated tests and do not make paid functionality available without the required entitlement in the version supplied for ordinary operation. Independently created software that does not incorporate or derive from protected Software material is outside the copyright grant of this license.
5.2 Personal use expressly permitted
If You are a natural person, You may make or apply a Restricted Modification to a copy of the Software lawfully obtained under this license and run the resulting version solely for Your own personal, noncommercial use.
For that limited purpose, Phalcode expressly authorizes the necessary modification or bypass of its own Paid Feature Controls within that copy, to the extent Phalcode has authority to give that authorization.
The Restricted Modification itself must remain private, and the functionality it enables must remain exclusively for Your use. You may use devices and servers You own, rent, or otherwise lawfully control, including a remotely hosted server, provided that no other person is given access as a user to the functionality enabled by that Restricted Modification. Other persons may use unaffected functions of the same installation under Section 6; that does not permit supplying them with the Restricted Modification or the modified Software copy.
Infrastructure providers may process installation and backup copies solely to deliver hosting or storage to You, under terms granting no independent use or onward supply of the modified Software. Incidental privileged administrative access for that limited purpose does not itself make the provider a user of the personally enabled functionality. This exception permits a paid general-purpose hosting or storage service, but grants no permission to operate a commercial GameVault managed service or to use the personally enabled functionality for anyone else.
This exception does not permit use on behalf of an employer, business, client, or organization. It does not extend to friends, household members, other server users, or any other person. Each individual who wishes to rely on this exception must independently make or apply their own modification to their own lawfully obtained copy and comply with this license; that rule creates no permission to receive or distribute prohibited materials.
5.3 No onward supply of restricted versions
You may not distribute, publish, upload for others, lend, sell, or otherwise supply a Restricted Modification or a Software copy containing one. This restriction applies to source code, executable builds, containers, patches, and configuration files, whether supplied publicly or privately, with or without payment. Supplying such material to even one friend is outside the personal exception.
You may not let another person use functionality enabled by Your Restricted Modification, including through a shared installation, a user account, remote access, an API, or a hosted service. Moving the bypass into a separate component or entitlement service does not expand the personal exception.
As a contractual obligation where validly agreed, You also agree not to supply patches, scripts, plugins, or other executable materials specifically designed to enable other persons to bypass the Software's Paid Feature Controls. This obligation addresses such targeted materials; it does not assert copyright in independent ideas or general-purpose development tools, and it does not bind persons who have not agreed to it.
These restrictions do not prohibit general technical discussion or lawful security research. Describing a targeted patch, configuration, or executable material as discussion does not create permission to supply it under this license, whether separately or embedded in a post. This rule remains subject to Section 11, including rights to use information or excerpts without contractual restriction under mandatory law.
You may privately supply relevant material directly to Phalcode or its authorized representatives for confidential review as a security report, defect report, fix, or proposed contribution. This exception permits those recipients to review the material, without authorizing its supply to other persons. Contributor permissions for inclusion in the project are addressed separately in Section 9.
5.4 Boundaries of the exception
This exception authorizes changes to Your own Software installation. It grants no permission to access Phalcode's or any third party's servers or accounts without authorization, forge credentials for an external service, obtain another person's subscription, use leaked secrets, or bypass protection of third-party works. It provides no entitlement to cloud services, support, downloads, or other resources supplied separately by Phalcode.
Phalcode may separately authorize a specified distribution, shared use, or other activity in writing. Without such authorization, the personal exception remains limited by this Section 5.
6. Remote access and shared installations
You may operate a Software installation for Yourself and other persons for Noncommercial Purposes, subject to validly applicable feature entitlements and these terms.
Other persons may not use functionality enabled by a Restricted Modification under the personal exception. That prohibition applies even if the installation is private and its users are friends or household members. You must keep any personally unlocked functionality inaccessible to them.
Commercial hosting or other commercial remote access requires separate permission under Section 3. Remote use alone does not count as distribution for Section 4's source-delivery requirement. It remains subject to the noncommercial limitation and all of Section 5.
7. Third-party material and legal ownership
Phalcode grants only rights it owns or is authorized to grant. Copyrights remain with their respective holders.
Components, dependencies, artwork, documentation, or other material expressly supplied under a separate license remain governed by that license. This license neither removes their existing permissions nor replaces their conditions. You must preserve their required notices and comply with their licenses.
The ShareAlike requirements for Phalcode-covered material do not change a separate license applicable to genuinely independent third-party material. You may not combine or distribute material in a manner that requires incompatible permissions. Obtain any additional permissions needed before making such a distribution.
8. Attribution, branding, and paid licensing
The attribution requirements in Section 4 permit truthful identification of the Software's origin. They grant no trademark license for naming, branding, or promoting an unofficial product as GameVault, GameVault+, or Phalcode, except where applicable law permits the use without permission.
You must not imply Phalcode's approval or endorsement of a fork, build, service, or modification. This does not prohibit accurate descriptions of compatibility or origin permitted by law.
Phalcode may offer material it owns or controls under separate commercial or other licenses. Your permissions under this public license do not restrict that ability. Phalcode must itself respect rights belonging to contributors and other third parties.
9. Patents and contributions
For activities permitted by this license, Phalcode also grants a worldwide, royalty-free, non-exclusive license to patent claims it owns or is authorized to license that would necessarily be infringed by those activities with the Software as supplied by Phalcode. The patent permission does not cover claims infringed solely because of additions or changes absent from that supplied Software, or patents Phalcode is not authorized to license. It lasts for the applicable patent term, subject to Section 10.
When You license Your own covered modifications to recipients under Section 4, You grant those recipients a patent license on the same terms for claims You are authorized to license that would necessarily be infringed by Your modifications, alone or in their combination with the Software as You distribute it. This obligation grants no rights in third-party patents You cannot license.
Publishing a fork under this license does not assign its author's copyright to Phalcode. Contributions submitted for inclusion in a Phalcode repository are subject to the separately presented Contributor License Agreement when validly accepted. This public license does not replace that agreement, establish acceptance of unseen contribution terms, or create retroactive contributor permissions.
10. Duration, breach, and reinstatement
The grants last for the applicable copyright or patent term while You comply with this license.
Subject to mandatory law, an exercise of licensed rights outside the conditions in Sections 2 through 8 is not authorized by this license. Upon that breach, Your copyright and patent grants under this license terminate for the Software release or releases involved in that breach, including Your modified copies of them. Permission for unrelated releases and rights under separate licenses do not terminate merely for that reason. To the extent a promise concerns conduct that requires no licensed intellectual-property right, its breach has contractual consequences only where a valid contract and applicable law provide them; it is not converted into copyright infringement by this license.
For Your first breach of this license, the terminated grants are reinstated prospectively when You fully cure the breach within 30 days after You become aware of it. A continuing breach counts as the same breach until cured; obtaining another copy does not reset the opportunity for first-breach reinstatement. Cure requires You to stop the prohibited activity and remove copies from locations You control. You must also take reasonable steps to stop further unauthorized supply or access. You need not perform acts that are technically impossible or unlawful. Reinstatement does not retrospectively authorize the breach or erase accrued claims.
For a later breach, or a first breach not cured within that period, reinstatement requires Phalcode's express written agreement or a right provided by mandatory law. No contractual penalty or fixed damages amount is imposed by this license.
Termination of Your grants does not terminate permission independently held by compliant recipients for copies lawfully supplied to them. It creates no permission for prohibited distribution of Restricted Modifications.
Terms concerning ownership, the limits of granted rights, accrued claims, warranty, liability, governing law, and interpretation continue to apply as relevant after termination.
11. Mandatory rights and statutory exceptions
This license does not restrict conduct that applicable mandatory law allows without Phalcode's permission. Its restrictions apply only to the extent legally effective.
In particular, it does not override mandatory rights concerning necessary backup copies, observation or testing of a program, permitted decompilation for interoperability, lawful security research, or applicable copyright exceptions. For German computer-program law, the mandatory protections reflected in Sections 69d, 69e, and 69g of the German Copyright Act remain unaffected.
Mandatory consumer protections and rights arising under a separate purchase or subscription agreement remain unaffected. Nothing here extends Phalcode's rights into unprotected ideas or facts, user-owned content, or independently licensed third-party material.
12. Warranty and liability
Unless Phalcode separately agrees otherwise, this public license includes no commitment to support, update, maintain, or provide a particular feature or availability level. Phalcode makes no additional contractual guarantee of performance, suitability for a particular use, or freedom from defects. Statutory rights and separately agreed guarantees remain unaffected.
Liability is unlimited for intent and gross negligence, culpable injury to life, body, or health, fraudulent concealment of defects, and a breach of an expressly assumed guarantee within its scope. Liability under the German Product Liability Act and any other liability that cannot lawfully be excluded also remains unaffected.
For simple negligence, liability for breach of a material contractual obligation is limited to loss reasonably foreseeable and typical for the agreement. A material contractual obligation is one whose performance is necessary to fulfill the agreement and on which the other party may ordinarily rely. Subject to the preceding paragraph and mandatory law, liability for other simple negligence is excluded.
These provisions apply correspondingly to persons acting for Phalcode. They do not reduce any statutory liability privilege applicable to a gratuitous grant or limit rights under separately applicable consumer or digital-product rules.
13. Applicable law and interpretation
German law governs this license to the extent a choice of law is permitted. Consumers retain protections of mandatory law that would otherwise apply to them. This license imposes no exclusive court or venue requirement.
This license applies only where version 1.0 is expressly designated for the material concerned. A later license version applies only when separately offered and applicable to that material; publication of a new version does not amend existing grants automatically.
Permissions already granted for earlier releases or material under another license, including Creative Commons licenses, remain available according to those earlier terms. This license does not retrospectively withdraw permission to modify or distribute that material. Phalcode must have sufficient rights before applying these terms to material containing earlier contributions.
If a provision is invalid or has not become part of an agreement, the consequences are governed by applicable law, including Section 306 of the German Civil Code where applicable. The remaining agreement continues only to the extent provided by law. No invalid restriction is automatically replaced with the broadest enforceable restriction.
Additional permission or a waiver by Phalcode must be express and attributable to an authorized representative; an email may satisfy a requirement for writing in this license unless mandatory law requires a stricter form. Failure to enforce a term on one occasion does not itself waive it for another occasion.
This license is a source-available license containing noncommercial and redistribution restrictions. It is not an OSI-approved open-source license.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fields🔧 Planned
Activity
[-]Switch to GPL + Commons Clause License[/-][+]Switch to Open Source License + Commons Clause Combination[/+][-]Switch to Open Source License + Commons Clause Combination[/-][+]Switch to Open Source Code License + Commons Clause Combination[/+]DACRepair commentedon Mar 31, 2024
I already saw this coming. All I can say is make sure you are careful about changing licences when moving to a paid model with an open source project (see redis recently). I'm all for the free market etc etc, but this just seems like another step towards closed source / monetization. At best I wish you the best of luck, but in reality this is another push to prevent users from the "allowed circumvention" of your paid features you promised, which is just a glorified federation service. Good luck!
Alfagun74 commentedon Mar 31, 2024
@DACRepair
No, this isn't another attempt to hinder users from "allowed circumvention.", or a step towards closed source. We're simply revising our license terms to better suit code. It's become apparent that our current CC BY-NC-SA 4.0 license isn't ideal to license code and has caused some complications and questions.
We're only considering transitioning to a code license that closely aligns with the existing terms, such as a copyleft-license with a commons clause combination. Legally, nothing should change; it's merely a move to optimize the license for our code while maintaining the same terms. Our plans for "allowed circumvention" or GameVault+ remain unchanged and have nothing to do with this license update.
DACRepair commentedon Mar 31, 2024
While I want to believe the best intentions, you need to understand that a business must benefit it's board members and/or it's owners. Going commercial means that the assumption of monetization, because that increases profit generally.
Compatibility with other licenses: meaning you have software that is licensed in a way that is compatible with other licenses from dependencies. This is straightforward.
The CC doesn't really cover software because it doesn't cover derivative. This means that the binary derivative are not really covered. I could easily circumvent your monetized code and redistribute, and there is not a lot you could do about it. This means you can have control of your monetized code usage, taking away from sales. This is the "to the benefit" part I spoke of.
While it is easy to assume the worst, and I do agree a better OSS license is needed, I can see how this is driven by business decisions. You have decided to monetize some API functions and some not on FOSS software, which tells me that you don't really support derivation of your software. Plus "we allow you to do this" doesn't really cut it legally since that can be revoked at any time.
All of this stinks of dishonesty.
Alfagun74 commentedon Mar 31, 2024
Alright Sherlock @DACRepair, there seems to be some misunderstanding. GameVault has never been nor was it ever intended to be FOSS. It has always been a free commercial product developed by an indie team of two devs. There are no board members involved.
To understand the reasoning behind the decision to not make it open-source, please refer to this and this.
This statement is incorrect. Its clearly stated in the first section of the license:
I understand your concerns about switching licenses, especially given past instances of rugpulls by larger companies. However, this isn't the case here. There's no need to play detective and search for hidden greedy agendas within our indie company with a yearly total revenue of about 200$ ffs..
We aren't gating off essential features with GameVault+, and the decision to consider a license switch stems from user feedback on Discord, expressing concerns about the current license's suitability for code and its potential legal ambiguities.
You can fork and change whatever you want in GameVault, like bypassing paywalls. The current license only
Same terms apply if we would switch to a CopyLeft Open Source License + Commons Clause combination.
Have a nice day.
wieluk commentedon Feb 26, 2025
Hey, I think you can't just use a project like Ludusavi with CC BY-NC-SA 4.0 or Open Source Code License + Commons Clause Combination.
Their license is MIT:
https://github.com/mtkennerly/ludusavi/blob/master/LICENSE
And MIT does not allow imposing additional restrictions.
Alfagun74 commentedon Feb 26, 2025
Hey @wieluk,
thanks for your concern! You are partially right — I hadn’t included the copyright notice, but I’ve corrected that now.
Other than that, the MIT License remains a very permissive open-source license that allows unrestricted use, modification, and even commercial distribution, as long as the original copyright notice is retained. We can use it however we like and apply additional terms to our own release, as long as we don’t restrict anyone’s rights to the original MIT-licensed code.
P.S.: Just to clarify, when the MIT License states that you are permitted “to deal in the Software without restriction”, it explicitly means that you have the right to do so without any limitations, including using, modifying, distributing, sublicensing, and even selling the software.
[-]Switch to Open Source Code License + Commons Clause Combination[/-][+]Planned license change: Phalcode Source-Available License 1.0[/+]Alfagun74 commentedon Nov 6, 2026
Migrated from
Phalcode/gamevault-app(was #381) as part of the GameVault 2 release. GV1 is feature complete, so the remaining backlog moves here and gets re-checked against the new frontend.