# Top-Down Engine - Getting Started {% hint style="info" %} **Good to know:** Both the Platformer Engine & Top-Down Engine share a lot of functionality. and a lot of times the same techniques can be applied to both engines. {% endhint %} ## The Demo Map When you open the project, you will see the Pixel2D Demo Scene.

You can explore any blueprints to see how they work if want to recreate certain aspects or duplicate the object. You can also duplicate this scene if you want to quickly try out some RPG ideas, but for the purpose of this tutorial, we will start with a clean slate. ## Creating a new map We will start by creating a new folder under **Content** named after your project. We are calling ours **ManualTM**.

Try to keep your files as organized in folders as possible.

Right-click in your Maps folder to create a new level.

We are using a prefix (**Man_**) for any assets that I make or are specific to my side of the project so that I can find them easily even if they share the name with a pre-built asset.

Once you have opened your go to **Edit → Project Settings**. We will be changing some settings to make the project your own.

Let's start with some rendering settings. Switch off some of the default render settings, especially Bloom and Auto exposure. These settings are great for making 3D Unreal games and templates look great out of the box, but will be useless for our needs with the 2D game.

The other settings shouldn't do much, but if something looks wrong with the visuals (i.e it starts whitening and brightening up for no reason), check these settings.

Time to go to maps and modes. Here, take a peek at the **default game mode**. It decides what defaults are spawned in-game unless overridden. If you would like to change the Game mode later on you can, but we will only be changing the **Default Pawn Class** later in the tutorial.

The second thing to look at is your **Editor Startup Map and Game Default Maps**. Changing the startup map to the current map helps with a quicker startup while changing the game default makes sure any build you send will use the current map as Level 1. If you would like a different map to open when you open your game build, you can change the map in **Default game map**.

We are going to add three more things to this scene. You can add these through the **Place Actors** Window or this icon in Unreal 5 →![](https://184658417-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwhC5kRxAV2gkiYRfd0As%2Fuploads%2F19v4HVtDVqgtO4jKRERW%2F6.PlaceActor.png?alt=media\&token=63d6d896-b0d0-42ae-aef7-bf678d3bf05c) A directional light, because I will need it to see the 3D objects. We will only need this during development.

A plane, because this will be the object our player will actually be moving on. It will automatically be added in horizontally, which is great for us.

And a player start, because we need the player to start somewhere.

We are going to import test images for a player, NPC and enemy sprites, and a test tileset (Danger tiles, Walkable tiles, Special tiles, and Blocking objects). It's great to have test graphics especially if you are just starting out and want to play around with your idea without being limited by the graphics. They can help you quickly test things out before you get custom art.

Danger tiles, Walkable tiles, Special tiles, and Blocking objects

The tutorial is written in the recommended workflow where we start by making the Core Gameplay, then interfaces before I work on adding the art and animation. However, you can do the following tutorials in the order you choose. --- # Agent Instructions: 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://polyart.gitbook.io/pixel-2d/guides/top-down-engine/top-down-engine-getting-started.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.