I'm working on a cloud Rating Engine for anybody to use. I've finished it, and it works completely fine on the example project. Unfortunately, when the required sprites are copied to the backpack and placed in another project, it doesn't work right.

Here is the example project: http://scratch.mit.edu/projects/26127896/

Here is what happens when I move it to a new project: http://scratch.mit.edu/projects/26127284/

Please help! I worked very hard on this, and I NEED it to work.

Bump

Bump again.

andrewjcoleRMX wrote:

I'm working on a cloud Rating Engine for anybody to use. I've finished it, and it works completely fine on the example project. Unfortunately, when the required sprites are copied to the backpack and placed in another project, it doesn't work right.

Here is the example project: http://scratch.mit.edu/projects/26127896/

Here is what happens when I move it to a new project: http://scratch.mit.edu/projects/26127284/

Please help! I worked very hard on this, and I NEED it to work.

In the new project, before running a script from another project, be sure to create a cloud variable of identical name to any transplant cloud variable.

I don't understand. Would you be willing to remix and show me what you mean?

What he's saying is to create new variables with the same names as the ones that are in your backpack's script. Then import the script.

Any cloud variable that is in a script from another project needs to be created before the script from the other project is run.

Click ‘Make a variable’ and check the ‘Cloud variable (stored on server)’ box.

Then create a cloud variable in the new project for each cloud variable in the script from your backpack.

Be sure to name the new cloud variables the same as those in the script from your backpack.

So you would want to create 1, 2, 3, and 4 as cloud variables in the new project and then add the scripts from the backpack.

Also, if you end up with a variable for this sprite that is supposed to be for all sprites, delete the variable and re-create it for all sprites.

TheHockeyist wrote:

What he's saying is to create new variables with the same names as the ones that are in your backpack's script. Then import the script.

Yeah.

Cloud variables should be created in advance. Also, possibly, global (stage) variables.

Sprite (local) variables do not need to be.

Oh gosh. I might as well forget about releasing this engine to the public. That's not something I want in the instructions for something that's supposed to be “easy to implement”.

Part of the challenge is figuring out how to write instructions so it is easy to implement.

It may take a number of rewrites, but it can probably be done.

TimothyLawyer wrote:

Part of the challenge is figuring out how to write instructions so it is easy to implement.

It may take a number of rewrites, but it can probably be done.

Ok, well thanks. I might get someone to help me with that. Would you be willing to help? You don't have to, but I'll give you credit if you decide to.