> For the complete documentation index, see [llms.txt](https://picnic-in-the-oblivion.gitbook.io/level-editor/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://picnic-in-the-oblivion.gitbook.io/level-editor/waypoints-or-hard/transitions-and-waypoints.md). # Transitions and Waypoints Let's create transition to that tree! First we start from easy one - teleporting.

First - create transition zone, go to ZONES/ folder and drag transition\_zone.tscn to the scene.

Then go to HELPERS/ folder and drag transition\_target.tscn to the level.

Helper - 3D Arrow for player's future position and rotation

This helper will be our spawn point when we use transition zone. Let's set transition\_zone parameters inside inspector in Keys.

Basic transition zone has: **last\_point\_is\_end** - used only with waypoints, last point will be the same as target\_object **name** - must have unique name for scripts **target\_object** - name of our helper, will teleport player to target position \*can't be empty **waypoints** - play walking animation between points and then at the last point teleport player to target position \*if empty - only teleport to target Let's rename our target helper to "tree\_target"

Set same name to **target\_object** in transition\_zone Keys.

Let's test. We teleported to the helper and looked at the same direction that the arrow is looking.

But let's make it difficult - create some waypoints path. Click Right mouse button on the level root node and select Add Child Node...

Search for the Path3D.

Click create. {% hint style="warning" %} Do not move it from zero XYZ position. {% endhint %} When Path3D is selected you'll see that you have new tools at toolbar at right top corner.

{% hint style="info" %} First - select point\ Second - Select control point\ Third - Add point\ Fourth - Delete point\ Fifth - Close curve {% endhint %} Create first point. with Third button on toolbar (green plus sign with green dot). Also don't forget to switch to top view.

Top view. Can be switched by clicking on X Y or Z at the right top corner.

And put first point.

Then go to the inspector and open Curve parameter. Select Points group.

Set Y to 1.7, so the next new points will be at the same height.

Now draw click new point and place the last one close to helper target.

Okay, lets name our Path3D with unique name and put same name intro transition\_zone Keys.

Lets test! See, now player walk with these points right into target.

Hey, let's delete target helper and will try to make last point of waypoint ours target!

Keep waypoints name, but delete target\_object and turn on last\_point\_is\_end.

Now, let's make transition trigger with level change function! You can do it in a few ways - manual or using prefab. Let's talk about a manual option. Select transition zone on the current level and change its "id" from "transition" to "transition\_to\_level" and add a new String key "level" with String value of target level ID. For example - let's set "intro" level from res\://assets/levels/

As you can see, after we reach last point of waypoint - we load new level.

I recommend to block rooms between for prevent player use triggers through walls.

Orange - blocks between rooms | Screenshot from old level editor

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://picnic-in-the-oblivion.gitbook.io/level-editor/waypoints-or-hard/transitions-and-waypoints.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.