When comparing MonoGame vs PlayMaker + Unity3D, the Slant community recommends MonoGame for most people. In the question“What are the best 2D game engines?” MonoGame is ranked 9th while PlayMaker + Unity3D is ranked 77th. The most important reason people chose MonoGame is:
Support for iOS, Android, Mac OS X, Linux, Windows (both OpenGL and DirectX), Windows 8 Store, Windows Phone 8, PlayStation Mobile, PlayStation 4, Xbox One, Nintendo Switch, and the OUYA console with even more platforms on the way.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Cross-platform
Support for iOS, Android, Mac OS X, Linux, Windows (both OpenGL and DirectX), Windows 8 Store, Windows Phone 8, PlayStation Mobile, PlayStation 4, Xbox One, Nintendo Switch, and the OUYA console with even more platforms on the way.
Pro Open source
All the code is available to you ensuring you'll have the ability to make changes when you need to or even port to whole new platforms.
Pro Well-known and documented API
The framework implements the XNA 4 API, so games made in XNA can be ported to other platforms using this. This was the same API used by the Xbox Live Indie Games platform so there's lots of documentation online for it.
Pro Managed code
By leveraging C# and other .NET languages on Microsoft and Mono platforms you can write modern, fast, and reliable game code.
Pro Good community
The community MonoGame has to offer is helpful and mature.
Pro Performance on desktop
The performance on desktop platforms matches that of C++, but you still get all the pleasant features that C# has to offer.
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 Slow rate of updates
Versions 3.9 is overdue by a year, and version 4.0 is set to release in 2040.
Con Non-Windows tools are a bit funky
Monogame support for Xamarin Studio or Monodevelop is a bit shaky especially for library references. Only good non-Windows IDE compatible with MonoGame is Rider and that costs money & isn't open-source.
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.
