NEW QUESTION:
CLOUD LISTS??
USERNAME VARIABLE?? (SCRATCH USERNAME)
------------------------------------------------------------------------------------------
The first one is not exactly a concern, but is a suggestion.
1.
Each clone of each sprite is assigned a number
So we can use these blocks:
go to clone (1) of [Sprite2 v] set my clone# to (5) delete clones (1,4,6) set clone (3) of [Sprite5 v] x to [10] set clone (3) of [Sprite5 v] y to [10] think [of the possibilities!]2.
Last edited by Markyparky (2012-05-14 03:05:07)
Offline
First one would be nice.
Second one wouldn't be a problem - it would technically be a new project so it'd have separate variables.
Offline
About the second one, I have news from a source that while they (that person) doesn't know whether it would create a new DB, or just not work, you shouldn't be concerned about cheating in games.
Offline
This has nothing to do with this topic but I will say it anyway. Next there will probably be a scratch 2.1 that will probably be released in 2020. So scratch here is an idea for the next version of scratch MAKE A CHUCK NORRIS BLOCK it will say add chuck Norris and it will attach to the green flag button. Chuck norris will have his own sprite and commandments already programed into him and the commandments will probably be a bunch of punches and kicks and roundhouses. That is my idea for the next scratch 2.1
Offline
facebookyoutube wrote:
This has nothing to do with this topic but I will say it anyway. Next there will probably be a scratch 2.1 that will probably be released in 2020. So scratch here is an idea for the next version of scratch MAKE A CHUCK NORRIS BLOCK it will say add chuck Norris and it will attach to the green flag button. Chuck norris will have his own sprite and commandments already programed into him and the commandments will probably be a bunch of punches and kicks and roundhouses. That is my idea for the next scratch 2.1
That, I guarantee you, will never happen. At all.
Offline
but it would be sooooooooo awsome. OK maybye it is a little out there but still I am wondering what new scratch features will be put on scratch 2.1 in 2020
Offline
facebookyoutube wrote:
but it would be sooooooooo awsome. OK maybye it is a little out there but still I am wondering what new scratch features will be put on scratch 2.1 in 2020
It's not going to be 2020, it's probably going to be 2014. I'm more wondering about what features they're going to put in 2.0.
Last edited by TorbyFork234 (2012-05-10 22:38:20)
Offline
You litterally copied my idea
Offline
Clone IDs would be very useful; i support that.
And once you edit a project, it becomes a new project, so it shouldn't affect the original (unless you're the owner).
Offline
Thanks, scimonster. And also, will there be
(scratch username)
Offline
Markyparky wrote:
Thanks, scimonster. And also, will there be
(scratch username)
IDK. I hope so.
Offline
Clone IDs would be the best
Offline
roijac wrote:
sci, do you know if you can give access to certain part of your db to other users? like your test account etc.?
(or use it to make a chat protocol so anybody can make a client)
Huh?
Offline
From the research ive done tinkering of the scripts cant be saved to that project. so it would not work (second one)
Offline
scimonster wrote:
roijac wrote:
sci, do you know if you can give access to certain part of your db to other users? like your test account etc.?
(or use it to make a chat protocol so anybody can make a client)Huh?
like, if you can choose that the 'chat' cloud list will be shared between users...
Offline
roijac wrote:
scimonster wrote:
roijac wrote:
sci, do you know if you can give access to certain part of your db to other users? like your test account etc.?
(or use it to make a chat protocol so anybody can make a client)Huh?
like, if you can choose that the 'chat' cloud list will be shared between users...
Cloud lists update across all copies of the project.
Offline
scimonster wrote:
roijac wrote:
scimonster wrote:
Huh?like, if you can choose that the 'chat' cloud list will be shared between users...
Cloud lists update across all copies of the project.
What if I don't want people using my cloud variables?
D:
Offline