Beat It

[MessengerOfDreams]

This post by Blablob was thumbed up by: 2

Killswitch (April 6th, 2013, 5:37 am) • MessengerOfDreams (April 6th, 2013, 9:34 am)

[Suyo]

This post by Suyo was thumbed up by:

Killswitch (April 6th, 2013, 9:35 pm)

[ChaosYoshi]

I love how the backround, while simple, looks great,[/repeat] and it doesn't destract me from the gameplay at all, which I've found to be a reoccuring thing with a few of the block-style games I've tested recently.

If there's anything that bugs me, it's the fact that the game pauses automatically when the mouse goes off the game screen. I know you made it so that people don't have to worry in case they accidentally go too far. However, I can't remember how many times I have lost lives because by the time I resumed the game, because the paddle kinda warped a little before going back to my mouse, thus missing the ball that I wanted to hit. I also find it just annoying overall because it breaks the pace.

[Blablob]

I've updated the game. Most of the update includes some subtle changes, but there are some noticeable ones as well.

Maybe rename the label though, to "Combo Multiplier" or something. At first I thought it just influenced which combo value you start off from.

I thought the description should have explained that pretty clearly, but I changed the name so that it makes a little more sense.

If there's anything that bugs me, it's the fact that the game pauses automatically when the mouse goes off the game screen. I know you made it so that people don't have to worry in case they accidentally go too far. However, I can't remember how many times I have lost lives because by the time I resumed the game, because the paddle kinda warped a little before going back to my mouse, thus missing the ball that I wanted to hit. I also find it just annoying overall because it breaks the pace.

I personally found myself losing less often after I added the autopause. But I've added an option for people who don't want to have it.

My framerate is being very jumpy - and since you use a fixed timestep, sometimes the game get really laggy. Try using a variable timestep, which moves objects depending on the time since the last frame, not based on the framerate. There are hardly any downsides to variable timestep, so you should use it wherever possible

I did some research on this and I couldn't figure out how to set it up. There are some other aspects that affect the speed of the squares, but let's pretend for a second that my code is:

public function Main():void
{
addEventListener(Event.ENTER_FRAME, moveSquare);
}

private function moveSquare(e:Event):void
{
square.x -= 5;
}

Then how would I change the code in order to use a variable time step?

[Suyo]

This post by Suyo was thumbed up by:

Blablob (April 7th, 2013, 6:46 am)

[Raz]

I like it. It's fun.

[Killswitch]

Good game. There's like a 75% chance for the game to lag. It's like the game is running fast and slow alternatively; it's a little frustrating.

Good thing you added the "Autopause"; I lost a life when I got moved the cursor outside accidentally.

The Willem Dafoe feature is awesome.

Question: How did you compile this?

[Jellonator]

This post by Jellonator was thumbed up by:

Killswitch (April 13th, 2013, 4:37 am)

[Killswitch]

Question: How did you compile this?

Most likely Flex SDK.

I know it's possible that he compiled it with mxmlc.exe, but I wonder if he didn't use any of these stuff.

[Blablob]

This post by Blablob was thumbed up by:

Killswitch (April 13th, 2013, 4:36 am)