Made by the scratch user 4dragonking

Scratch doesn’t really have a lot of ragdoll games so this project is pretty refreshing. In this project, you control a ragdoll and shoot down an enemy. I love the movement and the way the body parts on the ragdoll move about. I also like how you can shoot a ton of bullets at your enemy.  There is also a neat little feature to change the ragdoll’s colour by clicking on the head. The game is good but I think that there could be a lot more added to it. While starting out the game is pretty fun it gets somewhat tiresome after 20 or so enemies are destoryed. It is a great concept and I think that 4dragonking should continue to add to it.

PROS

+Cool concept

+Fun gameplay

CONS

-Bland visuals

-Repetitive gameplay

-Too easy

How it Could be Better

This is a good concept and a lot could be added to it to make it great. Put in better visuals, more enemies, levels, and more features. This project has a lot of potential.

My Critical Rating 3/5

This is another quality submission by the scratcher Zelda123

This is one of the best star wars projects I have seen on the site. It plays well online and off.The game has 2 parts to it, the first part is a side scrolling game to reach the end of the level and the second part is a battle with the battle droids. The side scrolling part of this game is pretty well done. It doesn’t have a lot of extra things like check points and enemies but the level design is nice and fairly challenging. The droid battle part of the game is pretty fun with nice animations of the droids being destoryed. However, there is one big glitch in this mode and that is when you destroy a droid while it is still falling, it will attack you when it lands. I lost all of my lives because I destroyed the droids while they were falling the first time I played When you finish the second part it ends with a cliffhanger (You will have to play the game to find out what it is ).

PROS

+Challenging gameplay

+Nice visuals

+No major bugs

CONS

-Doesn’t have extra things to make it better (eg checkpoints, extra levels, enemies in part 1)

-Has a minor bug

How it Could be Better

This game is a great start but it would be much better if more was put into it. Add more levels, more level graphics, more enemies, checkpoints, items, and a boss. Then fix all bugs and this game would be perfect.

My Critical Rating 3.5/5

Now, I glanced over at the comments for zelda123′s project that was
on the frontpage. Since people seemed to like it it will be the first
project I write a tutorial for. There were some comments that said that
programming it would be very difficult, but if you understand how it
all works, it is actually pretty easy.

I will explain how to make the game from the ground up and take you through all the steps.

The first thing we will want to do is create the terrain for mario
to move around so just draw the pictures yourself or use tilesets like
the ones from http://www.spriters-resource.com/

A good place for mario terrain graphics is http://www.spriters-resource.com/nintendo/mario/platform/smw/

I recommend just making four different terrains for now. Once you
understand how it works you should be able to do more with your project
but if you don’t just make four terrains. One terrain for the bottom
left corner, one for the bottom right, one for the top left corner, and
one for the top right corner.

When you are done with that we can start to put code on the terrain sprites.

Name the sprite in the bottom left corner terrain0_0. The first zero
represents its horizontal position and the second zero represents its
vertical position.

Now, put this code into the terrain0_0 sprite.

This will make it so that this terrain will scroll. The two zeros
correspond to the zeros in the sprites name. So for the bottom right
terrain sprite you would name it terrain1_0 and have scrollX+(480*1) in
the x space and scrollY+(360*0) in the y space.

Now do the same for the other three terrain sprites and name them
properly. One you have done this you can set the variables displays so
that they display the sliders so that you can easily change the
variables to see what happens.

One you have done this it is time to start programming our player
sprite. But before we can start to put code on our player sprite we
must have four sensor sprites to detect collisions.

It should look something like this when you make the sensor sprites
go to the player sprite. It can vary depending on your sprite shape
though.

Now for the code on the sensor sprites. It is the same code for every sensor sprite.

What this script does is it check to see if it is touching the
colour of the terrain sprites and it sets its private variable named
hitTest to 1 if it touches the colour and 0 if it doesn’t.

Now, we can put code on to our player sprite. Put the code in the picture below into your player sprite.

Here is the breakdown of the code.

if (hitTest of rightHitTest=1){

//if the sensor says that there is a wall on the right side scroll left

change scrollX by 10}

else{

if (Key right arrow pressed){

//if there is no wall on the right side and the right key is down scroll right

change scrollX by -10

point in direction -90

}

}

You do basically the same thing for the left side.

if (touching colour green){

//if we are touching the ground make sure the player stops falling

set yVelocity to 1

if (up arrow pressed){

//if the player is touching the ground and is pressing the jump key then jump

set yVelocity to 15

}

}

if (hitTest of topHitTest=1){

//if you hit the ceiling move down and start falling

set yVelocity to -3

change scrollY by 3

}

if (hitTest of bottomhitTest= 1){

//if player is stuck in the ground move him out of the ground

change scrollY by -5

}

//this makes you fall down

change yVelocity by -1

//make it so that the yVelocity variable scrolls the terrain

change scrollY by (yVelocity*-1)

At this point you should have a properly working mario scroller.

If you want your characters to display animations when they move
take a look at the code in this project:
http://scratch.mit.edu/projects/archmage/291819

For an example of how this project should look when it is done go to.

http://scratch.mit.edu/projects/archblogger/312838