Scratch

Well, if it helps, the Red Alert Collaboration project I've been working on has scroll x and scroll y, and a 15 by 11 screen map. All that terrain has is one script, and that's to keep it in place, that should help. Don't mess with the scripts while the project is running though, or it will be extremely slow.

... Is anyone else going to reply? ...

amcerbu wrote:

If you're up for a challenge (or you want to use a platformer base that's already made) you could check out array-based platforming.  Music Marathon (a collab between applejack, Hardmath123, and myself) doesn't actually use the "touching?" block at all.  Hopefully that'll help.  You can remix and change the sprites and levels if you want.

Wow, I was going to reply saying that I was up for any challenge, then I downloaded it and looked at your scripts. That is the most complex scripting I have ever seen on scratch, but boy does it work well!! You did an amazing job on that...
Anyways, I sadly can't use that because my platformer is going to be a different type. I REALLY appreciate it though! I'll just let it out and tell you that it will be a lot like doodle jump (and iphone/itouch/ipad game). But when I get a bit better at scripting and start incorperating hard math (not hardmath123, lol) into my games.

The problem is is that I am going to have tons of animations playing while the character is moving, and I can't use color sensing first cause it messes up in flash and cause its gonna be all black (besides the background).

I feel like I can trust you in just telling me ways of doing that, you don't need to find a project if you don't know of one like this. Again, I really appreciate you helping me. 

amcerbu wrote:

[mega-post time]

Wow, it sure was!

amcerbu wrote:

I think it would be entertaining if the game were infinite, and grew gradually more difficult.  If this were the case, you would need to dynamically add to the level, while also deleting platforms below the player by a certain amount (so that falling would reveal a chasm).

Yah, I'm planning to do stuff like that, like increasing the chance of breaking/fake platforms, making the platforms smaller, etc.

amcerbu wrote:

We want to store a collection of platforms.  Presumably, they're all the same size, although we could add support for large and small, as well as springy, disappearing, fake, etc.  So, we set up a minimal data structure called a Parallel Array.  This allows us to store multiple pieces of data about each platform.  Each element of each list will represent one platform; we have one list for the platform's y-position, one for its x-position, one for whether the player can jump on it (as discussed above), one for its type, another for its size, etc.  You can have as many as you need (or just one, if all the platforms are the same type and the same size). 

We delete items at the beginning of the arrays when we want to get rid of old platforms, and we add items at the end of the arrays when we want to generate more.  We always add and remove items from all the arrays at once; this keeps our "table" of values level.  We know that there is a platform at ((item 4 of xPositions), (item 4 of yPositions)), and that that platform has a type of (item 4 of Types), and we know that the player either may or may not have cleared the platform based on (item 4 of CanJump?). 

When we add new platforms, we can set their y-positions to the y position of the last platform plus a random amount, up to a maximum.  As that maximum increases, the game becomes more difficult.  Here's an example in Scratchblocks.

set [MinY v] to (5) // Keep platforms at least 5 pixels above one another.
set [MaxY v] to (20) // Don't allow them to be too far apart.  

when I receive [NewPlatform v]
add ((item (last v) of [YPositions v]) + (pick random (MinY) to (MaxY))) to [YPositions v]
delete (1 v) of [YPositions v]
add (pick random (MinX) to (MaxX)) to [XPositions v]
delete (1 v) of [XPositions v]

OK... I think I understand what your saying about it... I could do it like this..

set [Platform1] to [45.120.80.3]

amcerbu wrote:

So that's platform generation, sort of. 

Now, as for the physics, we'll say that the item in the list of x-positions represents the center of the platform, and that the item in the list of Sizes (or, if all platforms are the same, the Size variable) represents half the width.  Adding or subtracting the width to the x-coordinate will give the left or right bound of the platform.  The player is touching the platform if

<([abs v] of ((item (i) of [XPositions v]) - ([x position v] of [Player v]))) < ((item (i) of [Sizes v]) + ([Radius v] of [Player v]))>

Where Radius equals the radius of the bounding circle of the player.  The character doesn't have to be circular, but if we imagine he is, everything is easier. 

That's all for now, I'll get back later and finish this post up.

Okay. I get this part too. 

Thanks for the examples, a TON!!! Its been a big help in my game... I hope.. 

amcerbu wrote:

Is that enough information for now?  If you have questions about specifics, I'd be happy to help out with that as needed.  I'm also planning to make a very simple y-scrolling 1s1s Doodle-Jump-style game on my test account.  When I finish that, I'll post a link.

Yes, I think that's enough for now.    Thanks! I'll check out your project when you post it!

Okay, I made most of it but I'm stuck on one part that should be soo simple. I already ripped out all of my hair and thrown myself out of a window, and I'm about to release a swarm of nukes to blow up the world, so someone had better help before I do that.

I'll have a link up in a few minutes in my next post...

Okay here it is, sorry I took forever to post, but I needed to go to bed cause it was past 1 in the morning. 
Anyways, what I'm trying to do is make it so when the sensor sprite lands on any of the board sprites, it aligns exactly to it so he doesn't land weird. I obviously failed in it, cause every time I try doing that, he ends up going through the platform or some other crazy thing. Could you help me with that amcerbu? I know your an excellent programmer, so it shouldn't be too hard for you. I'll be sure to put you in the credits for special thanks to. 

Here's the project: http://scratch.mit.edu/projects/LEGOengineer261TEST/2641516

You know that using color sensing won't mess up what ever color you want your sprite to be? It switches to the sensing sprite so fast that you don't see it change.

Did you manage to fix the bugs?