Plenty of people do this. The trick is that you don't reset variables when you click the green flag. Take a look at Colkadome's games; there's plenty with continue options. When I say continue, I mean that there's a feature that lets you go to where you got up to.
The problem is that you have to download to save your progress. Sure, you can click the green flag online, but it won't save when you leave the page. Or refresh the page; that'll reset the game also.
Anyway, how would the Scratch Team make the blocks?
Offline
leon0 wrote:
in the next scratch why dont you mack a save and a lode blok
that way you can play games and be abelt to stop playing then play wher you wher up to that wood be convent.
you spelt load and block wrong lol but good idea
Last edited by dav09 (2009-08-15 09:04:30)
Offline
The-Whiz wrote:
Adding cookies?
Maybe... but would it lag the Scratch website? What I mean by this is that there are hundreds of thousands of projects on the Scratch website; if there were cookies for every project (not every project would need them, but it wouldn't be able to sense which ones), wouldn't it lag the Scratch website?
Offline
leon0 wrote:
thats true you can do that but how will you redem your ponits and all the over stuf?
What point thing? If you're talking about cookies, it wouldn't be that hard; people use cookies all the time.
Offline
Jonathanpb wrote:
The-Whiz wrote:
Adding cookies?
Maybe... but would it lag the Scratch website? What I mean by this is that there are hundreds of thousands of projects on the Scratch website; if there were cookies for every project (not every project would need them, but it wouldn't be able to sense which ones), wouldn't it lag the Scratch website?
Why would it affect the website? Cookies are stored by the user's web browser.
Offline
leon0 wrote:
JSO wrote:
The best way to do a save/load in scratch is by using a level code, I think. Level codes work online too.
whats a level code? ?
+_+
you type in a code and if it's correct you go to that level
Offline
Ok... How to do it.
Make a list with all your level codes in it, named 'level codes'. Just make them random. The list should have as many items as you have levels. Item 1 of the list is the level code for level 1, 2 for 2 etc.
This is a script you could use:
When the user entered a correct level code, "start level" is broadcasted and the level number is in the variable "level"
(tell me when this has bugs in it )
JSO
Last edited by JSO (2009-08-16 05:44:43)
Offline
JSO wrote:
Ok... How to do it.
Make a list with all your level codes in it, named 'level codes'. Just make them random. The list should have as many items as you have levels. Item 1 of the list is the level code for level 1, 2 for 2 etc.
This is a script you could use:
http://img29.imageshack.us/img29/7350/levelscript.gif
When the user entered a correct level code, "start level" is broadcasted and the level number is in the variable "level"
(tell me when this has bugs in it )
JSO
Q1.how wood(( <-> )) level code work becurs level code never ((1 <-> ?
Q2.how did you get a list block?
Offline
Jonathanpb wrote:
The-Whiz wrote:
Adding cookies?
Maybe... but would it lag the Scratch website? What I mean by this is that there are hundreds of thousands of projects on the Scratch website; if there were cookies for every project (not every project would need them, but it wouldn't be able to sense which ones), wouldn't it lag the Scratch website?
Well you could select [_] Use cookies? when you upload it if they give that as an option...
Offline
The-Whiz wrote:
Adding cookies?
Cookies would be the best thing.
such as:
<when green flag clicked> <if><( cookie <=> yes/1 )> (whatevers supposed to happen) <else> (Start game)
Last edited by markyparky56 (2009-08-17 09:53:33)
Offline
Cookies for Scratch can be very similar to lists. Sample blocks for cookies in Scratch:
<cookie contains [ ] ?>
<cookie is [ older/newer ] than ( ) hours ?>
(element ( ) of cookie)
(length of cookie)
(cookie)
{Add ( ) to cookie}
{Replace element ( ) of cookie with [ ]}
{Delete whole cookie}
{Delete ( ) of cookie}
{Create cookie}
Legend = < > - Boolean (diamond-shaped block)
( ) - Variable
{ } - Procedural block
Offline
leon0 wrote:
sory
dosnt matter jenuine mistake but good i dea
Offline
filo5 wrote:
Cookies for Scratch can be very similar to lists. Sample blocks for cookies in Scratch:
<cookie contains [ ] ?>
<cookie is [ older/newer ] than ( ) hours ?>
(element ( ) of cookie)
(length of cookie)
(cookie)
{Add ( ) to cookie}
{Replace element ( ) of cookie with [ ]}
{Delete whole cookie}
{Delete ( ) of cookie}
{Create cookie}
Legend = < > - Boolean (diamond-shaped block)
( ) - Variable
{ } - Procedural block
like the idea
Offline
you would need internet acess for it though wouldn't you? (Cookies) To be able to recognise an IP adress... then you run into the internet block, Scratch would need protection from viruses and the like...
Offline