Working with Maps | Unreal Engine 4.27 Documentation

After Blueprint Arrays, there's a good reason why Blueprint Maps are so popular. They support efficient look-ups and retrievals of values with the use of associated keys. At the end of this guide, you'll get some experience creating and editing Maps in the Blueprint scripting environment, querying and displaying items, and performing basic operations on Blueprint Maps in Unreal Engine 4 (UE4).

1. Required Setup

Before you can start working with Blueprint Maps, you'll have to set up your project to display the container's contents.

Create a new Project using the Games > First Person template, using the following settings:
- Blueprint enabled
- Maximum Quality enabled
- Desktop/Console enabled
- With Starter Content enabled
Name your project, ExampleMapProject.
Double-click the Blueprint folder from the project's Content Browser.

Click image for full view.
From the Content Browser, click the Add New button, then select the Blueprint Class, which is located under the Create Basic Asset pop-up menu.

Click image for full view.
After the Pick Parent Class menu opens, click the All Classes arrow to search for the TextRender Actor Blueprint Class.
Enter TexRenderActor in the Search Bar, selecting the TextRenderActor Blueprint Class before clicking the Select button.
At this point, you should have a new TextRender Actor located in your project's Content Browser. Go ahead and name the new Actor DisplayMap.

Click image for full view.
Now, drag the DisplayMap TextRender Actor into Unreal Editor's Perspective (3D) Viewport.

Click image for full view.
With the DisplayMap TextRender Actor selected, click the + Add Component button (located in the Details panel), and enter Box Collision into the Search Bar.

Click image for full view.
After adding the Box Collision Component to the TextRender Actor, name the new Component, Trigger Box.

Click image for full view.
Now, select the TextRender Component to view the Actor's Transform settings in the Details panel.

Click image for full view.
Update the DisplayMap Actor's Transform settings to reflect the following values:
Now, change the DisplayMap Actor's Horizontal Alignment to be Center aligned (rather than Left aligned, which is the default Horizontal Alignment value).
Currently, the Trigger Box Component is Hidden in Game. Go ahead and clear the Hidden in Game check box (located in the Rendering menu of the Details panel) so that you can view the Box Collision Component in-game.

Having the ability to view Box Collision Components in-game is a great way to debug any potential issues with the underlying logic driving a triggered event.
If you enter PIE (or Play in Editor) mode, you'll notice that your projectiles will have a collision response to the DisplayMap collision box. Currently, we only want the DisplayMap collision response to trigger an event that allows us to display the contents of your Map containers. To do this, go to the Collision menu (located in the Details panel), click the Collision Presets drop-down list box, and select the Custom... option.
Finally, update the Collision Presets to reflect the following values:

Section Result

Click image for full view.

By now, you've created a new project and you have also set up a new TextRender Actor, which will display the contents of a Blueprint Map container that you'll create, edit, and display in the next step.

2. Creating and Displaying a Blueprint Map

Now that you've set up a TextRender Actor in your newly created project, you're ready to create a Blueprint Map container, the contents of which you'll display in-game.

From your project's Content Browser, double-click the DisplayMap TextRender Actor to open its Blueprint Event Graph.
If you see the following screen, go ahead and click the Open Full Blueprint Editor link to get started.
Click for full image.
You should see the DisplayMap TextRender Actor Blueprint Event Graph, where you'll be able to add a Blueprint Map and its display logic.

Click for full image.

If you don't see the aforementioned screen, click the Event Graph tab to open the Actor's Blueprint Event Graph Editor.
Now is the time to create a Blueprint Map container, where you'll store some key-value pairs that you'll display later on. To create a new Blueprint Map, click the + Add New button (located in the My Blueprint panel) and select Variable from the drop-down list.
Name your new variable, Instruction Map.
Click the variable's pin type button, which is located next to the variable's name.
Now, select the Integer variable type from the drop-down list.
Click the variable's container type button, which is located next to the Variable Type drop-down list in the Details panel.
Select the Map container type from the drop-down list.
Now, it's time to define your Map's key-value property types. Currently, the key is an Integer type, which is the desired property type. The value type, however, isn't a String variable type, though. To change the value from being an Integer to being a String, go ahead and click on the value property type drop down list.
Select String from the drop down list.
At this point, you have a key-value pair that is of Integer and String types (respectively). Also, the Blueprint Graph reminds you that you need to compile the Blueprint in order to the define the items that you're going to store inside of the container. Go ahead and click the Compile button to get started.
Click for full image.

