Using excel to store gameplay data - DataTables

Revision as of 23:10, 5 September 2016 by Vertex Soup (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Rate this Article:
(7 votes)

Approved for Versions:(please verify)


Data driven gameplay helps mitigate the amount of work and complexity involved, as well as providing the ability to visualize and parameterize data creation and progression, for games that have an extended lifetime well beyond that of a typical boxed game, and require constant tweaking and balancing of data based on player feedback. The ability to move data out to Excel documents that can be maintained using proven tools and then imported to automatically take effect in the game. Epic's Data Driven Page

Quick How To Use

1. Create the CSV File

Using Excel / Google Docs, create a sheet with the following properties:

Csv table example.png

Remember to not use spaces in the field titles, and also its important to have the first column/row in blank. Export this file as CSV.

2. Create the structure in the game

There are two methods of creating the structure.

1) You can create a blueprint Structure in the engine under "Add New > Blueprints > Structure".

2) You can create a C++ struct in code like this:

/** Structure to store the lookup of GameObjects for use in a UDataTable */
struct FGameObjectLookupTable : public FTableRowBase
	/** Full Path of Blueprint */
	UPROPERTY(BlueprintReadOnly, Category = "GO")
	FString Blueprint_Class;
        /** Category of GamePlay Object */
	UPROPERTY(BlueprintReadOnly, Category = "GO")
	uint16 Category;
        /** Scriptable Use Code */
	UPROPERTY(BlueprintReadOnly, Category = "GO")
	uint32 Usecode;

3. Create the structure in the game

Import the data into your game. Make sure your file is named CSV, drag to content or hit the import button, select the destination data structure.


4. Using the DataTable in Game


// o-- Lookup table for Game Objects - Loaded from CSV/Excel
UDataTable* GameObjectLookupTable;


static ConstructorHelpers::FObjectFinder<UDataTable> 
GameObjectLookupTable = GameObjectLookupDataTable_BP.Object;

Searching and Getting Data

static const FString ContextString(TEXT("GENERAL"));
// o-- Search using FindRow. It returns a handle to the row.
// Access the variables like GOLookupRow->Blueprint_Class, GOLookupRow->Usecode
FGameObjectLookupTable* GOLookupRow = GameObjectLookupTable->FindRow<FGameObjectLookupTable>(
if (GOLookupRow) {
		GEngine->ScreenMessages.Num() + 1,

Referencing Assets from your data table

1. Within the content browser, find the game asset you wish to reference. Right click on the asset and select "Copy Reference" to get the full path reference. Then, copy and paste that into your CSV file. Your asset will need to be surrounded by three double quotes (The first and last quote are quoting the quote). Note: The asset path contains an extension for the asset, which must be included! It's super easy to overlook.

Sample in CSV file: """Texture2D'/Game/Assets/Textures/Characters/KnightPortrait.KnightPortrait'"""

2. Your struct should contain a TAssetPtr<T> for the asset type you are importing. The TAssetPtr is a lazy initialized asset pointer which only loads an asset when its needed by the game. Be careful with assets which have a large file size. If they need to load during runtime, you'll get a slight delay in game. You can force an asset to be loaded at any time within code by calling the "Get()" method.

Sample in struct:

UPROPERTY(EditAnywhere, BlueprintReadWrite, Transient, Category = "CreatureData")
	TAssetPtr<UTexture2D> Portrait;


  • Show how to load the CSV dynamically too. If you do, remember to get back here and put how you did.