Actually, to be more specific, I meant being able go from a double-jump to a wall-jump and then do another double-jump after jumping off a wall, if that makes sense to you. You can pretty much do that in the later Mega Man X games with Zero, if I recall.

Also, I just remembered, having a variable to control wall-slide speed (for example, some characters may slide down walls quicker, and you could press down to slide down quicker, like in the Mega Man Zero games).

Well, wasn't expecting to find this. This looks good, though I think the lack of being able to double-jump after wall-jumping is jarring, but I've also got some recommendations:

• Crouching... Erm, I don't think that's really needed in a behaviour. All it really is is mainly just a change in animation and collision and, depending on whether the player can move while doing so, not move or just move slowly. Nothing a couple of variables can't do. Basic as hell.
• As said, being able to double-jump after wall-jumping.
• Multi-jump, up to any number of jumps.
• Being able to adjust the angle and force of a wall-jump (for stuff like Mega Man X-style wall-jumping, for example).
• Ledge-hanging.
• Dashing, and having multiple options for dashing (such as locking movement controls, a timer on the dash duration if desired, etc).

Geez, what's with all the multiplayer votes? It's going to be very difficult to implement, and who knows how good any sort of implementation is going to be. I personally think that should wait.

Modularity and debugging are certainly high on my list, though I do recommend tile map support, which I voted for. Support for the most widely-used tilemapping editors would go a long, long way, and as well, Tiled recently implemented a Terrain tool, which enables easy transitions between types of tiles (water, sand, grass, dirt, stone, etc). As someone who works with tiles, tilemap support would be an absolute godsend.

I'd definitely say tilemaps, debugging and modularity should be done first. Multiplayer can come much, much later.

I thought I wasn't gonna be able to figure something out for the Newgrounds comp, but it turns out I had a bit of an idea. It's yet another Breakout clone, but with the 'endless game' style. So far, there's no music, three power-ups, and the collision's a bit janky, but it's getting there.

Also, the assets are entirely open-source, found on Opengameart.org.

<img src="https://dl.dropboxusercontent.com/u/919275/Block%20Tower%20Breakdown/Screenshot.png" border="0">

Play the game here.

I'll probably upload the full game up onto the arcade later once it's more feature-complete, and update it as I go, and then I'll submit it to Newgrounds once I'm satisfied.

I personally think this behavior would have to be done from the ground-up anyway, so making things more modular in nature would help with bug-testing and the like.

For all we know, this might be on Ashley's to-do list, but in any case...

Basically, the idea behind this is having a platform behavior that incorporates various functions that are either common in platformers or useful to have. Though my main desire is to be able to create a platformer with physics similar to Sonic the Hedgehog (which I have tried and failed miserably multiple times), I want to be able to see the creation of a behavior that covers the needs of as many people trying to make platformers as possible. It's not a 'replacement' for the official platform behaviour, but just an option.

So, with that in mind, potential feature list:

• Controlled variable jumping height
• Allowing collision with non-Solid/Jump-Thru objects (for a variety of reasons)
• Incorporating rotation and momentum mechanics similar to Sonic the Hedgehog
• Wall Jumping, wall climbing, edge hanging, etc.
• 'Realistic' platforming mechanics, ala Flashback or Prince of Persia
• More to come, maybe

Potential features are open to request, and I'd really like to be able to get someone on board to create something like this.

Another update, including a basic saving system allowing the map to be automatically updated once the array is loaded from JSON. Problem is, there's a couple of annoying issues, such as part of the non-explored map appearing properly, same with the contents icons. I'm trying to debug and figure out how to fix them right now, but it's a bit frustrating.

Updated the .capx with a couple of extras:

* Grid visibility is now affected by a couple of variables. For example, some parts of the map may already be revealed in certain circumstances (like data stations in Super Metroid).

* Opening the map pauses the game.

* Tried experimenting with using colour effects. Didn't quite get what I was going for, but, eh.

Edit: More changes!

* Implemented an additional 'layer' of icons for stuff like save rooms, nav rooms, rooms with items, etc.

* Sped up the sine fading on the player icon to make it easier to see stuff behind it.

Alright, I've finally made some progress on this thing. Here's what I've got so far, it's not actually that complex, but it does require families.

Map.Capx

Basically, rather than taking a collision-based approach to it, I've used the player's position as a reference for where it should be on the map and which parts of the map are explored.

It's based around setting up the 'grid' in the level editor first, but in theory it could be set up in reverse in the exact same manner. But I prefer it like this, for now, as it's much easier to plan out and build your layouts in that way, as the map will generate itself accordingly.

It's a bit basic so far, you gotta hold down the 'm' key to show the map, and the map won't update until you reach the top-left corner for some reason, but it's a start.

Edit: Nevermind, found the issue. It's working perfectly. Now, to update the cap with documentation...

I've been wondering about what kind of 'base' resolution is ideal for a widescreen game, actually, especially one with high-quality art assets. It's a bit tricky to figure it out, to say the least.

Sorry to drag up the thread again, but any idea on how to get the example to work with what I'm trying to do? I've got a time system based around the fact that 24 hours is 1440 minutes, and converting those minutes to 24 and 12 hour time accordingly.

https://dl.dropbox.com/u/919275/24%2612HourTime.capx

As well, are there any shader effects that would be useful?

I've tried the example scml with the C2 platformer template, and I've noticed that the scml animation object lags behind the actual player object, which is rather odd. It's specially noticable if you zoom in.