|Ⅰ||This article along with all titles and tags are the original content of AppNee. All rights reserved. To repost or reproduce, you must add an explicit footnote along with the URL to this article!|
|Ⅱ||Any manual or automated whole-website collecting/crawling behaviors are strictly prohibited.|
|Ⅲ||Any resources shared on AppNee are limited to personal study and research only, any form of commercial behaviors are strictly prohibited. Otherwise, you may receive a variety of copyright complaints and have to deal with them by yourself.|
|Ⅳ||Before using (especially downloading) any resources shared by AppNee, please first go to read our F.A.Q. page more or less. Otherwise, please bear all the consequences by yourself.|
|This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.|
PlayMaker is a very popular visual scripting tool (based on finite-state machine, FSM for short), also a hierarchical logic framework for Unity, developed by Hutong Games from China. Game designers and programmers can use PlayMaker to conduct interactive development with Unity, and quickly complete prototyping of games. Therefore, it is suitable for both independent developers and team collaboration, greatly improving the game development efficiency.
PlayMaker has many advantages, such as the ability to quickly implement many actions without having to write a single line of code, easy and concise chart management, the ability to play game directly, real-time error checking, the ability to set breakpoints and step-by-step status, etc. However, its disadvantages are also quite obvious. For example, the actions that can be implemented in a few simple lines of code require many states to be implemented by PlayMaker; although it’s possible to make a full game without writing a single piece of code, it’s hard for PlayMaker to make a commercial game, because there are so many features that can’t be implemented at all.
What can really be called a “visual programming plug-in” for Unity should be uScript, while PlayMaker is nothing more than one “visual interaction design plug-in” for Unity. Because PlayMaker allows only one “programming strategy”: FSM, and the design idea of FSM strategy is different from the normal design approach when writing program scripts. Specifically, PlayMaker provides a visual solution that allows users to design and implement interactive logic in Unity using the FSM design idea without having to write scripting code.
PlayMaker was supposed to be the “savior” who would save game makers from the sea of code, but that is just a joke. It can get the user out of writing code, but that does not mean that users can be freed from the task of programming. And because PlayMaker is entirely based on the FSM strategy, it actually makes the programming job harder. Therefore, it is only the first step to learn how to use PlayMaker itself. What is more important is to use this tool to train our thinking and solve practical problems.
The real purpose of PlayMaker is not to replace developer’s programming work, but to give non-programmers a tool to quickly prototype games, allowing them to implement the gameplay design in their own minds on their own. As for what PlayMaker can actually do, that’s a tough question to answer. PlayMaker is just a tool, with advantages and disadvantages. What we can do with this tool is up to us, not the tool.
// Key Features //
|Realize your creative vision without knowing how to program!|
|Intuitive Visual Editor|
// Official Demo Video //
// System Requirements //
- Supported Unity versions: v5.3.0+
// Edition Statement //
AppNee provides the PlayMaker multilingual full registered package for Unity.
// Related Links //
- PlayMaker Official Video Tutorials
- PlayMaker User Tutorials Index
- PlayMaker User Manual
- PlayMaker Showcase
// Download URLs //
|If some download link is missing, and you do need it, just please send an email (along with post link and missing link) to remind us to reupload the missing file for you. And, give us some time to respond.|
|If there is a password for an archive, it should be "appnee.com".|
|Most of the reserved downloads (including the 32-bit version) can be requested to reupload via email.|