-Io- wrote:

dvargasews wrote:

Letting others access variables in your projects might be a good idea for sharing highscores between remixes that don't have a significant effect on the actual gameplay physics (like a recoloring), but I think that in that case, variable sharing between projects by different users should require the consent of all users who have projects that the variable is being shared between.

It's only between one user's projects, not multiple users

dvargasews wrote:

-Io- wrote:

dvargasews wrote:

Letting others access variables in your projects might be a good idea for sharing highscores between remixes that don't have a significant effect on the actual gameplay physics (like a recoloring), but I think that in that case, variable sharing between projects by different users should require the consent of all users who have projects that the variable is being shared between.

It's only between one user's projects, not multiple users

I know. I was asking if it could be for multiple users.

jokebookservice1 wrote:

dvargasews wrote:

-Io- wrote:

dvargasews wrote:

Letting others access variables in your projects might be a good idea for sharing highscores between remixes that don't have a significant effect on the actual gameplay physics (like a recoloring), but I think that in that case, variable sharing between projects by different users should require the consent of all users who have projects that the variable is being shared between.

It's only between one user's projects, not multiple users

I know. I was asking if it could be for multiple users.

If it was, somebody could edit their project after the consent is received and mess up the variables.

How about it is read-only access, and you get a notification in your mailbox, like this:

IgnaxioScratcher wrote:

Reported for scratch team finally review this post!!!

dvd4 wrote:

don't read text below
fnaldklafn waohiawiugduo oprgjrgjocvoj fsoifief

Told you so

Dont make unconstructive post putting a joke like that

dvargasews wrote:

jokebookservice1 wrote:

If it was, somebody could edit their project after the consent is received and mess up the variables.

How about it is read-only access, and you get a notification in your mailbox, like this:

Each party would be able to opt out at any time.

zorket wrote:

dvargasews wrote:

jokebookservice1 wrote:

If it was, somebody could edit their project after the consent is received and mess up the variables.

How about it is read-only access, and you get a notification in your mailbox, like this:

Each party would be able to opt out at any time.

Sharing variables between users received negative criticism in the past due to possible messing up other projects and moderation issues. If bridge variables are added, they should at least be started being single-user.

dvargasews wrote:

How about cross-user bridge variables are only available to users who have been Scratchers for at least two months?

dvargasews wrote:

This reminds me of mesh. Am I right?

stickfiregames wrote:

dvargasews wrote:

This reminds me of mesh. Am I right?

It does actually sound very similar, although I never thought of Mesh that way. As far as I can remember the other project's variables in Mesh were read-only, so bridge variables would have more functionality. I also found way Mesh read variables from the sensing block was quite confusing when I tried it several years ago, this suggestion's way of importing variables sounds more intuitive.


Anyway, I support this, although I probably have already.

I saw a few pages back some people were no-supporting because of the bridge variable shop some Scratchers are running. That doesn't seem like a very reliable workaround: as far as I can tell (they are describing it quite vaguely, and I don't blame them if it's what I think it is) it uses an exploit that lets you modify other people's variables, which the ST could fix and break the whole thing. There is also the possibility that it could just be discontinued.

stickfiregames wrote:

dvargasews wrote:

This reminds me of mesh. Am I right?

It does actually sound very similar, although I never thought of Mesh that way. As far as I can remember the other project's variables in Mesh were read-only, so bridge variables would have more functionality. I also found way Mesh read variables from the sensing block was quite confusing when I tried it several years ago, this suggestion's way of importing variables sounds more intuitive.


Anyway, I support this, although I probably have already.

I saw a few pages back some people were no-supporting because of the bridge variable shop some Scratchers are running. That doesn't seem like a very reliable workaround: as far as I can tell (they are describing it quite vaguely, and I don't blame them if it's what I think it is) it uses an exploit that lets you modify other people's variables, which the ST could fix and break the whole thing. There is also the possibility that it could just be discontinued.

IcyCoder wrote:

We are making Bridge variables so no support

Gabriel2900 wrote:

IcyCoder wrote:

We are making Bridge variables so no support

^