Compiling the Blueprint replaces the container's Default Value message with an interface, enabling you to populate your container with key-value pairs, wherein the Map's keys are Integers and the values are Strings.
If you already haven't done so, go ahead and click the Save button to save all of the work that you've done so far.
Click for full image.
Click the + (Adds Element) button (located in the Default Value menu of the Details panel) to add a new key-value pair to the newly defined Instruction Map container.
Define your container's new key-value pair, defining the key as 1, and defining the value as WASD to run.
Repeat the previous two steps, making sure to fill your Instruction Map container with the following key-value pairs:

Scripting the Logic

Before you can display the contents of your newly created Blueprint Map, you'll need to write the necessary logic.

Now that you've defined your container, go ahead and drag the Instruction Map variable into the Blueprint Event Graph.

Click for full image.
Select Get from the Instruction Map drop-down list.

Click for full image.
Drag off the Instruction Map node and add the Find node from the Map Utilities interface.

Click for full image.

There are several ways to get values from a Map. For this part of the tutorial, we'll go ahead and increment an integer key to display the associated values contained in the Instruction Map.
With the aforementioned note in mind, go ahead and click the + Add New button, selecting Variable from the drop-down list.
Makes sure to set the variable's type to an Integer type, giving it the name, Key. Right-click to the pin type to change it to a single value instead of a map if necessary.
After you've declared and defined your new Integer variable, drag Key into the Blueprint Event Graph, and select Get from the drop-down list.

Click for full image.
Drag off the Key node, search for, and add the IncrementInt node.

Click for full image.
Now, go ahead and connect the IncrementInt node to the Find node.

Click for full image.

For the purposes of this tutorial, you're going to use a time function to increment the Key variable.
Drag off the Event Tick node, search for, and add the Delay node.

Click for full image.
After you've set the delay duration to 2 seconds, connect the Delay node to the IncrementInt node.

Click for full image.
Go ahead and drag off the Event BeginPlay node, search for, and connect to the Branch node.

Click for full image.
Connect the IncrementInt node to the Branch node.

Click for full image.
Now, connect the Boolean return value belonging to the Find node to the Branch node's Condition pin.

Click for full image.

If the Find node successfully locates the item in the Map, the node returns true. Otherwise, if the Find node returns false, there is no item contained in the Map that uses the provided key.
Drag off the Branch node's True pin, search for, and connect to the Set Text(TextRender) node.

Click for full image.

This branch of your logic means that if there are valid key-value pairs in the container, go ahead and display the container's associated value(s).
To display your container's values in-game, connect the Find node's return Value pin to the Set Text node's Value pin.

Click for full image.
Now, drag off the Branch node's False pin, search for, and connect the Set Text(TextRender) node.

Click for full image.

This branch of your logic means that if there are no valid key-value pairs in the container, go ahead and display something else.
Drag off the Branch node's Value pin, search for, and connect to the ToText(string) node.

Click for full image.
Now, define the string to read, Now, shoot the blocks!.

Click for full image.
After inspecting your completed script, go ahead and click the Compile button before going back to the Editor's Viewport interface.

Click for full image.
From the Editor's Viewport interface, click the Play button to see your newly implemented script at work.

Click for full image.

Section Result

At this point in the guide, you've defined a new Blueprint Map, filled the container with key-value pairs, and displayed the values with some basic logic that you created in your TextRender Actor's Blueprint Event Graph. If you want to learn how to perform a slightly more advanced operation, please continue onto the next step, where you'll learn how to Add a key-value pair to a Map, subsequently displaying the Map's values.

3. Adding Keys and Values to a Map

By now, you have a TextRender Actor displaying the associated values of a Blueprint Map that you defined in the previous step. In this step, you'll learn how to Add a key-value pair to a Map, subsequently displaying the Map's keys and associated values.

From your project's Content Browser, double-click the Display Map TextRender Actor to open its Blueprint Event Graph.
You should see the Display Map TextRender Actor Blueprint Event Graph, where you'll be able to add a new Blueprint Map, to which you'll Add a new key-value pair, ultimately displaying the Map's keys and associated values to the Viewport.

Click for full image.
At this point in the tutorial, you'll want to create a new Blueprint Map container for the upcoming Add operation. Go ahead and right-click on the Instruction Map variable and select Duplicate from the drop-down list to create a new Blueprint Map variable, naming it Weapon Inventory Map.
Please make sure that the new Map container matches the following properties, where the key is a String and the value is an Integer:

For illustrative purposes, you're creating a weapon inventory Blueprint Map container, where the key is the weapon name and the value is how much ammunication is available for the weapon.
If you select your new Blueprint Map, the Default Value message, saying Please compile the blueprint, should be visible.

Click for full image.
Go ahead and click the Compile button.

Click for full image.
After compiling the Blueprint, you should see the Default Value disappear, making way for a default Map with no elements. Click the + (Add Element) button to add a single key-value pair.
At this point, the editor's Compiler Results window should also display the following warning:

