Recently there has been some confusion about how the OpenBOR license works, and how/why Chronocrash will not support alternate versions of OpenBOR. Hopefully we can clear some of that up here.
License
OpenBOR's license is BSD-derived. There is no point in restating it verbatim here, but the meaning is fairly simple. Anyone who wishes to use the OpenBOR engine or any part of its source code for any reason must include the original license. That license in turn protects the existing codebase from misappropriation and its creators from liability.
The license does not prevent you from selling modules made with OpenBOR or from including the OpenBOR executable. It applies to the OpenBOR engine and its codebase, not to your original module assets or materials.
Forks (Unofficial OpenBOR Builds)
One of the inevitable results of an open source codebase is that sooner or later everyone and their dog has a personal fork or port of the software. Although the license allows forks and personal builds of OpenBOR, the ChronoCrash community strongly discourages them. OpenBOR is a very unique application in that it relies entirely on end-user content to operate.
The forking model has already been tried. It did not work for OpenBOR, and it still does not work, for several reasons. One of them is simply resources. We are a small community, and it is already difficult to support a single official version. Despite every effort to maintain backward compatibility, differences from one version to the next are inevitable. Adding horizontal compatibility issues on top of vertical compatibility only serves to splinter the community further.
Any links, advertising, or projects concerning unofficial builds of OpenBOR are subject to removal on sight. There is some leeway for test builds and similar situations, and those will be handled case by case. Attempts to subvert or ignore this policy may result in infractions.
Furthermore, because OpenBOR and its forks remain subject to the original license, we will not recognize any attempt to relicense the engine or claim ownership of its existing code. If an unofficial project introduces worthwhile ideas or legitimate improvements, we may incorporate comparable changes into the official codebase under the original OpenBOR license.
Keep in mind this policy exists to protect the community and maintain a single application with minimal confusion for module creators, not to prevent change. You are always welcome to submit updates and fixes to the official OpenBOR codebase. Assuming your changes are compatible with current development and do not overlap functionality the engine already has, they will likely be added, and you will receive full credit. If you have ideas for the engine, please consider joining our team.
Engine Credit
OpenBOR is royalty-free. Follow the license as explained above and you may use the engine without charge.
That said, there is an unofficial policy that modules include a reasonably prominent splash page stating “Powered by OpenBOR,” or similar. Module creation is no small task, though it is only possible because of the twenty years and counting that have gone into OpenBOR’s development. Giving the engine visible credit is a reasonable courtesy.
Most commercial engines and platforms expect to be recognized, and many charge for the privilege. OpenBOR asks only that you acknowledge the engine and help direct people back to the community behind it. More people means more games, and more fun for all.
License
OpenBOR's license is BSD-derived. There is no point in restating it verbatim here, but the meaning is fairly simple. Anyone who wishes to use the OpenBOR engine or any part of its source code for any reason must include the original license. That license in turn protects the existing codebase from misappropriation and its creators from liability.
The license does not prevent you from selling modules made with OpenBOR or from including the OpenBOR executable. It applies to the OpenBOR engine and its codebase, not to your original module assets or materials.
Forks (Unofficial OpenBOR Builds)
One of the inevitable results of an open source codebase is that sooner or later everyone and their dog has a personal fork or port of the software. Although the license allows forks and personal builds of OpenBOR, the ChronoCrash community strongly discourages them. OpenBOR is a very unique application in that it relies entirely on end-user content to operate.
The forking model has already been tried. It did not work for OpenBOR, and it still does not work, for several reasons. One of them is simply resources. We are a small community, and it is already difficult to support a single official version. Despite every effort to maintain backward compatibility, differences from one version to the next are inevitable. Adding horizontal compatibility issues on top of vertical compatibility only serves to splinter the community further.
Any links, advertising, or projects concerning unofficial builds of OpenBOR are subject to removal on sight. There is some leeway for test builds and similar situations, and those will be handled case by case. Attempts to subvert or ignore this policy may result in infractions.
Furthermore, because OpenBOR and its forks remain subject to the original license, we will not recognize any attempt to relicense the engine or claim ownership of its existing code. If an unofficial project introduces worthwhile ideas or legitimate improvements, we may incorporate comparable changes into the official codebase under the original OpenBOR license.
Keep in mind this policy exists to protect the community and maintain a single application with minimal confusion for module creators, not to prevent change. You are always welcome to submit updates and fixes to the official OpenBOR codebase. Assuming your changes are compatible with current development and do not overlap functionality the engine already has, they will likely be added, and you will receive full credit. If you have ideas for the engine, please consider joining our team.
Engine Credit
OpenBOR is royalty-free. Follow the license as explained above and you may use the engine without charge.
That said, there is an unofficial policy that modules include a reasonably prominent splash page stating “Powered by OpenBOR,” or similar. Module creation is no small task, though it is only possible because of the twenty years and counting that have gone into OpenBOR’s development. Giving the engine visible credit is a reasonable courtesy.
Most commercial engines and platforms expect to be recognized, and many charge for the privilege. OpenBOR asks only that you acknowledge the engine and help direct people back to the community behind it. More people means more games, and more fun for all.
