I'm a little sad that the baba custom level thing died so quick. You never even finished the official levels that show off the new mechanics.

oh my god the baba dream is alive again

Demoncrawl multiplayer would be cool to see

@@godlyvex5543 It's because the new mechanics were just not that interesting

@@darianfelice5353 it's a dream but I wish Tyler played metatatext (a levelpack based off metatext)

There's actually a mod being developed that is implementing custom hub worlds as a mod off the basegame, curious to see how that turns out!

@@IcelyPuzzles Any update on it?

Yeah I would do that for level progression

There are some main game puzzles that use this mechanic, yeah, like Challenge 28 and 29. But it wasn't combined with 'you have to stuff specific voids with specific amounts of blocks' too like here!

It would actually be a lot like walking to your front door and going outside, but only being able to then move around in the front yard. If instead you went through the house and out the back door to the back yard you would be outside once again, but not in the same part of out side.

@@thedrunkshinobi you're not going through the back door, but the cat flap of the same front door to get to a different outside, which equally doesn't make sense. You can't get away without explaining how the game generates voids.

Oh it makes sense now because theoretically every infinity 'is' in void but when you are in void there is only one

infinity multiverse

thank you for the explanation but I still don't understand unfortunately

@@wiktord9264 it's simply because the purple box blocks itself from eating, that's all

@@wiktord9264 basically if you are off center the box will eat the void block, while in the center it acts like a normal solid block allowing you to enter from the side.

​@@wiktord9264 like others have said, you can eat the box when its off centre. this is because when you eat something, the thing you eat gets centred (pushing the purple block into the blue block will cause the blue block to be eaten and go into the centre of the purple block). however, when the purple block is in the centre, trying to eat the blue block would result in the blue block being "pushed backwards" into the purple, but the purple is "pushing forwards" into the blue, cancelling both pushes out (blue is pushing backwards because it enters from outside into the purple block) hope that helps. the level right after helps explain it further anyway

@@drcgaming4195 oh. Oh. I never realised that it centered the eaten box. Now it makes sense

OH MY GOD ITS A COMPLETELY REASONABLE MECHANIC

It's just recursive with a void outside to the right

this very well be the second last video, so enjoy it while you can lol

The level with the two different Epsilon blocks was still weird af, since the same paradox was used to enter both the Double Epsilon and the 2nd Single Epsilon, just from different clones.

@@doomse150 They really should've applied more colors to the boxes.

@@henke37 they couldn't in that level, because the second epsilon was the epsilon of the epsilon - it's like what happens if you stack two different colors in an infinite enter, but in this case it is the level and the epsilon of the level. The terminology is super confusing, but if you enter the epsilon block instead of the normal one you end up doing an infinite enter _of the epsilon_ instead of a double infinite enter of the normal one.

