Several months after we started working on HTML5 game editor, we have decided to open-source it – giving the community a tool that will help you in the game development process. We are thrilled to see the development of other open-source tools and frameworks, and we are hoping that letting people join us in the process of creating this awesome tool will give an additional boost to the future of MightyEditor. Our team is fully dedicated to continuing our work on improving the editor, adding additional features and fixing the bugs.
MightyEditor started out as a simple tool for our own games, but seeing an increased interest from the community, we decided to improve it and develop it as a universal editor that can also be efficiently used by other developers. This strategy leads to money questions. Currently we are funding the editor from whatever we can spare while developing our own games so it takes a chunk of our resources, but in the future we are planing to launch a web service where you will be able to buy advanced plugins, hosting and other goodies for reasonable amount of money. We will be happy to see other developers creating their own free and paid plugins.
Check out online version of the editor or fork it on github.
Some updates that are coming in near future:
- Tileset support
- Texture atlas
- Simple physics support + ninja physics tilemap
- Tweens
THE LICENSE
Copyright (c) 2014 MightyFingers
You can
– use, copy, modify, merge, publish, distribute code free of charge
– write plugins and distribute them under any license you want
– develop games on editor and own full intellectual property
You cannot
– create paid service on top of this software
You must
– include reference to the author – http://mightyfingers.com
– include the license notice in all copies or substantial uses of the work
– publish code modifications you have made
Just a suggestion about the tweening, guys. If you have not already done so already, take a look at Greensock JS. I don’t know if this is desirable to you, or even possible, license-wise, but it might make sense to use this library for tweening.
Hi Michael,
Greensock JS looks like a great tweening library and indeed we haven’t implemented tween editor yet, but it’s in our top priority list. However there are couple of reasons why we won’t use Greensock JS in near future. In short – incompatible licenses, it doesn’t work with canvas and currently we are focusing on Phaser. It may change someday and we would build universal tool working with multiple frameworks.
Thanks for suggestion, we will definitely explore Greensock JS a bit more and try to borrow some good idea from it
I was thinking that licensing might be a problem yeah. I rather stupidly did not even consider the canvas aspect. Either one is a compelling reason to take a pass. Pity, Greensock JS is very nicely done.
Thank for the reply.