Click for full image.

UE4 emits this warning because you're duplicating Instruction Map, which is a Blueprint map having an Integer-String key-value property, to create a Weapon Inventory Map, which is a Blueprint Map having a String-Integer key-value property. During the duplication process, the engine parses key-value pairs belonging to Instruction Map, attempting to copy them into the key-value pairs for Weapon Inventory Map, which is undesired behavior.

Click for full image.
Go ahead and fill your new Weapon Inventory Map container with the following key-value pairs:
Now, click the Compile button.

Click for full image.
After filling the Weapon Inventory Map container with the appropriately typed key-value pairs, satisfying the new Blueprint Map's key-value property requirements, you should see the warning disappear.

Click for full image.
Before you can add new logic to the existing Blueprint Event Graph, go ahead and drag the Weapon Inventory Map variable into the Blueprint, and select Get from the dropdown menu.

Click for full image.

Scripting the Logic

To get started with building your new logic, drag off the Weapon Inventory Map node and add the Keys node from the Map Utilities interface.

Click for full image.

The Keys node will output an Array of all keys that are present in your Weapon Inventory Map.
Drag off the Array output pin belonging to the Keys node, search for, and add the ForEachLoop node.

Click for full image.
Now, drag off the Array Element pin belonging to the ForEachLoop node, search for, and add the Print String node.

Click for full image.
Right-click in the Blueprint Graph to open the Context Menu, where you'll search for and add Event ActorBeginOverlap.

Click for full image.
Drag off the Other Actor pin of the Event ActorBeginOverlap node, search for, and add the Cast To FirstPersonProjectile node.

Click for full image.
Now, connect the Cast To FirstPersonProjectile node to the Keys node.

Click for full image.

Displaying your Map's Keys

At this point, if you enter Play in Editor (PIE) mode, you'll be able to fire a projectile at the collision box for your Display Map Text Render Actor, where you'll be able to display an Array of keys that are contained in your Weapon Inventory Map.

Click for full image.

Finishing the Script

Now's the time to add a new key-value pair to your container. To do this, go ahead and drag the Weapon Inventory Map variable into the Blueprint.

Click for full image.
Drag off the Weapon Inventory Map variable, adding the Add node from the Map Utilities interface.

Click for full image.
Now, define the key-value pair that you'd like to add, defining Weapon 6 as the key and 60 as the value.
Drag off the Add node's output pin, search for, and add the Branch node.

Click for full image.
Before you can set up the additional display logic showing your added key, you'll need to drag the Weapon Inventory Map variable into the Blueprint.

Click for full image.
Now, drag off the Weapon Inventory Map variable, adding the Keys node from the Map Utilities interface.

Click for full image.
Drag off the Array output pin belonging to the Keys node, search for, and add the ForEachLoop node.

Click for full image.
Now, drag off the Array Element pin belonging to the ForEachLoop node, search for, and add the Print String node.

Click for full image.
Click on the Text Color box to open the Color Picker menu.

Click for full image.
Go ahead and set the color to the following values:
Again, before you can set up more display logic, showing your added value, you'll need to drag the Weapon Inventory Map variable into the Blueprint.

Click for full image.
Now, drag off the Weapon Inventory Map variable, adding the Values node from the Map Utilities interface.

Click for full image.
Drag off the Array output pin belonging to the Values node, search for, and add the ForEachLoop node.

Click for full image.
Now, drag off the Execute Output pin belonging to the ForEachLoop node, search for, and add the Print String node.

Click for full image.
Drag off the Array Element pin belonging to the ForEachLoop node, connecting it to the In String pin belonging to the Print String node.

Click for full image.
Click on the Text Color box to open the Color Picker menu.

Click for full image.
Go ahead and set the color to the following values:
Connect the Branch node's True pin to the Keys node.

Click for full image.
Now, connect the Branch node's False pin to the Values node.

Click for full image.
To complete the script's logic, go ahead and connect the Cast Failed pin of the Cast To FirstPersonProjectile node to the Add node.

Click for full image.
After inspecting your completed script, go ahead and click the Compile button.

Click for full image.
Finally, click the Save button before going back to the Editor's Viewport interface.

Click for full image.
From the Editor's Viewport interface, click the Play button to see the updated script at work.

Click for full image.

End Result

As you can see from the video, when you initially fire a First Person Projectile the Display Map TextRender Actor's collision box, you'll see the original five keys being printed to the Viewport. Then, when you walk through the collision box, you'll see the new key being added, subsequently being printed. After backing out of the collision box, go ahead and fire another First Person Projectile to confirm the newly added key. Finally, when you walk through the collision box for a second time, you'll see all of the values being printed.