First there was 1.0, then together with 2.0 I've made an announcement that more or less once a year there will be a new engine version.
Esenthel 3.0 should've been released a few months ago, but I was too busy with general development to think about packaging it as a new standalone version.
So the time for a new version has come now, normally I would've call it Esenthel 3.0, and in the next year there would be 4.0, etc. However, because of recent announcement from other game engines, that they're moving into subscription based system, I've decided to do the same, and because of that, the new release won't be called EE 3.0, 4.0. There will be just Esenthel Engine, continuously updated all the time, but as a subscription.
Why am I moving to subscription system? If a potential customer sees that he can get another engine for initial payment of ~10-20$, then most likely he will not choose a bigger up-front fee of Esenthel's current 199$. That's why I'm introducing multiple options:
-monthly subscription (binary only)
-yearly subscription (binary only) with 20% savings
-yearly subscription (binary+source only) with source access
(unfortunately I'm not introducing monthly binary+source option, because for me it's too risky at the moment to make the source to be available at so low cost).
Introducing subscription system doesn't change the situation much from the customer side, because normally I'd be releasing new engine version (3.0, 4.0, etc.) and charging fee for upgrade from an earlier version, with the subscription it works the same but it's automated, and with more options.
The new licensing system is available here:
http://www.esenthel.com/?id=store&cat=0
When subscribing to the source license, in order to access the source code, you need to:
1. Buy Source License.
2. Click on 'Set GitHub account for this license' next to your license key in the 'Download' area.
3. Enter your GitHub account name.
4. Use this account to access the source code on Esenthel GitHub page
https://github.com/Esenthel/EsenthelEngine
At the moment, at the step #3 you don't get instant access, because I need to manually give you permission on the GitHub website to view the source code, this should take within 24 hours. But I'll try to make this process automated ASAP so you can get access instantly.
Also, because I'm releasing a brand new engine version, there won't be any more updates to 2.0.
However if you have a 2.0 license that was purchased less than a year ago (after 6th April 2013), then you can send me PM including your license key, and I can change your 2.0 license to the newer "engine binary license yearly subscription". It will have the same purchase date, which means that it will expire 1 year after your original purchase. (So if you've bought 2.0 license 9 months ago and want to upgrade it now, then you get 3 months of the new license, if you've bought 3 months ago, then you get 9 months of the new license).
If you don't wish to upgrade you can stick with 2.0 license.
Upgrading process may take a few days depending on the number of PM's that I get, thank you for your patience.
If you want to go with the new source license (highly recommended
), then you need to make a brand new purchase for the source license (there are no upgrades to the source license from an older license).
Also please read carefully the license details on each subscription item as they're now slightly different and reflect the subscription related info and source access info.
About releasing engine's source code:
I was reluctant to this initially, obviously due to security reasons, but now that other engines do this, I have no other choice.
However, I'm completely excited, because I'm sure that thanks to release of the source code, much more people will be able to collaborate on it together (github is supposedly good at this), and make the engine grow faster.