Skip to content

🧠 Working with Variables

The Saveable component allows storing key-value string pairs during runtime.

🔁 Blueprint Functions

ℹ️ All Saveable variables are stored as strings internally. Use GetVariableAsInt or manual conversion for numeric operations.

✅ Saveable variables are ideal for counters, flags, or state values that don't need to exist as native Blueprint variables.

Available under Save Kit → Saveable:

  • SetVariable(Name, Value) — set a string value at runtime
  • GetVariable(Name) — get string value
  • GetVariableAsInt(Name) — parse as integer
  • HasVariable(Name) — check if variable exists
  • IncrementVariable(Name, Amount) — add to numeric value
  • RemoveVariable(Name) — delete variable

Saveable Blueprint functions

⚙️ Example: Using Saveable Functions

Use Saveable functions to manage data at runtime:

  • SetVariable — assign a value
  • GetVariableAsInt — retrieve and modify numeric values
  • IncrementVariable — track counts or scores

Using Saveable: Set, Increment, SaveGame

Example: reducing Health, marking as Damaged, and incrementing HitCount.

🆚 Saveable Variables vs SaveGame Properties

Use Saveable for lightweight, flexible runtime data.
Use SaveGame for Blueprint-visible variables and type-safe access.

Method Defined In Access at Runtime Saved by SaveKit
Saveable Variables Saveable Component ✔️ via Blueprint nodes ✔️ Yes
SaveGame UPROPERTY Actor/Blueprint field ✔️ directly (Get/Set) ✔️ Yes (if serializable)

Use Saveable for flexible runtime state, and SaveGame for native Blueprint variables.

SaveGame property example

Note: Actor transform, tags, and SaveGame properties are also saved.
See Saving & Loading for details.

🧪 Example: Displaying Saved Data

Use GetVariable, Tags, and SaveGame properties to dynamically show state:

Displaying Saveable + SaveGame

This Blueprint formats and displays Health, HitCount, Tags, and Damaged state.

🚫 Limitations of Saveable Variables

⚠️ Only string values are supported in Saveable variables. Complex types like vectors, rotators, and structs are not supported.

  • UObject references
  • Arrays of objects

Use IDs or reconstruct them manually after loading.

ℹ️ See Limitations for serialization compatibility.