Create a new custom Godot Resource class for game data (items, skills, character stats, quests, enemy definitions, etc.). Use when you need a reusable data container.
Create a custom Resource class for: $ARGUMENTS
Custom Resources in Godot are the standard way to define reusable data containers. They can be:
.tres files in the editor inspectorpreload() or load()@export types on other scriptsMANDATORY — before writing any code, complete BOTH of these:
godot-docs subagent:
Task(subagent_type="godot-docs", prompt="Look up Resource class and custom Resources. I need the Resource API, @export patterns, and how to create .tres files for a [RESOURCE_TYPE] data type.")
Read("docs/best-practices/04-resources-and-data.md")
Parse the arguments to identify what properties this resource needs. Common JRPG resource patterns:
| Resource Type | Typical Properties |
|---|---|
| Item | name, description, icon, item_type, value, stack_size, effect |
| Skill / Ability | name, description, icon, mp_cost, damage, element, target_type, animation |
| CharacterStats | max_hp, max_mp, attack, defense, speed, luck, element_resist |
| EnemyDefinition | name, stats, sprite_frames, loot_table, ai_type, exp_reward, gold_reward |
| Quest | id, title, description, objectives, rewards, prerequisites |
| QuestObjective | description, type, target, required_count, current_count |
| DialogueLine | speaker, text, portrait, choices, next_line_id |
| StatusEffect | name, type, duration, strength, tick_damage, stat_modifiers |
| LootEntry | item, drop_chance, min_count, max_count |
| Equipment | name, slot, stats_bonus, required_level, sprite |
Create at game/systems/<system>/resources/<name>.gd or game/data/<category>/<name>.gd.
@icon("res://assets/icons/<resource_type>.svg")
class_name <PascalCaseName>
extends Resource
## <Brief description of what this resource represents.>
##
## <Extended description. How to create instances, what they're used for.>
## <Property description.>
@export var name: String = ""
## <Property description.>
@export var description: String = ""
## <Property description.>
@export var icon: Texture2D
## <Property description — use enum for categorical types.>
@export var <property>: <Type> = <default>
@export on ALL properties so they're editable in the inspector## doc comments above every property@export var stats: CharacterStats)Array[<Type>] for typed arrays (e.g., @export var loot_table: Array[LootEntry])@icon if you have a relevant iconIf the resource needs enums, define them in the resource script:
class_name Item
extends Resource
enum Type {
CONSUMABLE,
EQUIPMENT,
KEY_ITEM,
MATERIAL,
}
enum Rarity {
COMMON,
UNCOMMON,
RARE,
LEGENDARY,
}
@export var item_type: Type = Type.CONSUMABLE
@export var rarity: Rarity = Rarity.COMMON
If the user wants sample data, create .tres files:
[gd_resource type="Resource" script_class="<ClassName>" load_steps=2 format=3]
[ext_resource type="Script" path="res://data/<category>/<name>.gd" id="1"]
[resource]
script = ExtResource("1")
name = "Example"
description = "An example resource."
After creating files, report:
@export var item: Item, preload("res://data/items/potion.tres"))