That metanight looks pretty sweet.

edit Fixed that freezing bug, and got collisions working with clones. Only have to fix hitboxes and see if I didn't break multi.

Falco Climbers!

Any luck anyone on an opponent AI? I don't know one thing on coding, so I hope one of you guys are able to achieve it.
[...]
Also, if anyone can, please work on an opponent AI.

An AI is not easy at all to do especially a smart one. So if I do an AI, it would be ridiculously easy to beat. So I agree with you, if anyone has experience with AI, they should try their hand at writing one for SSBO. If they need help, I can help them understand how the whole program works but I certainly can't write a smart AI.

Is there a way to have one person controlling one character on one calculator and one on the other and play each other in the same game?

Yes. I should probably give more details about this in the readme and update the first post but that's already implemented.
Launch the game on both calculators, then have one calc go in the "Multi" menu, wait for a second or two, have the second calc go in the "Multi" menu and you should both see the character selection menu. Remember about the first step. Both calcs must have lanuched the game before the first one goes in the "Multi" menu.
If that doesn't work, quit (press Clear) and try again.

Oh and also new characters. That would be so awesome!

Just on the previous page, you can see a Meta Knight flying around (also mentionned on top of the current page).

heck yes puffballs ftw!

Glad to see progress. I hope those hitboxes will be fixed soon.

This looks like it's coming along really nicely. But one thing has always bothered me slightly... the appearance of character sprites when scaled down. Loss of detail is of course unavoidable, but when lots of pixels are lost at smaller sizes, it can be hard just to recognize the character. Have you considered a mipmap-like system for which each sprite has a few scaled down versions as well? This would of course mean that every sprite needs more artwork done and will take up more space, but the graphical improvement may be worth it.

Thanks all ^^

I'm planning on making a character if I have time.

Well for now, you can only sprite your character since tutorials are not done (and the engine is not done either and might be subject to changes). Be sure to have your sprites sized correctly compared to the already existing characters

I think that jigglypuffs jump should be higher and I agree about it being a little less floaty.

Yeah, I put some random constants as usual
I'll change that later. For now, let's have fun with that magic bubble

But one thing has always bothered me slightly... the appearance of character sprites when scaled down. [...]

Yeah, I know it's ugly.
And while your idea seems acceptable, it would probably be undoable. Fox is already 4KB large. MetaKnight is already 5KB large even though he has less moves than Fox. And I need to fit in RAM both characters and one map to run the game. This will be worse when items will come or when more than 2 players will be able to play. So I really have to save RAM

Anyways, UPDATE !

Will the characters be included in the next release?

Notice that the zip is no longer called "SuperStarFoxOpen"

Now for real changes since last update:
-doubly linked list instead of table for object creation/deletion
-added falco's blaster (doesn't do damages but still fires)
-added falco's clone (for testing purposes, will not be in final version so have fun while you can )
-moved menu sprites into appvar (be sure to update SSBODATA !)
-limited horizontal airspeed if in a state where we can control speed (probably too restrictive but at least enough)
-added halfpivot for Jigglypuff and MetaKnight's air jumps, and also for regular groundjumps (allows you to dash and jump backwards)
-hitboxes did not want to work so I reverted them back to a state where they worked with a bit of precision loss

Note: I don't know if Multi still works, I don't have two calcs with me at the moment -.-

Download at the same place

Have you considered hard-coding the movement into the app, using variables in the appvar to control specific speeds and friction? (or is this even possible?)

Could you also put in a debug-like hitbox view option? Just black rectangles wherever hitboxes are?