Jump to content
  • 0
Sign in to follow this  

Important Changes * Licensing Policy *




Hello Community,
since we got in the last days some leaks from our source and some attacks from people who wants to crash our community and our work we need to change some
of our core distribution ways.
And before you will think now; "OMG, a closed development again!" No we wont going complete closed source or something like this! We will still provide as before our compiled Download Packs,

for free and accept everyone as developer who can provide that he can help in our project.
For that, we need to change some points to be able to provide the best quality Gameserver, like before.
So, please read carefully the next lines.
To protect our work and to protect the whole project, we will implement a free of charge Dual-licensing (DLS) in to our core; GPL v3&Proprietary Licenses)
With this feature we can protect ourself against leaker or unserious persons,  which try to sale or hijack our development, and call it their own.


Dual-licensing is the practice of distributing software under two or more different sets of terms and conditions.

This may mean multiple different software licenses or sets of licenses.

Prefixes may be used to indicate the number of licenses used, e.g. dual-licensed for software licensed under two different licenses.

When software is multi-licensed, recipients can choose the terms under which they want to use or distribute the software. The distributor may or may not apply a fee to either.

The two usual motivations for multi-licensing are license compatibility and market segregation based business models.


An alternative approach to monetising your code is dual-licensing. This involves releasing your software under a strong copyleft licence such as the GNU GPL, and also making available

a version under an alternative licence, thus allowing users who do not wish to be bound by the GNU GPL to pay for the non-copyleft version. Generally, they would do this because they

wish to produce a product based on the code but not confined by a copyleft licence. Whether the additional administration involved in this model is worth it for you will depend on how likely

you think it is that customers will want to pay for the right to produce non-copyleft derivative products. You should remember that in order to offer an additional non-copyleft licence, you must

have the agreement of all contributors or own all the copyright in the code yourself


Multi-licensing is commonly done to support free software business models in a commercial environment. In this scenario, one option is a proprietary software license, which allows the

possibility of creating proprietary applications derived from it, while the other license is a copyleft free software/open-source license, thus requiring any derived work to be released under

the same license.

The copyright holder of the software then typically provides the free version of the software at little or no cost, and profits by selling proprietary licenses to commercial operations looking

to incorporate the software into their own business. This model can be compared to shareware.



And now, we wish to make something clear to anyone who reclaimed that our Source-Code can not be accessed for the large Public, or we are not allowed to distribute binaries, without the Source-Code

Here are some questions and Answers from GNU:

Frequently Asked Questions about the GNU Licenses


Does the GPL require that source code of modified versions be posted to the public?



The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization

can make a modified version and use it internally without ever releasing it outside the organization.
But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program's users, under the GPL.
Thus, the GPL gives permission to release the modified program in certain ways, and not in other ways; but the decision of whether to release it is up to you.


Disclaimer: We are not releasing our gameserver "to the public in some way", as we are a community and an organization. That are the rules with you sign up to the membership our community.

                   We do not offer our modifications to the "public" outside our community and "use internally without ever releasing it outside the organization."

We do not public downlaods outside our community, every download must be made with community member access rights and exclusively from our Download Application


GNU Version 3, 29 June 2007
6. Conveying Non-Source Forms.



Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you

offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that

is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of

source, or (2) access to copy the Corresponding Source from a network server at no charge.



A company (n.a. organization) is running a modified version of a GPL'ed program on a web site. Does the GPL say they must release their modified sources?


The GPL permits anyone to make a modified version and use it without ever distributing it to others. What this company (n.a. organization) is doing is a special case of that. Therefore, the company (n.a. organization)  does not have to release the modified sources.

It is essential for people to have the freedom to make modifications and use them privately, without ever publishing those modifications. However, putting the program on a server machine for the public to talk to is hardly “private†use, so it would be legitimate to require release of the source code in that special case. Developers who wish to address this might want to use the GNU Affero GPL for programs designed for network server use.



Is making and using multiple copies within one organization or company (n.a. organization)  “distributionâ€? (#InternalDistribution)


No, in that case the organization is just making the copies for itself. As a consequence, a company or other organization can develop a modified version and install that version through its own facilities, without giving the staff permission to release that modified version to outsiders.
However, when the organization transfers copies to other organizations or individuals, that is distribution. In particular, providing copies to contractors for use off-site is distribution.


Disclaimer END


Aion-Core 4.8 Licensing
by aion-core.net

 For you as end user we have three different license types.


General Requirement:

Public Server, Homepage with our Gameserver Logo and minimum 20 player online 

3. 6 Month License (SML)
This license is for everyone who already own a private server, or a dedicated server. This license has no restrictions either and its fully working.

You get this license if you are a "Developer, VIP Gold and Server Owner" in our Community.
You will be able to download every 6 month a new license.
4. One Year License (OYL)
This license is for everyone who already own a private server, on a dedicated server. This license has no restrictions either and its fully working.

You get this license if you are a Core Developer "Committer" , "VIP Platin and Server Owner" in our Community.
You will be able to download every year a new license.


We can assure everyone that there will be no negative impact with introducing our LS.
Nobody will feel any negative changes or quality issues. You can use our core as before without any restrictions.
We hope that you will understand this steps, they are really necessary.


The above licensing are avaible only for a stable versions of our release.

Alpha or Beta development are not for public use.
Licensing issues (before you ask 100x in forums)


1. Our Gameserver server requires an Internet connection for license validation. That will be requested from the Licensing Server, everytime a player login in game.
    That means, our Gameserv will not run without an internet connection, just in LAN or Offline.


There is no reason that the Gameserver shutdown except the followings:


1. The Gameserver has an internet disconnection or has no internet connection and so he is not able to validate his license.

2. Using an improper license, for example, using only the default trial license with more the 6 players loged in.


For everyone who maybe asking what about the Licensing server. That is located on the Nr.1 premium webhosting provider in Germany with 99.9% Uptime Guarantee. Our webiste/forum is located on the same place.


Your Aion-Core Dev Group Team

Share this post

Link to post
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Sign in to follow this  

  • Create New...