When comparing Polycode vs PlayMaker + Unity3D, the Slant community recommends Polycode for most people. In the question“What are the best 2D game engines?” Polycode is ranked 32nd while PlayMaker + Unity3D is ranked 77th. The most important reason people chose Polycode is:
Polycode uses Lua and C++ to create native applications for Windows, Mac, and Linux. Mobile platforms are planned for the future.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Can create portable native applications
Polycode uses Lua and C++ to create native applications for Windows, Mac, and Linux. Mobile platforms are planned for the future.
Pro Free and open source
Polycode is free and open source (released under the MIT license). The source code is freely available on GitHub.
Pro IDE for 3D editing
Recently, the editor and its integrated tools have been released in compiled form. Features coding and scene editing in one application.
Pro C++/Lua
Polycode is distributed in a C++ form as well as with IDE. And there's an additional LUA-based scripting system.
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.
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 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 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 Powerful
It basically can do same things as scripting in Unity.
Cons
Con Abandoned
The project does not seem to be maintained anymore: there has been no new release nor commit since mid-2015.
Con No mobile support
Doesn't have support for Android or iOS.
Con Comparatively high learning curve
Although C#, JavaScript, and Boo have extensive documentation available online, it could still be difficult to wrap your head around the library and Unity's component based system.
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.
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.