Mechanisms Sharing new (and old) mechanisms

I have some to share (these are all in my album "Frenzies' Original Levels"):

Floating Bot (I don't know who discovered that): You can place a Motor on the bottom of a bot for it to float/fly. To control it (that's the part I discovered), tap when a block is on the same level as the bot's Motor. My motorcycle mechanic actually uses this; the motorcycle weighs the bot down and prevents it from flying. Since its motor is on the ground, the bot is able to move the motorcycle around. Hope you understood it.

Joystick (my version): A Motor is placed on a Slider and the slider is blocked to prevent it from moving. Then, you can place blocks to make a stick and add a Draggable on top. But now it's rotating. So, you put a motor attached to the stick, then more motors attached to THAT motor and so on (basically making the tail thing). Then you surround it with stone blocks. The flexibility of the motors allow the Joystick to move when you want it to, but prevent it from spinning.

I have some more, but they're even harder to explain... let me know if you don't understand it; I'll attach some photos. And be sure to try the levels using those mechanics to see how it works (the Floating Bot is in Spiritual Assault, the Motorcycle is in Motorcycle, the Joystick is in Joystick by Frenzies).

EDIT: Okay, so here's one I found long ago but didn't use it in a level:

Help-me-think-of-a-name: You can put a Zapper or Eye on a Win Block, then attach the Win Block to a motor to make it freely movable. When it's touched, it will automatically activate. The glitch is pretty fragile, though...

Motor overload (or suggest another name): If you put a group of motors attached to each other in various ways, it will bend into itself and go crazy

 

That's not new, though.

 

All of KPACABA's levels are innovative

 

You guys should really consider taking @richardfu 's advice and stick this in the "Level Creation Help" forum when one of you becomes a moderator...

 

Why not now?

And @cpw, you could just make a Joystick stage. What else is there to do with a Joystick?

 

@cpw Weird. But it looks good enough to use in a level. I can just see richardfu using this

PS. Just a suggestion. Could you guys put the images in spoilers, or at least when you're posting multiple images? It's getting hard to scroll through here, and there're still more posts to come.

 

Spoiler

I'm sort of busy right now, so I didn't have time to polish this. It's a motorcycle that accurately goes to the location you tap. I guess this makes my old motorcycle obsolete. The card is in the spoiler.


EDIT: I guess it isn't as stable as I thought it was. If you're trying to go to a far location, don't tap on it directly. Tap in that direction, but on spots near you. It tends to randomly go around if you tap on a location too far

EDIT 2: It also has the properties of the floating bot mechanism (also the one used in my old motorcycle), which richardfu_ found in his level The Eagle, when it slowly glided downwards. So attaching enough bots using this mechanism will enable them to float.

 

@cpw - this is awesome! Yeah, I would have to agree with your theory of why the third block (past the stairs) also works. This possibility is huge news! It means that maybe B's autopilot routine is not mapped to the two-dimensional space within the three-dimensional space, but rather to the entire vertical column for that block space in the original two-dimensions.

I'll explain. Originally I thought that the Climbing exploit allowed him to reach a spot at any level that would still map down to the same spot tapped in the other level. In other words, Each spot he reached would be evaluated against "have I reached the spot tapped if I look down/up from here?" Rather - it seems - the calculation of the end spot is calculated also at the beginning of his autopilot routine and all spots that correspond to the spot tapped in that vertical column are considered acceptable end spots. Then all acceptable spots are mapped to actual blocks. So, since B does not ever actually reach the block mapped to as an acceptable end spot in this demo, he keeps pushing.

Why this is profound is that @Martin Magni may have intentionally known about the potential of the Climbing exploit! Consideration for its possibility surely seems evident from the behaviour in Push-glide.