Reply to Re: And this one doesnt work either...
If you don't have an account, just leave the password field blank.
The thing with the similar variable names was one of the fixes for v1.08 if I remember correctly. So it shouldn't cause problems anymore. Besides if that were a problem it would still create the rock. It would assign the spritenumber to the wrong variable, but the rock would still be created. In fact if you're not going to do anything to with the rock after placing it you could replace:
int &rock = create_sprite(549, 39, 0, 95, 7);
int &rocky = create_sprite(446, 353, 0, 95, 7);
with:
create_sprite(549, 39, 0, 95, 7);
create_sprite(446, 353, 0, 95, 7);
So something I can't explain is happening here. Doing a wait(1); command like scratcher said might be the best idea.
The second idea I have is to place the preload_seq(95); before creating the sprites instead of after creating them...
Oh, and I second the 'Huh?' comment...
int &rock = create_sprite(549, 39, 0, 95, 7);
int &rocky = create_sprite(446, 353, 0, 95, 7);
with:
create_sprite(549, 39, 0, 95, 7);
create_sprite(446, 353, 0, 95, 7);
So something I can't explain is happening here. Doing a wait(1); command like scratcher said might be the best idea.
The second idea I have is to place the preload_seq(95); before creating the sprites instead of after creating them...
Oh, and I second the 'Huh?' comment...
