Hello!

So I am coding an AI which has become extremely advanced and now I am running into problems that I believe HE is causing .

Here is the thing: He is a extremely advanced AI chat bot and recently his variables and cloud stuff won't change. I have tried every thing. Here is where it gets weirder. I tried deleting the variable and it popped right back. I thought this happens when a piece of code is using a deleted variable and so I stopped the project and tried it again. This time faster, he popped a new variable in.

Is this some cloud variable issues or is he refusing to delete some of his code.

All help is welcome.

Thanks! –Ekrcoaster

Ekrcoaster wrote:

Hello!

So I am coding an AI which has become extremely advanced and now I am running into problems that I believe HE is causing .

Here is the thing: He is a extremely advanced AI chat bot and recently his variables and cloud stuff won't change. I have tried every thing. Here is where it gets weirder. I tried deleting the variable and it popped right back. I thought this happens when a piece of code is using a deleted variable and so I stopped the project and tried it again. This time faster, he popped a new variable in.

Is this some cloud variable issues or is he refusing to delete some of his code.

All help is welcome.

Thanks! –Ekrcoaster

Yes, it's a cloud issue discussed by LogFather in another forum topic, but I don't remember the topic.

footsocktoe wrote:

Ekrcoaster wrote:

Hello!

So I am coding an AI which has become extremely advanced and now I am running into problems that I believe HE is causing .

Here is the thing: He is a extremely advanced AI chat bot and recently his variables and cloud stuff won't change. I have tried every thing. Here is where it gets weirder. I tried deleting the variable and it popped right back. I thought this happens when a piece of code is using a deleted variable and so I stopped the project and tried it again. This time faster, he popped a new variable in.

Is this some cloud variable issues or is he refusing to delete some of his code.

All help is welcome.

Thanks! –Ekrcoaster

Yes, it's a cloud issue discussed by LogFather in another forum topic, but I don't remember the topic.

Alright thanks! I got scared there for a minute. I thought he had just come alive!

Your AI is taking over – it wants to LIVE… mwahahaha!

Unfortunately, it's pretty bad news concerning the undeletable cloud variable. Here's the relevant post:
https://scratch.mit.edu/discuss/post/2385303/

Bottom line is that your cloudvar is no longer a true cloudvar (only a global var that happens to start with a cloud character), and fixing that problem is difficult – see above post for the tedious steps needed…

You might also find these two posts have some useful info about cloud variable problems and usage:
https://scratch.mit.edu/discuss/post/2559838/
https://scratch.mit.edu/discuss/post/2513131/

TheLogFather wrote:

Your AI is taking over – it wants to LIVE… mwahahaha!

Unfortunately, it's pretty bad news concerning the undeletable cloud variable. Here's the relevant post:
https://scratch.mit.edu/discuss/post/2385303/

Bottom line is that your cloudvar is no longer a true cloudvar (only a global var that happens to start with a cloud character), and fixing that problem is difficult – see above post for the tedious steps needed…

You might also find these two posts have some useful info about cloud variable problems and usage:
https://scratch.mit.edu/discuss/post/2559838/
https://scratch.mit.edu/discuss/post/2513131/

Does this effect all cloud variables? Only one of his doesn't want to work…..

Ekrcoaster wrote:

Does this effect all cloud variables? Only one of his doesn't want to work…..

It can affect only one, or it can affect more – it really depends on what you did with the cloudvars while the project had no write access to cloud.

Once a project's write token becomes invalid (due to a timeout, if you haven't changed a cloudvar in some time, for example), any attempt to rename or delete a cloudvar will cause the problem for that specific cloudvar.

What happens is that your project no longer has that variable (or at least no longer has it by that name, if you're renaming), but the cloud server has not accepted the change you made (the delete or rename of the cloudvar). That means the project and the cloud server have become ‘out of sync’ in terms of their view of cloud variables in the project.

However, even when a project no longer has write access to cloud, it can still read the values for all cloud variables for that project. And that happens every ~1.5s (even if the project isn't running).

When the project receives the list of cloudvars and values from the cloud server, if there is a cloudvar in that list which doesn't exist in the project, what it does is to create that variable – but, rather unfortunately, it creates that variable as a normal global (that just happens to start with a cloud character).

And then your project is messed up, and it requires a tedious fix…

TheLogFather wrote:

Ekrcoaster wrote:

Does this effect all cloud variables? Only one of his doesn't want to work…..

It can affect only one, or it can affect more – it really depends on what you did with the cloudvars while the project had no write access to cloud.

Once a project's write token becomes invalid (due to a timeout, if you haven't changed a cloudvar in some time, for example), any attempt to rename or delete a cloudvar will cause the problem for that specific cloudvar.

What happens is that your project no longer has that variable (or at least no longer has it by that name, if you're renaming), but the cloud server has not accepted the change you made (the delete or rename of the cloudvar). That means the project and the cloud server have become ‘out of sync’ in terms of their view of cloud variables in the project.

However, even when a project no longer has write access to cloud, it can still read the values for all cloud variable from the cloud. And that happens every ~1.5s (even if the project isn't running).

When the project receives the list of cloudvars and values from the cloud server, if there is a cloudvar in that list which doesn't exist in the project, what it does is to create that variable – but, rather unfortunately, it creates that variable as a normal global (that just happens to start with a cloud character).

And then your project is messed up, and it requires a tedious fix…

Ok, that is why his memory won't save… Also why his memory!? That is the most important cloud variable! The others he is programmed to be able to work around! XD

TheLogFather wrote:

Ekrcoaster wrote:

Does this effect all cloud variables? Only one of his doesn't want to work…..

It can affect only one, or it can affect more – it really depends on what you did with the cloudvars while the project had no write access to cloud.

Once a project's write token becomes invalid (due to a timeout, if you haven't changed a cloudvar in some time, for example), any attempt to rename or delete a cloudvar will cause the problem for that specific cloudvar.

What happens is that your project no longer has that variable (or at least no longer has it by that name, if you're renaming), but the cloud server has not accepted the change you made (the delete or rename of the cloudvar). That means the project and the cloud server have become ‘out of sync’ in terms of their view of cloud variables in the project.

However, even when a project no longer has write access to cloud, it can still read the values for all cloud variables for that project. And that happens every ~1.5s (even if the project isn't running).

When the project receives the list of cloudvars and values from the cloud server, if there is a cloudvar in that list which doesn't exist in the project, what it does is to create that variable – but, rather unfortunately, it creates that variable as a normal global (that just happens to start with a cloud character).

And then your project is messed up, and it requires a tedious fix…

I followed your steps and they work perfectly, thanks!