Chat
Discord
10-03-2009, 05:42 PM
Just found a bug. (why do I always find bugs in my own codes just after I released them)
When the no highscore bug is reproduced an error will occour.
Solution:
Replace the code in game flow's alarm 0 with this:
Then delete all meteors player collision event and place their alarm 0 actions in game flows alarm1(you need to create one).
And in game flows step event add this:
Also in ships collision with the meteors delete the destroy game flow action.
When the no highscore bug is reproduced an error will occour.
Solution:
Replace the code in game flow's alarm 0 with this:
|
GML-Code:
if instance_exists(0){ var xx,yy,control; control = true while(control){ xx = random(room_width) yy = random(room_height) switch(floor(random(4))){ case 0: if point_distance(xx,yy,(0).x,(0).y)>120{ instance_create(x,y,1) control = false } break case 1: if point_distance(xx,yy,(0).x,(0).y)>120{ instance_create(x,y,1) control = false } break case 2: if point_distance(xx,yy,(0).x,(0).y)>120{ instance_create(x,y,4) control = false } break case 3: if point_distance(xx,yy,(0).x,(0).y)>120{ instance_create(x,y,5) control = false } break } } alarm[0] = 300 } |
Then delete all meteors player collision event and place their alarm 0 actions in game flows alarm1(you need to create one).
And in game flows step event add this:
|
GML-Code:
if instance_exists(0) = false{ if alarm[1] = -1{ alarm[1] = 30 } } |
Also in ships collision with the meteors delete the destroy game flow action.
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.