playMaker

Author Topic: Why can't PM just include all the actions?  (Read 1820 times)

wheretheidivides

  • Sr. Member
  • ****
  • Posts: 496
Why can't PM just include all the actions?
« on: April 17, 2015, 01:12:44 PM »
So Unity does not include unused assets in the final build.  This means you can have tons of playmaker scripts in a project and the unused ones will not be put into the final build (as far as I know).  So, if this is the case, why can't you guys just include all of the actions in the ecosystem into projects?  Or have a button to press to get all of the new ones and import them.  Just wondering.

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15620
  • Official Playmaker Support
Re: Why can't PM just include all the actions?
« Reply #1 on: April 17, 2015, 01:41:14 PM »
Hi,

This would be great, but not really practical for many reasons:

1: *ALL* scripts are recompiled everytime there is a change, so the more scripts the longer Unity will take to recompile, build, etc etc, so keeping a projec to its bear essential is highly recommanded, even when not using PlayMaker.

2: Unity is moving away from including everything, Unity 5 uses Modules, which soon will likely become optionnal so that someone not using physics can remove it all together and no be bother about the time it takes to deal with that aspect.

3: some actions are platform dependant, and de facto, not every action make sense to have, or would throw errors.

4: depending on the projects, some actions will never be used, why polluting the actions browser with a huge list with mayn actions totally not needed.

So, yes it's more effort, but that's why  I am trying to solve with the Ecosystem, so that getting actions is just as easy as browsing existing actions with the Playmaker Actions browser.

There are plans for the ecosystem to offer a way to favorite actions and in one click indeed download all your favorite. But you can do this already yourself very easily. select all actions you like to have, make a package out of it, and keep that package in a spot you can quickly access in your os, and then when you create a new project, simply get that in there as well.

 Bye,

 Jean