Mysterious Problem

[ProdigyX]

I dont even know how to explain this situation.

Here's the file.

So basically go up the ladder in the middle of the level.

Try to collect all of the blue bubble-like things. The last 4 columns on the right are uncollectable.

Press 1 & 2 to toggle between the display layer, and the layer where every thing happens.

What really bugs me is that if I move the bubble-like things below, or to the first part of the level, they are all collectable. Also at the start of the frame, you place the rainbow colored object name "Lil M'" on top of the 4 columns that are uncollectable, they are collected. Anyone have any idea as to what in the world is going on?

[ProdigyX]

bump

[Shawn]

Your events are really confusing. They seem overly complicated for what's going on in that simple level. There's not enough comments to really get an idea of what you're doing. It just seems there are way too many events to achieve what simple Mario gameplay is going on. I'm not even sure why you need to use the select object extension to accomplish what you're doing, as I don't really see anything that would require an extension.

If you could explain or provide a better commented example, that would help.

Edit: I didn't notice you had global events set up, so that explains why I wasn't seeing certain events to accomplish what was going on. Though that makes it even more confusing because there are even more events to achieve something relatively simple.

If I had to guess, something is going wrong with setting the Alt Value D with the Gear objects since you are comparing those values to determine whether they are destroyed or not when the player collides with them. Though I really don't know why you need to compare a value to determine that. I would think Player collides with Gear, then destroy Gear would be all you need, unless there's an underlying reason.

[ProdigyX]

I mean there isnt much took look at.

Dont look at any of the movements, ignore the Iniv1.5 start of frame stuff, enemies dont have anything to do with the problem,timer isnt a problem either, and neither is Pop-up numbers.

As far as the Select Object Extensoin goes, in which use are you confused about it being used?

Global Events merely set the position of some objects, and spread needed values into other objects

Working on commenting

[Shawn]

I guess I'm having a hard time seeing what you are using the Alt Val D for, and why you need to compare them. More specifically when you are determining the collisions with the player. But yeah if you comment that will help me or anybody else try to figure out the issue.

[ProdigyX]

I use Alt. D so that when the player touches the 2nd instnace of the Gear Detector, MMF2 destroys the 2nd instance of a Gear and not like the 80th or 25th.

Uploaded another one with a few more comments.

If you need me to explain anything else, dont hesitate to ask. You can use the same link as in the first post to get the updated-commented version

[Shawn]

I see. Well, I changed it so instead of testing the player colliding with the gear detector to destroy the gear, just testing the player collision with the gear itself then destroy it. It works the same as what you have without using any alt values, so that was why I was confused why you needed to use the gear detector to determine if the player destroyed a gear.

It didn't make a difference though with the last 4 columns not being destroyed, which has me thoroughly stumped. It's not related to any problems comparing the Alt D value, which was the only thing I could think of.

This was on the first version, I'll download the new one with comments.

[ProdigyX]

Yeah, i have removed all of the events except the Gears group and the Player's Movement and the problem still occurs, so i dont know what could possibly be the problem

[Shawn]

Hmm. Well. I briefly looked over the comments, and from what I saw, none of those should affect the gears not being deleted. It's not the alt value testing, I already tried that one earlier. Everything is on the same layer as the player, I had tested the visibility of the other layers to make sure the last 4 columns were still on the Action layer, though it wouldn't have been possible for them to be created on anything other than layer 2 in the first place. It's for some reason totally ignoring those last collisions and I don't see a reason as to why.

Hopefully some other people will check this out. I'm hesitant to call it a bug, as there's usually an explanation, but I honestly can't find one.

[ProdigyX]

And that is what makes this problem so frustrating!