When comparing PlayMaker + Unity3D vs uScript + Unity3D, the Slant community recommends PlayMaker + Unity3D for most people. In the question“What are the best 2D game engines?” PlayMaker + Unity3D is ranked 77th while uScript + Unity3D is ranked 97th. The most important reason people chose PlayMaker + Unity3D is:
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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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.
Pro Automatically generates nodes for third-party script assets
uScript's nodes are a visual representation of actual code blocks, and it takes advantage of C#'s reflection capabilities to automatically create nodes for any scripts it finds in your project, regardless of the source. This makes it inherently compatible with pretty much everything.
Custom nodes can also be created by hand, for cases where the automatically created ones contain more elements than they actually need.
Pro Versatile flow diagram script model
Modeled after UDK's Kismet (the predecessor to UE4's Blueprint), uScript's scripts resemble flowcharts where each box represents a function or value, with connections between them representing program flow. This provides a better at-a-glance indication of game logic than a simple list of events, and makes complex behaviors easier to accomplish.
Pro Generates C# source code
Nodes are translated directly to C# files in your project. This is great for learning to code, and also for advanced users who can use uScript for fast prototyping and then further optimize the scripts if necessary.
Cons
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.
Con Not that easy to use
It's a lot more complicated compared to something like Playmaker. Same tasks take a lot more time.