It looks pretty but..

Quote from: parserp on August 09, 2012, 03:07:51 pm

Currently it is 8000 bytes

I think you should optimize it a bit. O_o

yes of course, but that probably won't happen for a little while longer...

Alright, I ripped off tag/portalx a lot (charector, boxes, switches), BUT, this in many other cases is quite an original game. It is 2D, non-scrolling, with pickup-able objects (boxes, guns, tramps), doors/switches, and *possibly* a level editor. I call it Axio Man! (a play off of axiom/axe)
Screenshot:



Here's the stuff that is implemented/working:

-Player movement (with physics )
-Blocks of ice (careful, they are slippery!)
-Spikes w/ collision detection
-Pickup-able objects (Tramps, Boxes, Guns)
-Doors/switches
-Exit portal (in the top right corner in the screenie- it does not exit you yet)

Stuff that is going to be coded next:

-3 types of enemies (all do different stuff)
-Make the gun shoot
-Squashers (spikey things that come up, then go down on you (think super mario world))

...And that's all. Here's a download (includes the level from the screenie), you may want to know the controls:

2nd- Jump
Alpha- Pick up/put down boxes
Left/Right arrow keys- move
Up (While releasing a box)- throw the box up into the air
Clear- Quit

Currently it is 8000 bytes, running at 6Mhz with a pause 40, so hopefully I won't have to restrict it to 15Mhz calcs only.

So, DJ_O, will there one day ba a highscore of top rated posts?

lol, that list would include the first post in this topic and the rest from axe updates.

Here's usually what I do:

-It helps a lot (for me at least) to play a lot of games beforehand and take the best ideas/concepts and twist them in a way that will work together for a game
-Usually the tilemapper comes next, as well as a test level to screw around in
-Then comes the basic layout of a player movement engine, just enough to jump, move, and do other basic stuff
-Then I usually code objects (if there are any), perfecting player's physics/movement, and add basic movements of AI (assuming there is any)
-Collisions (this can take a long while if you have complicated stuff)
-Any other jibber-jabber that you haven't coded yet that is vital to the playing of the game
-In game menus, level editor (provided you want to have one)
-Main Menu, other menus
-Levels (evidently this is probably the longest part)
-Putting it all together so all the stuff runs smoothly together
-Saving/Loading

...and that's about it. It may seem like a short list, but in all reality, for a good game at least, takes a good portion of time.

Another idea would be to display a % rating below each ones, so for example if out of 1059 ratings someone got 895 positive ones, it shows a score of 85%.

I like this idea.

Maybe we should avoid displaying a red and green bar like on Youtube, though, otherwise some people will bring up rather spammish Youtube memes such as Quigibo's dislike bar being the same size as Justin Bieber penis and Njaddison having a lightsaber.

3173: You are thinking of compiling it into a giant list.

Sounds WAY too logical to me.