), True Movement (movement type / speed / tile collision / object collision), Stationary/Mobile spellballs and meteors, Linked/Linkback, Using in-game textures by searching through the folder, an ever-expanding number of new glitches (also in RTW yw ;p) and discovering WA compression can be used to obscure malware... 
[DW that's not actually that big an issue lol.] One thing that's helped us play around with these is the ability to more easily experiment with these variables, largely thanks to MNIK's editor, which allows you to play with several variables. However, there is one unassuming variable that does a surprising amount of work - something I only discovered myself just yesterday, on accident, but something which MNIK and a couple individuals looking through the code themselves (shoutout to Kyuu who I also ignored xD) had previously known about. That variable is ButtonPush.
So, what does ButtonPush do? Well, it covers a few things. It tells whether an object:
- Can interact with (i.e. press) buttons. This is all I assumed it did until recently.
- Can interact with (i.e. activate/use) transporters
- Sinks collapse bridges / Rainbow Floats when going over them or not
- Interacts with springs and suction tubes
Put simply, when this value is set to 0, it does none of these things; when set to 1, it does all of them.
----------------------------------------------------------------------------------------------------------------------------------------------------------
So, all of these are actually really interesting as-is. Thanks to CMD 4 (yes, that one again), you can change the ButtonPush properties of anything at any time. This means you can even set the player to not interact with objects, or... yes, you can make spell balls and even zapbot lasers activate transporters, sink bridges, and even press buttons (a constant zapbot laser actually holds down round buttons
). Floing bubbles can also press buttons, but they have to move off a bridge to actually sink it, and trap transporters, so they don't exactly activate them.However, there are a few limits to this godly ability. For instance, grow flowers don't seem to interact at all (possibly due to their wall-like status; I have not tested ice flowers but I imagine much the same is true for them). Another example: spellballs (but afaict not lasers, although maybe they just move too fast) stop as soon as they activate a transporter.
One thing that is not affected by ButtonPush is interactions with ice and ice floats. I'm still not sure what causes this, actually, but regardless of buttonpush status, an object will slide on ice and deactivate brr pads i.e. ice floats. The only exceptions to this are z-bots (including retro z-bots, weebots, ufos and zapbots; NOT moobots, NPCs unknown), for which don't do any of these things. This is tied to their logic, and no other variable.
----------------------------------------------------------------------------------------------------------------------------------------------------------
This is all well and good, but I'm only just getting started: there is a plethora of other things you can do with buttonpush. Take a look at this last use for it:
- Interacts with springs and suction tubes
This is actually immensely powerful. So, yes, you absolutely can make it so objects do not get affected by springs or suction tubes in the slightest. However, there's a potentially even more powerful use for this: making objects that should not be affected by springs interact with them.
Alright, so, there's a caveat to this. With few exceptions (such as coins... and not much else xD), objects that are sprung will just... explode.
This allows you to delete specific objects (like teleporters, buttons, magic, etc.), but it doesn't do a whole lot for you. At least, not in most circumstances.However, if the tile that the object is being sprung into is a water OR lava tile? Well, for some reason, those two tile logics specifically act different... and are a lot more interesting
So, objects that are sprung into water or lava will actually act like any other object sprung. And guess what: this applies to virtually everything. You can push custom models (set to deadly and moving, in fact), particle effects, spell castors, magic mirrors and arcade machines, decorations, voids, teleporters, buttons, bridges, waterfalls, and - yes, even other springs and suction tubes. You name it, it works! There are a few exceptions: some things break a little. Signs seem to completely break down. Voids are a bit finicky. Sunspheres do leave behind their inside bubble (although you can turn that off separately if you wished). But beyond that? ... Most things work
Floinged objects also seem to be properly trapped in time; however, floing bubbles themselves work just fine There are a few other really niche quirks. Objects that change tile logic in some way, such as gates, bridges, transporters, teleporters, etc. leave behind a meta tile where they were pushed from. Usually it's a floor tile, although closed gates leave behind a wall, and brr pads leave behind ice. Some objects also leave behind a whole trail of tile logic along their flight path, including gates (making walls), rainbow floats (making floors; this is not the case for normal bridges), cages (floors) and signs (walls). Suction tubes without modified z-adjust (Z not affected) leave behind walls either side of their flight path. Active Flip bridges also leave behind floor tiles where their extensions were. Active bridges also This isn't too big an issue if the object starts on a floor or wall tile, or inaccessible area.
Another quirk is that objects cannot be walked on. At least, not most of them... at least not right away
So, you can still interact with them using buttons or, for poppable objects - pop. Transporters, I believe, will be in an active state, as well as non-tile-logic objects like springs and suction tubes. Objects that leave behind a trail of metatiles also remain active. Other objects will have to be activated, or deactivated and reactivated, in order to be walked on / interacted with. Teleporters can still be exited (i.e. from another teleporter), effectively creating a one-way teleporter.Objects also are sprung whether they are activated or not, interestingly enough. Objects can continue to be sprung around in this inactive state and not create any further floor metatiles; however, objects reactivated or otherwise not deactivated will leave behind further metatiles. Objects may also be activated mid-flight, creating a metatile in their fully active state. This applies to teleporters and bridges (including alternating ones).
Transporters, once activated, will move in their pointed direction (at flying speeds) until they hit the end of their path, before continuing down the direction they were originally sent in. This will also create a metatile in the spot where they first activated. Flip bridges will remain water/lava tiles, however their extended components will function as expended. (Activated flip bridges will fly straight through small paths and still appear active.) Conveyorbelts and their tails can stack; once the head activates, the conveyorbelt will actually "fix" itself.
Objects also block other objects, as long as they are in a normal condition. If they're sprung and not updated, they can fly into other objects. This allows you to actually stack objects, including multiple floing bubbles.
A really weird interaction is how spellballs and lasers (which are actually super-fast pow charges - just shoot a laser through a prism and save/load to repeatedly see this
) will activate springs and suction tubes, but won't actually move at all with them... well, sort-of. Actually, if a spring rotates into a pop charge with buttonpush on that pressed its button to rotate, it'll hit the button twice. Another weird thing that happens is spells that hit springs or suction tubes function as if they have buttonpush off - with the exception that they will still interact with springs and suction tubes. (Sidenote: with "teleportable" on, this is also true for teleporters, for which you can deactivate them with bubbles or magic but nothing more.) Lastly, even though they can fly through a spring facing a wall or water tile unscathed, they actually do die if the spring is facing a wall, making a magic barrier (although, there are more subtle and effective ways of handling this).I think this is the extent of my personal findings, but if anyone wants to experiment and see if they can find out more, I fully encourage it! There are plenty of interesting use cases that I probably haven't even thought of yet! But other than that, if you find any other interesting use cases, or have any questions as to how something in particular works, feel free to ask away in this thread: that's what it's made for.
I hope to see more puzzles using this quirk in addition to the plethora of other findings. Have fun!
