Anyone know if right now i can do something with this?

I also did already a thing. (That terrain is optional,the idea under the grass is going to be the final map,it's going to be giant,and all the sticks and guys will be seen like this animation [Small])

As well,what engine should i use for make a game like that one?

So... you want to make a game and the only thing you have is a spritesheet? That's a weird way to start a project, you usually have some idea of what to do, not just some assets.

You can use that for some kind of game, I guess. Some of those sprites look like a character animation.

Engine to make "a game like that one"? There's no game in your posts, with that little information you could use any engine and do anything that the engine supports as long as it loads spritesheets.

So... how should the game work? What game mechanics do you want to have?

Sprite sheets like this are laid out in a grid, and accessed using the grid numbers.

Lets say your sprites are 8 x 8 pixels.

To get grid numbers:

You divide the X and Y coordinates by 8, round down

To get the position of the top left pixel:

Multiply the X and Y grid coordinates by 8

To animate, call the appropriate grid coordinates at the desired speed.

If you have never programed before, I would strongly suggest trying much easier game concepts before moving on to more advanced topics.

Have you tried Game Maker? It's a very flexible and powerful tool.

When drawing healthbars, you don't need to manually draw each amount of health. You just draw a full health bar, and an empty health bar, and use some simple programming magic to draw all the different amounts of health inbetween.

Also, you (normally) don't need to draw the entire game map. Usually game maps are composed of smaller elements like tiles or objects that are assembled into a larger map. Sometimes it's done other ways though.

This thread reminds me of this TV commercial:

Oh well the 99% of who responded was serious

Ain't it "easy" already?

So... you want to make a game and the only thing you have is a spritesheet? That's a weird way to start a project, you usually have some idea of what to do, not just some assets.

You can use that for some kind of game, I guess. Some of those sprites look like a character animation.

Engine to make "a game like that one"? There's no game in your posts, with that little information you could use any engine and do anything that the engine supports as long as it loads spritesheets.

So... how should the game work? What game mechanics do you want to have?

Well the game if i can get something from that thing is going to be an "arena" like game where those 4 stick fights,then when there remains one he fights with the brown stick,when the brown stick dies then he becomes that big guy.This is the idea i had when i started everything when i was bored.

Ain't it "easy" already?

Think about it this way: A game is a system of parts which define its function. For any game to exist, every part of the game must be created by someone. Creating just one part might be easy, but there are often thousands of parts required to make a complete game.

Engines are a reusable collection of parts. Someone realized that a lot of games all need the same subset of parts and decided to create those parts in a way that could be reused by multiple projects more easily. But the engine creators don't include parts that only one or two games need - those are up to you to create yourself.

How easy or hard it is depends on how many parts are already provided by the engine vs. those you need to create yourself.

Evaluating the difficulty of writing a game means figuring out what you have to do yourself. This requires knowing exactly what parts you need, and exactly what parts an engine already has. As the game creator, you're responsible for doing research into which engine(s) will minimize the extra work that you need to do. This itself is pretty hard to do; the level of detail you require to accurately evaluate this is greater than the detail provided by the feature summary of most engines. You have to read their API documentation to get a better idea, and even this isn't the complete story. You also need to actually try using the engine - sometimes documentation is out of date or things don't work in specific cases that the engine creator didn't anticipate.

Making a game is only "easy" if someone else has already done the work for you.

Well,i'm not gonig to be alone,but,ain't i'm doing the re-search for what engine i have to use here?
Then i'm going to search other stuff as well