Okay, so you may be thinking the next part is actually pretty hard. But actually, it's really, really easy. Because of the way I've we've set up a game. So remember, everything is on a flat plane, everything is that the coordinate of one zero in the y axis, and a player is actually is freezing is positioned in the white position because it never needs to move up or down, although it appeases moving around an earth around the planet. So what we need to do, we have our ground here, which has our ground and our water, we actually need to create a new object called I'm going to call this planet. Let's set its coordinates to 000.

And then let's just grab grab the ground model here and put it under the planet. And then all we need to do is we need to find the end of the planet. So right down here and we need to create a highlight here. And we're gonna create a new, 3d, new empty. I'm going to call this Trigger Zone. And we're going to add a box collider to this.

And we're gonna make it is trigger. And we're going to so right now our planet's coordinates should be at 000. Ground should be at zero, negative 0.5, and zero. And our Trigger Zone needs to be basically at the end of this planet area here. So if we just drag this forward, we can see that it's at about 100. So if we just spin this around, we'll see that Yep, that's pretty much at 100.

So if we just make this 100 should be perfectly on the edge there. And then we can make this scale. You know, five, make sure it's wide enough. Actually, let's make that 10. And let's make it five on the waxes as well. Cool.

So that definitely covers us. So when out play, it goes through this trigger, we need to do something and what we need to do is we need to create a script out to this method and then we need to add some instructions in that method. So let's let's do that. So let's go over to our script folder. let's right click Create C sharp script and we'll call this level. Jen.

Let's drag this on to the Trigger Zone. So add triggers Enter to have that level generator script the is trigger box claddagh and let's open up level 10. Okay, so inside about level generator script, we can actually just delete the void star The Void update, we don't actually need them. Okay, so the first thing we need is a on trigger enter method. So we can actually go over to our score script and just copy this one here because we've already written it out. dump it in here, void on trigger, enter.

Awesome collider other cool, we don't need this. And we don't need a The if statement in here either because we only have one thing that's going to be colliding. And then we're going to need to call a method, but the type of method that we're going to be calling is not actually an method but an enumerator. So it's the same as the method but what it lets it lets us do it's a ko routine. And what that means is what it lets us do is it lets us wait for a certain amount of time before we perform a certain action. Don't get too caught up in the terminology here because we don't we won't use them these too much.

But just know that we need to first create a ienumerator which is like a void but it's not a void. So we did that by creating ay ay numeral, we're gonna call it transfer And inside of an ienumerable, it needs to return something. And so what we need to do is we could we could write, return now, you return null, but we're not going to do that we wanted actually to wait for one second. So we're going to say, yield. Return new. wait for seconds.

And it's gonna ask us how many seconds and we just say one. Cool so now it's going to wait one second before performs the next line of code. And all we need to do to call this transfer coverage name, or our numerator is to start a ko routine. So start Kuru teen. My spelling is atrocious. And then we can just open parentheses open speech marks and right Trent transfer So that's a little bit overwhelming, I understand that it's because it's different terminology and different ways of calling things how we normally would.

But this will work just fine. And so now we're just gonna ride debug dot log, hit the Trigger Zone after one second. And let's close that out with the semicolon, copy this. let's dump it in here, just to make sure everything's working. delete that. And we can go back to unity and press play.

So press play. All right, if we go over to a console, hit the Trigger Zone, hit the Trigger Zone after one second. Awesome. So we know that this is working perfectly well so we can delete these two debug logs. And the only other thing we need to do to get the to get the level Moving forward continuously is we just need to wait for one second. And the reason we need to do that is just so we have enough time for the player to move through the trigger.

And for this part of the level to be behind the camera, so that's why we wait one second and then all we need to do is move the level forward by that certain amount. So it's actually quite easy. So I'm going to do is write game object dot transform dot parent dot position equals new vector three. And a new vector printing it's just needs to be zero, not changing the x axis zero not changing the y axis, and then game objects dot transform dot position z plus we need to have a certain amount. And we need to work out what that is. Let's just say 100 for now, but we need to actually work that out, add a semicolon in there.

So the reason we use game object dot transform dot parent dot position is because we actually need to get the position of the parent game object. So if we remember our Trigger Zone is here, but we don't need to get we don't need to move just the Trigger Zone for we need to move the parent. So we need to actually get the parent object which is this planet A. So that's the reason we use transform dot parent dot position. Cool. So now we've got a planet here.

Let's just copy this and paste it. And let's just drag this one forward. Right and two, we hit the right spot. So we can see here we've got 200. So we know the value that this needs to move forward. Because this panel is that zero, we know the value that this needs to move forward is by 200.

So let's go back into a script and let's change this to 200. And let's name this planet underscore B. And let's name this planet underscore a. And let's just press play and see what happens. Okay, so going forward, and it appears that the level just continues forever. So what's actually happening here?

So let's just have a quick look. We go to a scene manager script and we turn off object spawner. So we've got nothing in our way, and we press play, we can actually go to the player and you'll see that what's actually happening is as the player passes certain spots, it's deleting the world behind the player and sending it 200 clicks Forward, that makes sense. But from the player's perspective, the play that's actually playing the game, see our shader is stuffing up, have you there a little bit? That's okay. It just looks like the world is going on and on and on and on forever.

Because it's, it's it's lining up seamlessly. We know exactly where things lining up and the web will just continue doing this forever. Or until the phone breaks or something like that. Go back to the city manager, and we turn back on objects corner. So yeah, this is basically simple procedural level generation. But the only problem we have now is, is now if we pulls it, we have a bunch of different triangles here.

And eventually they will add up in our memory. And things will get really messy and really slow and use a lot of data. So what we want to do in the next episode is working out how we're going to clean up this the stuff that's behind the player. So see you there