The weird thing is that the basic loop that you get sent on is the same for both X_e1_e1 and X_e2, it just gets initiated and cut off at different places. Enter X_e2: When you enter the X loop, it leads to entering X_e1 which leads to entering the X loop again, which leads to entering X_e2. Enter X_e1_e1: When you enter X_e1, you enter the X loop which leads you to enter X_e1 again (imo X_e2 should occur here since you already were in X_e1, but I guess that isn't considered part of the loop yet) which makes it seem like an X_e1 loop sending you to X_e1_e1, even though it isn't really a loop, because the next loop iteration (entering X_e1, then entering the X loop) should send you to X_e2 and NOT X_e1, since it matches the "Enter X_e2" loop described above + the initial X_e1 entering. Or, in an attempt to phrase it differently, entering X_e2 already requires entering X_e1 an infinite amount of times (and each of those require entering X and infinite amount of times), thus reaching a different "dimension"/"power"/"level" of infinity. This is kinda the same result as entering X_e1 which leads to the X loop, resulting in entering X_e1 an infinite amount of times, again reaching the 2nd "dimension"/"power"/"level" of infinity, but being sent to a different location as a result. But maybe my interpretation of Multi-Epsilons and their entry conditions differs from the one used by the game-dev.

@@doomse150 The simple response is that it matters where you start from. Also the way the loop detection works is the simplest it can be. Initially in this level anything entering either X clone is immediately sent to Xe1 because X is already stuck at its own right edge from the start. Then Tyler sets up the X clone inside of Xe1. From this point, you can either try to enter the other X clone or you can try to enter Xe1 directly, and those send you to Xe2 and Xe1e1 respectively, because of how the loops get detected: Start from enter X clone -> enter X -> enter X -> "enter X" has appeared once before in the move chain, loop detected on X, enter Xe1 -> enter X clone -> enter X -> "enter X" has appeared twice before in the move chain, loop detected on X again, enter Xe2 -> success Start from enter Xe1 -> enter X clone -> enter X -> enter X -> "enter X" has appeared once before in the move chain, loop detected on X, enter Xe1 -> "enter Xe1" has appeared once before in the move chain, loop detected on Xe1, enter Xe1e1 -> success The loop detection simply looks for repeat entities in the move chain as soon as it can, and counts them, and uses the count and the base room to identify the fallback. So Xe1 is triggered on the second occurrence of entering X, and Xe2 on the third. Now, you can imagine that instead of triggering Xe2 on the third occurrencd of X, it was triggered later, on the second occurrence of Xe1 - since in some math sense having a loop on not just X but also Xe1 is why it reaches Xe2. But this would actually do more work than is minimally necessary.

@@AexisRai I guess that makes sense, treating the different X Epsilons (Xe1, Xe2, ...) in an iterative way instead of a recuesive way is probably as reasonable as everything else. It would be could if they found a way to make the relations between Epsilons and their base level more explicit, since the color distinction fails for this case, but I can't come up with one on the spot.

@@doomse150 Maybe the Epsilon’s Epsilon could show up over the block as e^e instead of 2e.

@@tanookisam4911 i think i have a way of interpreting epsilons double epsilon: EE -> Ex2 epsilon's epsilon: E -> EE double epsilon's epsilon: E -> Ex2 E this works with epsilon's infinity as well epsilon's infinity: oo -> Eoo

desc text looks updated now

Map was called teleport yeah

whaaaaa?

Not this shit again... of course we end up with baba mechanics

@@pikminman13 level is inner push Is You2

Baba is the gold standard for meta gameplay if only because every sort of mechanic that can be done in a meta way can be replicated in Baba.

This is one bit I'm still stuck on personally, because I tried fiddling with this in Challenge 13 and predicted it would make a separate void, but it didn't seem to. If I go back and try again more carefully then maybe it will resolve this nicely.

I have confirmed that there is in fact a different void for every infinity. [That is, every one that is constructed on the spot. Obviously infinities that start inside a room don't need a void.] There's nothing weird happening in Challenge 13, it behaves the same way there as anywhere else, I just didn't know what I was doing.

how come it doesn't eat if the blue is centered vertically though?

@@patrolin because then you aren't pushing or eating, you're simply entering a block.

@@cyborg98 but why can't you push the block if it's in the middle? surely the algorithm goes something like: if (canPushBlock) pushBlock() otherwise if (canEnterBlock) enterBlock() otherwise stayPut()

@@patrolin So Patrick tries to push rightward into the purple room box that's inside itself. So... The purple room tries to leave itself, so tries to move to the void. Purple tries to _push_ the blue box, but they're all stacked up against the wall in the void. Purple tries to _enter_ the blue one, but they're unenterable because they're in the void. Purple tries to _eat_ the blue one. So... The blue room tries to enter (be eaten by) the purple room. If the purple room is not at the center of its own edge, there is nothing in the blue room's way of entering the purple room. So the blue room succeeds entering leftward into the purple room, the purple room succeeds moving rightward out of purple-infinity and into the void by eating the blue room, and Patrick succeeds at moving rightward by pushing the purple room. Move done. If the purple room *is* at the center of its own edge, then the spot that the blue room is trying to enter the purple room *at* is occupied, by the purple room. So the blue room tries to push it, so it tries to push Patrick - but Patrick is already pushing the opposite direction from earlier in the move-chain. Running into another entity from earlier in the chain moving in the opposite direction apparently actually hard-cancels the move attempt - not just the push attempt, but also skips the enter / eat / possess attempts that would come after it. So because the blue room's leftward move attempt (for being eaten) fails in this way, blue fails to be eaten, so purple fails to eat. Purple then tries to possess blue which of course fails, and so purple's move attempt fails, so Patrick's push attempt fails. _THEN_ since it turned out purple can't be pushed, Patrick tries entering purple and succeeds.

Definitely LOL

They are custom levels but there are no modded mechanics in them, in case that was implied by you saying "mod"

@@AexisRai That's actually what I was praising about them: the lack of any modded mechanics. I kind of get bored of people who mod games trying to make something either stupid difficult or adding whole new concepts after a while, when all the good fun can be achieved with the game in its most basic form, but designed in such a way that it makes you realise just how incredible the base mechanics already are.

"Keeo"

Never mind it happens right in the next level...

Yep, this is right

I do love that he says "blocks that were previously empty are now solid" at _exactly_ the time that he pushes the room outside itself, causing infinite exit, causing the room to eat the first of the solidified empty blocks, *_causing the eaten block to stop being solid again._* It's just perfect timing.

headcanon Patrick is a top

@@thepinkbunnyempire1027 ayo

...and this was elaborated upon in the next level because ofc it is.

Moving into the goal is not a bug, the behavior is correct, but the actual reason is subtle and there's a question of whether the "mechanic" of it was ever well taught in the game. The actual reason (I'm pretty sure) is this: When purple tries to move right by eating green, green must therefore try to move left by entering purple, so green must try to move left into purple at the spot where purple is, so green tries pushing purple left. But purple is already trying to move in the opposing direction (right), so by trying to push it left we hit this "mechanic": when a block's move attempt would try to cause another block from earlier in the move chain to move in the opposite direction, that move attempt fails entirely - it doesn't just fail the push attempt (which is probably when the opposing direction is detected), it skips everything else in the move attempt (so it skips trying to enter / eat / possess as well). So when green tries to move left into purple (because of trying to be eaten) and therefore tries to push purple left, the opposing direction is noticed and green entirely fails trying to move left into purple. So green fails to be eaten, purple fails to eat, purple fails to move right outward into the void, purple fails to exit purple, purple fails to move right, Patrick fails to push purple. _Then_ Patrick tries to enter purple and succeeds.

Sorry to break it to you but more like day 7 of backseating

Did I say day 7 sorry I’m super drunk

@@zandurka1 Imagine being drunk and going to the comments, couldn't be me.

Similar to how which block things infinite exit out of depends on which block they started in (refer to the level where you had to infinite exit out of purple and out of yellow), which block you start in when you infinite enter determines where you go. If you infinite enter and then infinite enter again going to the epsilon block, you go to double epsilon block. But if you infinite enter going into the epsilon block DIRECTLY, you go to the epsilon block's epsilon block. (And that's what the clone on the east border is a clone of.) It is a bit confusing, but it makes a kind of logic.

As Patashu said, the one on the right is epsilon's epsilon. You can see the video "Infinite Epsilon" by Reat showcasing this in Challenge 34, as well as epsilon's infinity. And Patashu is also right that it's about where the loop detection happens. If this happens: Try to enter X -> ... -> try to enter X that's a loop, so the game tries to send you to X's epsilon instead. If this happens: Try to enter X -> ... -> try to enter X, loop detected, try to enter X epsilon instead -> ... -> try to enter X that's a second loop on X, so the game tries to send you to X's second epsilon. But if this happens: Try to enter X's epsilon -> ... -> try to enter X's epsilon that's its own loop, not on X but on X's epsilon, so it goes to _its own_ epsilon.