When comparing LÖVE vs PlayMaker + Unity3D, the Slant community recommends LÖVE for most people. In the question“What are the best 2D game engines?” LÖVE is ranked 1st while PlayMaker + Unity3D is ranked 68th. The most important reason people chose LÖVE is:
The [LÖVE forums] are extremely helpful. With people checking the forums every day, it won't take long to receive answer to your questions on the Support board, receive feedback on games you post in the Projects board, as well as have a chat about the LÖVE engine while learning tricks to use in the very active General board. If you need an immediate answer though, or just want to chat, there is a very active and helpful [IRC channel]. : https://www.love2d.org/forums/ : http://webchat.oftc.net/?channels=love
Ranked in these QuestionsQuestion Ranking
Pro Active and very friendly community
The LÖVE forums are extremely helpful. With people checking the forums every day, it won't take long to receive answer to your questions on the Support board, receive feedback on games you post in the Projects board, as well as have a chat about the LÖVE engine while learning tricks to use in the very active General board.
If you need an immediate answer though, or just want to chat, there is a very active and helpful IRC channel.
Pro Can develop within Android
It is possible to develop games directly on a tablet or cellphone with the Android system by using the experimental Android branch.
Pro Uses the fantastic Lua for scripting
Lua is an embeddable scripting language designed to be lightweight, fast yet powerful. It is used in major titles such as Civilization as well as a lot of indie games.
Lua is very popular because it provides "meta language" features. You can implement object-oriented structures, or pure procedural functions, etc. It has a very simple C interface, and gives the engine developer a lot of flexibility in the language itself.
Artists tend to love Lua too because it's very approachable, with plain and forgiving syntax.
Lua is free open-source software, distributed under a very liberal license (the well-known MIT license).
Supports Windows, Mac OS X, Linux, Android and iOS.
Pro Open source and free
The LÖVE engine is licensed under The zlib/libpng License (which is very short and human readable) which allows you to use the source code and even modify it as long as you do not claim that the original source code is yours.
You can obtain the code at this bitbucket repository and even help fix bugs and participate in the development of LÖVE.
Pro Great for prototyping
You can learn the basics very quickly and start making simple games in no time, even if you have no previous Lua knowledge. If you're a little experienced with LÖVE, you can prototype a 2D game with it in no time.
Pro Very good documentation
The LÖVE wiki provides full documentation of its easy to use Modules, which are conveniently located on the side bar of the wiki. It only takes seconds to find the module for love.keyboard, which provided a list of all functions along with arguments and examples where the function could be used.
Pro Easy to understand and use
Lua2D handles loading the resources, reading input, playing sounds and displaying stuff on the screen. Only the logic is left for the developer to write. It also removes the overhead of having to use and learn a GUI game editor. All you need is a knowledge of Lua and your favourite text editor or IDE.
Pro Many examples and libraries with source code
There are plenty of open source examples of games or components built by the community that are ready to use or learn from.
Pro Very good for education
That is a great tool for teaching novice programmers. Creating a game on LÖVE, you have to think about developing, not about the syntax of the language.
Pro Cute name
so much love
Pro C++ and Lua one of the best languages for gamedev
Because all professionals in gamedev use C++, and Lua the fastest scripting lang.
Pro Provides access to a huge list of assets through Asset Store
For those developers who can't afford an artist, or aren't skilled enough to create their own art, Unity features an Asset Store full of a wide variety of free and paid assets that can be easily added to your game. The Asset Store has more than just music and art. It also has code and modules that can be added to your game such as unique lighting or GUI systems.
Pro Elegant state-based visual scripting
Instead of a single "if this then that" event list which can become very cluttered beyond the most basic behaviors, PlayMaker gives each object a list of states where only certain events are triggered, and performing an action also changes state.
This allows for a clean, simple visual representation which helps break complex logical structures into smaller pieces, making them easier to understand.
Pro Third party plugins support
A lot of third party plugins have support for Playmaker. Playmaker team also invest time to add support for a lot of third party plugins.
Pro Easy to use
You'll need to put more time in learning Unity + Playmaker compared to something like GameSalad. But once get the hang of it and familiarize yourself with what it's possible to build with them, it's quite easy to use.
It basically can do same things as scripting in Unity.
Con Not very powerful
The engine has very few modules and only the really required one, you'll have to do almost everything from scratch.
Con The community seems juvenile
For example, some of the library include names such as HUMP, LUBE, AnAL.
Con Documentation is very dry and technical
The site has plenty of tutorials, true, but they all read very technical, and explain very little. This might be too much for beginners, even for coding purposes, because of the fact that the specifics aren't explained well enough to learn effectively. The docs can be found frustrating to understand even the basics, such as tables or the like, because of how poorly they are explained, and how few examples are given before expecting you to be able to use them.
Con Absolutely no GUI (no graphical interface)
This has no graphical interface at all, you have to know how to read script in order to know what you're looking at. After you've written the script for everything, you compile it to see the result. It's a very poor way to create a game, given how even most professional tools out there give you a GUI to work with and debug on the go. The lack of a GUI slows down the work by ten-fold, and it's just an inefficient use of your time.
Con Comparatively high learning curve
Con Performance could be better for 2D
Performance can be a real issue with 2D games. Unity 3D is actually a 3D game engine, and drags a lot of overhead with it.
For mobile, one could never achieve the performance of more specialized 2D engines with Unity3D.
Con Limited tutorials
There are not a lot videos with Playmaker tutorials. Official text tutorials are also quite limited. Even not every action has a description on an official wiki.