0
\$\begingroup\$

I'm integrating in-app purchases in my game. To do so, I chose to use Soomla (http:soom.la) asset. I use the free version registering for the grow bundle. I've downloaded a unitypackage named unity3d-grow-spend from my grow web console.

When I'm going to import the unitypackage I find that it wants to import things in a variety of top-level directories, like:

/GROW/*
/Plugins/Android/*
/Plugins/GROW/*
/Plugins/iOS/*
/Plugins/Soomla/*
/Plugins/WP8/*
/Soomla/*
/WebPlayerTemplates/SoomlaConfig/*

All this installs inside my /Assets directory.

The thing is that in my assets I only have

/Assets/Scenes
/Assets/Plugins

and I do not want pollution in there.

Question:

Is it safe to move /Assets/GROW into /Assets/Vendor/GROW and move Soomla and WebPlayerTemplates also into the Vendor directory?

Or doing that movement some in-app purchases mechanism will fail?

This would result in having only

/Assets/Scenes
/Assets/Plugins
/Assets/Vendor

in the top-level, which is rather nice.

\$\endgroup\$

1 Answer 1

1
\$\begingroup\$

Yea, you can safely replace folders and keeping in mind about the Special Folders Name. Other than that you can play around with.

\$\endgroup\$
7
  • \$\begingroup\$ As I use the free version, which is a bundle to grow, I moved both, the /GROW/* and the /Soomla/* into /Vendor/GROW/* and /Vendor/Soomla/*. Doing so, gives some erros into the log window. Instead, I could still compile and publish, and publication works properly connecting to the play-store in-app purchase market performing the operations from inside Vendor. Thanks @Hamza. I'll report more if I ever find why those errors or how to correct them. \$\endgroup\$ Commented Feb 28, 2016 at 11:33
  • \$\begingroup\$ Well... In fact... there is a problem with this move... then it works in the build but stops to work in the editor... Seem no move possible at this moment. \$\endgroup\$ Commented Feb 28, 2016 at 13:23
  • \$\begingroup\$ Can you paste that error? \$\endgroup\$ Commented Feb 28, 2016 at 18:27
  • \$\begingroup\$ Sure, here it is: pastebin.com/AE7p9uPL - First, the 3 errors I can see that relate to Soomla. Then, the stack-traces for each of 3. \$\endgroup\$ Commented Feb 28, 2016 at 19:43
  • \$\begingroup\$ Man it is trying to use same path that came with it by default, means Assets/GROW and so on. I didn't use Soomla, so what I can say is to find that editor script, from which this error come from and change its path to Vendor/GROW... \$\endgroup\$ Commented Feb 28, 2016 at 20:38

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.