Official Everybody Edits Forums

Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?

You are not logged in.

#1 Before February 2015

cheezpuffs
Guest

health gauge, damaging obstacles, checkpoints, and life count!

HEALTH GAUGE: it would be cool if we had a health gauge in the top-left corner of the screen, where it slowly increases had you not received any damage for X seconds, you should also be able to turn off this option if you dont want people dying. When people die, they turn pale, cross-eyes, and roll upside down. Plus You can get hurt in a few different ways:

- falling from heights of up to 20 blocks +

DAMAGING OBSTACLES: this relates to the health gauge as where if you touch them, fall into them, go along them, you lose a certain amount of health, further damage either how hard you hit it (like spikes, vertically moving heavyweights, (add more if you like)

CHECKPOINTS: this connects with the health gauge, as when you die, you go back to the most recent checkpoint touched.

LIFE COUNT: when/if you die, you lose a life, (you start out with 5 lives in each world, maximum life count able to be increased via magic coins) going back to the most recent checkpoint touched, but when all of your lives are gone, you go back to the lobby.

here are some i added:

HEALTH PICK-UPS: when touched, you get a certain amount of health increased, these then dissapear until you die.

ALSO: the owner gets FULL CONTROL over all of these, so they can place the pick-ups, hazards, checkpoints and the rest //forums.everybodyedits.com/img/smilies/big_smile

#2 Before February 2015

Different55
Forum Admin
Joined: 2015-02-07
Posts: 16,574

Re: health gauge, damaging obstacles, checkpoints, and life count!

suggested 6 times already.


"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto

Offline

cheezpuffs 1423733143228289

Board footer

Powered by FluxBB

[ Started around 1715111861.2931 - Generated in 0.022 seconds, 10 queries executed - Memory usage: 1.33 MiB (Peak: 1.41 MiB) ]