NOTHING will work!!!!! Everything on it's glitchy!

[madeleine]

thanks do you have any idea what could have been wrong with the brickbreaker one? the condition was "ball/exits screen/create ball from (x,y)" (I don't rememer what the coordinates where) but even thought the ball didn't exit the screen new ones were created. I tried "y posiiton of ball=(a few less than the height of the screen)/create ball from (x,y)" but that didn't work either. The rest of the game was perfect but i never got the balls to work right.

[LB]

Well, you must know that MMF2's coordiante system (and pretty much everything else computer-based) has it's origin in the top-left corner of the screen, and not the bottom left like a graph. Y coordinates increase going down the screen, and decrease going up the screen. X is still normal, of course.

Also, you may want to sue the condition Ball is Outside the Play area instead.

[madeleine]

I can't remember exactly what it was but if the height was 300 I set the condition as "when it passed 299" or something. On the "when exits the screen" condition does it have to leave the screen or just get close? On mine it thought it was leaving the screen when it was in the middle.

[LB]

Was your screen only 300 pixles high? Normally MMF2 starts with it being 480 pixles high.

There is also an expression, Frame Width and Frame Height, that you can type that in and it will always be the height/width of the frame. It is an expression from under th Frame object in the expression editor.

[madeleine]

No that's just a random example because i don't remember how tall I made it. I was just trying to say that the condition was the height of the frame minus a few.

[Jacob]

It depends where your hotspots are in the image as to when the condition will occur. These are all user errors, and not the program's fault.

[Na]

Yeah, that happened to me once. But all the fun in MMF2 comes from messing around with stuff and seeing what works. Its like the game making is a game in itself, like Warioware DIY.

[00J]

go back over your code, nothing is going to get created unless you made it happen yourself.

When you start an MMF app there is absolutely nothing there, no events, no artwork, no variables nada, everything is set to zero...

Trust me, you need to go back over your code, comment things and double check your coding, it happens to the best designers.

I can say i don't have objects creating themselves, a project i'm working on has 973 event conditions not including all the encapulated behaviors inside active objects, and it all relies and works on about 934 different active objects, lots of them created controlled and deleted as needed during the games running processes.

The game also allows the user to create and save a custom designed character to their computer/games location and load it back in during another play session...

So a simple bat and ball game, yeah you've obviously made some mistakes along the way somewhere in there.

Oh and MMF 2 makes all this happen over and over without a hiccup...