I CAN SING MY SWORD SWORD, I CAN SWING MY SWORD SWORD! THE DOCTORPROFESSOR IS OUT!

The reviving doesn't actually work. I tried it. The DoctorProfessor is out!

Really cool game, but i feel kinda lonely playing a two player game by my self, maybe an option to just be one player? Hehe I ran around and collected zombies in a big pile until the game lagged very much, then I struck 601 zombies in one blow :)

Sure thing, I could implement single player. I might even experiment a bit with AI for the second player. I think it's safe to say you have the record for the highest combo. :P

That was a quick update! This game is really nice. Maybe you should add some small randomness to the zombie walk, cause I find that the easiest way to actually survive is to not enage in combat, but just run around and avoid them which is easy since they're quite slow and predictable, Maybe add like a sudden spurt when they get really close, to get the impression that they "jump in" to bite you :D That will atleast ruin my tactic

Well, I haven't added randomness to the zombie walk, but I added in lunging (sudden spurts of speed when they get close), and it seems to be just what this game needed! Thanks for the suggestion, it turned out great!

Oops, accidentally released an update to try and fix a browser problem :P Check the previous update that I uploaded today! It's got lots of cool stuff!

In the last update I said that Player 2's item button was changed to "L". That was incorrect. Player 2's special attack button was changed to "L".

Idea for a game, try something out of your element. maybe a strategy trading game that focuses on trading resources that fluctuate in price. Or maybe a city builder? like an 8-Bit Sim-City (top view ofcourse) where you manage resources :D Hope this helped somewhat, and for some reason i cant play this game, my java security settings is down and its just some games i can play :/ Could you send me the jar? my email is myran168@gmail.com Thanks, Ryan

They all sound like great ideas TehRyan, but unfortunately I don't have time for a big project like that at the moment because I'm busy making the art for someone else's game right now.

The game is quite fun, very well made and i really enjoy the art! art is a big part of a game, and im sure the person your doing the art for appreciates it!

One minor thing is that while moving up/down/left/right he moves slower than he does when he moves diagonal. For example, if he is moving 7 cells per act cycle when going up/down/right/left, while going diagonal he would be moving 7 cells in each direction, ending up with him moving approximately 10 cells diagonal, (the square root of 98 to be exact). Just something to think about if you really want to fine tune your game. Sorry I nitpick, it just bothers me :)

@dan11, how would you go about fine tuning the game in this situation? (not that I need to know, myself -- but for others, and for K_wow). To clarify: when simplified by moving one pixel at a time, you can move left, right, up, or down, at a speed of one pixel per move; but, when moving diagonally, you cannot. Then, you must move by multiples of the square root of 2. That is the distance between two diagonally adjacent pixels.

In my games that are 8-directional, I usually import the provided SmoothMover class and move Math.sqrt((speed*speed)/2) in two directions. For a speed of two, for example, that would be the square root of two in two different directions to move two pixels diagonally, as (sqrt 2)^2 + (sqrt 2)^2 = 2^2, (Pythagorean theorem, the two bases (x,y) must be sqrt 2 to make the hypotenuse 2, the hypotenuse being the the diagonal distance moved). Sqrt 2 is a decimal number, so one must use SmoothMover or a similar system to track movement. Speed of 3 would be sqrt 4.5 in two directions (sqrt 4.5)^2 +(sqrt 4.5)^2 = 3^2 Speed of 4 would be sqrt 8 in two directions (sqrt 8)^2 +(sqrt 8)^2 = 4^2 And so on... For games that require 360 degree movement, I would use trigonometry. Sorry if my explanation is not too clear

Yeah, I am aware of this issue, but I never really thought it was major enough to remake the entire movement code to fix. I'm not sure if I'll ever get around to fixing it, to be honest. Sorry :(

Yes, in order to move diagonally the same distance as one pixel distance horizontally or vertically, you must multiply the distance by one half the square root of two, or approximately 0.7071; because that value squared is two-fourths, or one-half, and two halves is a whole. I do not know why you would complicate it by moving speed inside the square root function and squaring it when you can just leave it outside. That is, instead of 'Math.sqrt((speed*speed)/2)', you can just use 'speed*Math.sqrt(1/2)' or 'speed*Math.sqrt(2)/2'.

@K_wow, see my last post. Another way of writing it could be 'speed/Math.sqrt(2)' (dividing, not multiplying).

Yes, I just put it as Math.sqrt((speed*speed)/2) to show a thought process. Speed*speed is c^2 in the Pythagorean Theorem, half of that is a^2 or b^2, and the square root of that is a or b, (only if the right triangle is isosceles of course). Any of the ways @danpost listed look neater and are more simplified; again, I only wrote it as I did to show a thought process. Again, sorry if I am making things more confusing.

Oh, yeah. I mean 2 times the square root of two is not the same as the square root of four, but that's irrelevant. Even so, fixing diagonal movement is still pretty low on my priorities list right now.