RPG Creation Kit - User contributions [en]

Main Page

2026-02-05T19:14:43Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

''Latest RPG Creation Kit Version: '''2.0.'''''

'''If you're new to the RPG Creation Kit, see the:''' [[:Category:Getting Started|'''Getting Started''']] '''page.'''

'''Newest Tutorials'''
* [[What's new in the RPG Creation Kit 2|What's New in the RPG Creation Kit 2]]
*[https://www.youtube.com/watch?v=llO1YsHaPtM <nowiki>[Video by OctoverseStudios] How to Add a New Race in RCK Using Synty Models</nowiki>]
*[[Converting Materials to HDRP]]
*[[Creating a New Race]]
*[[Creating Your First Worldspace]]
*[[Changing the New Game Starting Location]]
*[[Creating a New Persistent Reference AI]]
*[[Creating a New Looting Point]]
*[[Adding New Animations to NPCs dialogues]]
*[[Creating a New Creature AI]]
*[[Creating a New Melee Weapon]]
*[[Creating a New Armor Item]]

'''Other''' '''Tutorials'''

* [[Items Ownership, Metadata and Stealing]].
*[[Persistent References]]
*[[Mutable|Mutables]]
*[[Interactive Objects]].

[[Special:AllPages|View All Documentation Pages]]

'''Community Made Tutorials'''

The page below contains all the links to videos and articles of tutorials made by the community for the community.

* [[Community Made Tutorials]]

What's new in the RPG Creation Kit 2

2026-02-05T19:13:19Z

Silvematt: /* Other */

In this page you'll find an explanation of the new systems and changes that arrived with the release of the '''RPG Creation Kit 2.0'''.

== Show/Hide Demo Files ==
[[File:RCK2 1.png|423x423px]]

The first change to the Editor Tools is the addition of a toggle named '''"Show Demo Files?"'''. When toggled on, the respective Editor (such as "Rck Object Viewer", "Cell View", "Quests", "Rck AI Editor", etc.) will show files related to the Rck Demo. As you can imagine, toggling it off will hide from the lists content related to the demo.

This will be pretty useful when you'll be deep into creating your own content and the Rck items will get in your way as you're trying to find or search for things.

Each asset that can be hidden has now a flag "IS_DEMO_FILE", that will act as the flag that hides/show results:

[[File:Rck 2.png|400x400px]]

So as you'll make new content it will be enough to disable this flag for your own items.

'''You can also set the default value''' for the '''"Show Demo Files?"''' toggle to be on/off whenever you open your project by going in "''Edit->Project Settings-RPG Creation Kit''" and setting the value of the toggle there. Setting it off will make sure that whenever you open a window like the "''Rck AI Editor''" the demo files will be set to be hidden by default.

[[File:Rck2 3.png|400x400px]]

== Toolbar Functions ==
[[File:Rck2 5.png|578x578px]]

The main toolbar, located in the upper part of the Editor, will now have three more buttons related to the RPG Creation Kit:

* '''Load Last Save:''' allows you to Start playing in the Editor and automatically loads the latest savegame (or autosave) you have. It's an incredibly helpful tool that allows you to quickly jump in game to view your edits.
* '''Load Last Cell''': does the opposite. It loads the last cell that you've loaded via the Cell View or Cell Map View. It's best used along with the Load Last Save button t.
* '''Adjust Time Of Day (ToD) Preview:''' is a slider that sets the Time of Day for your selected "Time of Day Sky Material" (set in the Project Settings). It sets the "currentTime" value in the Sky's material and it updates the scene lighting in base of this value. It's useful to preview a Cell (or many cells) in the Editor at any given time of the day.

== Time of Day ==
The Time of Day feature adds the concept of time inside of the RCK.

Days consist of 24hrs and there's currently no convention for Days/Months/Years, which is something that can be extended from this system.

A GameObject named '''"TimeOfDayManager'''" has been added to the _WorldLoader_ scene, and it has a component with the same name as the Object that is, in fact, the manager of the time system.

[[File:Rck2 6.png|560x560px]]

* '''Current Time''' [0-24]: explicit the current time of the day. This can be set when the game starts, when a save game loads, and it can be arbitrarily set from other scripts. For example, the script "JustAnotherDeliveryStage10".
* '''Hours''' and '''Minutes''': are derived from the Current Time, and they're useful for you to read in order to create dynamic scenarios based on the current time (see next section "''Dynamic Responses to Current Time''") or to display the current time on the UI.
* '''Current Time Scale''': dictates ''how quickly'' time passes. The formula that runs on Update is is:<syntaxhighlight lang="csharp">
SetTime(currentTime + (currentTimeScale * Time.deltaTime));
</syntaxhighlight>A Time Scale of 1 means that one hour passes every second, so for the default value of 0.05, a full day (24hrs) 480 seconds or 8 minutes. You can also set this at runtime whenever you want, although runtime changes are not saved on the save-file (the value you set in the inspector will be loaded when a savegame is loaded).
*'''Skybox Material''': is a reference to the material that you're using in your world. If you want a different Skybox material you'll have to change this reference (to update it in game) and the reference in Project Settings (to allow the ToD slider to correctly preview the skybox in the editor). In the RCK default configuration there is only one Skybox Material that contains 3 Cubemaps that represent Day, Dusk, Night, that are blended in base of the Current Time Value. You can swap the Skybox Material reference if you want, even during runtime, but you'll also have to do so in the [https://docs.unity3d.com/ScriptReference/RenderSettings-skybox.html RenderSettings].

The next values "Sun & Moon" allows you to fine-control the lighting of your scenes as time passes.

* '''Sun Light:''' is a reference to your main Directional Light (sun) that is also in the _WorldLoader_ scene.
* '''Sun Color:''' is the sun's color.
* '''Sun Intensity:''' allows you to set a curve that controls the intensity of the Sun's light as time goes by. So the value at the beginning of the curve would be the sun's intensity at hour 0:00, while the last value is at the very last minute of the day 23:59.
* '''Ambient Color/Intensity:''' allows you to define gradients that controls the [https://docs.unity3d.com/speedtree-modeler/manual/light-object-reference.html ambience] of your scene at runtime. The gradient is also distributed over the currentTime, so you can have dark ambient settings at night and more light ones during the day.
* '''Fog Color/Density:''' allows you to do the same but to the fog setting of your scene.

The values set in here are to be thought as the "default" values.

'''However,''' you probably want control over ambience/fog for '''each [[worldspace]]''' and even for '''each [[cell]]'''.

[[File:Rck2 7.png|475x475px]]

The Worldspace data has also been given these properties, to allow you to customize your worldspaces as you wish.

* '''Global_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS:''' if set to true it will mean that the default 'Time of Day Manager' values we've set previously for Ambient/Fog will be '''overridden''' by the Worldspace when the player will be in that worldspace.
* The rest of the values are the same as explained previously, with some additional tweaks such as fog start/end and modes.

The same concept applies for individual Cells:

[[File:Rck2 9.png|581x581px]]

* '''Local_Override_ToD_Setting:''' determines whether to inherit the <code>TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS</code> setting from the parent Worldspace or use the local boolean <code>Local_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS</code> defined on this Cell. If Local_Override is false, <code>Local_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS has obviously no effect.</code>
* The rest of the values are the same as explained previously.

So the idea is that you would have ambient/fog responsive to the Time of Day (set at a worldspace level) for exterior worlds, and you can decide to override it for interiors (such as always-dark dungeons). But, you can also make interiors (such as houses with windows) whose Ambient lighting responds to time of day.

== Dynamic Responses to Current Time ==
This whole Time System goes well together with the [[Scripting|Scripting System]] of the RPG Creation Kit and in general with the component-based architecture of Unity.

We can query at anytime the Current Time of day, also as (Hour::Minute) and dynamically make things happen, or prevent things from happening. This allows you to create content that depends on time of day, such as dungeons that are only accessible at night, events that can only happen at a certain time of the day, and this also allows for Dynamic NPCs routines.

In the RCK demo we have 5 examples:

* '''NPCs equip torches at night.''' [RckAI_EquipTorchAtNight.cs]
* '''Shops in the city close at night.''' [CityInterior_LockShopsAtNight.cs]
* '''The "Killing Monsters" quest can be only completed during the night (22:00 - 05:00), because the door entrance will be locked during the day''' [Virrihael_LockUnlockVampiresDungeon.cs].
* '''Merchants in the City simulate stop working at night and simulate going in their houses''' [CityInterior_StallOwnersGoToSleep.cs].
* '''The windows of the houses in the city will be lit at night''' [CityInterior_TurnHouseLightsOn.cs].

Let's see the NPCs equip torches at night example.

You can attach the '''RckAI_EquipTorchAtNight''' component to any NPC prefab you have. Such as "CityGuard004" shown below.

[[File:Rck2 10.png|537x537px]]

This component acts as a "manager" or "controller" for the NPC actions that have to depend on time.

The logic for this example is very simple, if the CurrentTime is greater or equal of what we consider the start of the day (dayStartHour), and the CurrentTime is lesser than what we consider the start of the night (nightStartHour), we should not have a torch equipped.

Otherwise, we should equip a torch. This simple logic is present in the script "RckAI_EquipTorchAtNight", that subscribes to listen to '''OnHourChanges''' event.

So everytime there's an hour change we can run the check to equip/unequip the torch.<syntaxhighlight lang="csharp" line="1" start="1">
public void HandleOnHourChange(int curHour)
{
if (ai == null || ai.equipment == null || ai.isInOfflineMode || !ai.isAlive)
return;

bool isTorchEquipped = ai.equipment.currentTorchInHand != null;

// Equip torch logic
if (curHour >= dayStartHour && curHour < nightStartHour)
{
if (isTorchEquipped)
ai.equipment.Unequip(EquipmentSlots.LHand);
}
else if (!isTorchEquipped)
{
var torch = ai.inventory.GetItem("ITorch001");
if (torch != null)
ai.equipment.Equip(torch);
}
}
</syntaxhighlight>You can also subscribe functions to the '''onMinuteChanges''' or '''onTimeChanges''' to have more granular control.

The Scripts are placed on the most suitable GameObject you can think of:

* For RckAI Equip Torch, we place it on the NPC itself.
* For the Door that has to be locked at night, we could place it on the door itself. In my case I prefer to have a "TIME_DEPENDENT_SCRIPTS" GameObject in each Cell, so it will be attached to that game object.
* Same thing for both the houses window's light logic and merchants.

This idea is the whole foundation to build proper '''NPCs Schedules''', that I wish to create and formalize formalized in dedicated assets in a future update.

== XP, Leveling & New Attributes System ==
The Attributes System has been reworked to actually influence in-game actions, for both the player, NPCs and Creatures.

In addition to that, XP and Levels are now a thing. The player can earn XP by killing monsters, completing quests or via [[Scripting]], and also [[Events And Consequences|Events & Consequences]]. As you could expect, the player levels up and he's granted attributes points to improve his attributes. RckAI (and derived) also have a level now, that is defined by their attributes (the more the sum of the attributes values, the greater the level) and the level of the AI is used to compute the XP reward on kill.

Let's see how this is managed:

=== Default Values ===
The first thing that you should know are '''default values.'''

'''For the Player''', these are set in the RckSettings.cs file, under the name of '''<code>PLAYER_ATTRIBUTES_DEFAULT_X</code>'''where "X" is the attribute short name. By default all values are set to 25.

'''For the AI''' (when created via the RckAI Editor) they will have the values of the attributes of the '''RckAI_Prefab''' (located in your project).

=== Player XP and Level Up ===
The XP "curve" to level up is defined as a function the '''RckSettings''' file, under the name of "'''GetNextLevelXPValue(uint level)'''"''',''' and stands as the following:<syntaxhighlight lang="csharp" line="1">
// Calculates the XP needed to reach the given level
public static ulong GetNextLevelXPValue(uint level)
{
ulong xp = level * level * XP_NEXT_LEVEL_SCALING;
return xp;
}
</syntaxhighlight>So the value returned by this function is the '''amount of XP needed for a level up'''. This amount depends on the player's level.

You can of course change and tweak this function as much as you want.

=== Player Attributes Point per level ===
Regarding the player's level up, the RckSettings also defines these constants you may want to tweak:<syntaxhighlight lang="csharp">
public static float LEVELLING_UP_ALERT_MESSAGE_DURATION = 5;
public static uint LEVELLING_POINTS_PER_LEVEL = 5; // 5 attributes points per level
public static bool LEVELLING_LEVEL_2_SKILL_TUTORIAL_ENABLED = true;
</syntaxhighlight>

=== AI Level and XP Awarded On Kill ===
The AI level is automatically set while you tweak the AI's Attributes in the "RckAI Editor".

The level is calculated in base of a constant set in the RckSettings:<syntaxhighlight lang="csharp">
public static uint LEVELLING_AI_ATTRIBUTES_POINTS_PER_LEVEL = 5;
</syntaxhighlight>Every '''LEVELLING_AI_ATTRIBUTES_POINTS_PER_LEVEL''' (value) gave to the AI increases the AI level by 1.

AI Level is then used to calculate XP Reward:<syntaxhighlight lang="csharp">
public static ulong CalculateXPGainedOnAIKill(uint aiLevel)
{
ulong xp = aiLevel * XP_GAINED_ON_AI_KILL_BASE;
return xp;
}
</syntaxhighlight>You can edit "XP_GAINED_ON_KILL_BASE" default value as you wish.

The value returned by this function is also multiplied by the '''XpMultiplier''' that you can set for each AI:

[[File:Rck2 12.png|634x634px]]

Thanks to the '''Xp Mult''' I was able to tweak the value for all the AI the player would meet in the first tutorial dungeon and make sure that killing everything would gain him exactly 1 level.

=== Derived Attributes ===
Derived attributes (such as maxHealth, maxMana, etc.) are now effectively derived from the base attributes. For example, Constitution directly affects the max amount of HPs and Willpower affects the max value of Mana.

The formulas are explicited as static functions inside the RckSettings.cs file.

For example, max health is calculated as the following:<syntaxhighlight lang="csharp">
public static float GetMaxHealthCalculation(int attConstitution, int attStrength)
{
float constitutionModifier = 5.25f;
float strengthModifier = 0.5f;

float maxHealth = ATTRIBUTES_DEF_HEALTH + (attConstitution * constitutionModifier) + (attStrength * strengthModifier);
return maxHealth;
}
</syntaxhighlight>
'''ATTRIBUTES_DEF_HEALTH''' is by default '''1.0f'''.

There are now a lot of derived attributes, whose definitions are all in the RckSettings file. You can obviously add your own as well.

== Sprint Attacks / Skills ==
Sprint Attacks were added as an addition to the Combat System.

They are performed while the player sprints and holds the attack button. For the Demo you can perform sprint attacks while being unarmed or while using a one-handed weapon like a sword or a dagger.

Sprint Attacks are defined in the '''Weapon Charged Attacks''' list, inside the WeaponItem:

[[File:Rck2 13.png|558x558px]]

They should '''always''' stay at Index 1 as the combat system triggers "Attack Type Index 1" on the combination of keys that correspond to "Sprint + Charged Attack".

'''Is Full Body''': is an addition in the 2.0 version that allows you to setup attacks that override the whole character body, as opposed as only the upperbody.

In the same way, you can add new attacks/skills, such as "RIGHT_MOVEMENT + CHARGED_ATTACK" = triggers a specific attack animation.

You can see how the Sprint Attack is triggered in the '''PlayerCombat''' script, under the '''MeleeChargedAttack''' function. In there, by the very same logic, you can create new attacks/skills with different input combinations.

'''Attacks can now have movements properties''', i.e., take over movement. The sprint attack for example locks the player from moving and pushes him forward in conjuction with the animation. This logic is managed by Animation Events put on the FPS version of the animations, you can check the "FPSArms_OneHandedPowerAttackForward" animation to see how it works.

== Other ==
'''AI Aggro Lines:''' AI can now say voice lines when entering in combat. You can set those in the '''AISounds''' component (located on the AI prefab, es. [AI]BandintInFirstDungeon001->GFX).

'''Sneak attacks''': when an NPC is not in combat and he doesn't see the player, dealing physical damage (melee, ranged weapons) will result in critical damage. The modifier is calculated in the RckSettings (''GetSneakDamageMultiplier'').

'''Every UI state can be set to pause the game''' '''or not''' (RckSettings flags).

What's new in the RPG Creation Kit 2

2026-02-05T19:08:23Z

Silvematt: /* Sprint Attacks / Skills */

In this page you'll find an explanation of the new systems and changes that arrived with the release of the '''RPG Creation Kit 2.0'''.

== Show/Hide Demo Files ==
[[File:RCK2 1.png|423x423px]]

The first change to the Editor Tools is the addition of a toggle named '''"Show Demo Files?"'''. When toggled on, the respective Editor (such as "Rck Object Viewer", "Cell View", "Quests", "Rck AI Editor", etc.) will show files related to the Rck Demo. As you can imagine, toggling it off will hide from the lists content related to the demo.

This will be pretty useful when you'll be deep into creating your own content and the Rck items will get in your way as you're trying to find or search for things.

Each asset that can be hidden has now a flag "IS_DEMO_FILE", that will act as the flag that hides/show results:

[[File:Rck 2.png|400x400px]]

So as you'll make new content it will be enough to disable this flag for your own items.

'''You can also set the default value''' for the '''"Show Demo Files?"''' toggle to be on/off whenever you open your project by going in "''Edit->Project Settings-RPG Creation Kit''" and setting the value of the toggle there. Setting it off will make sure that whenever you open a window like the "''Rck AI Editor''" the demo files will be set to be hidden by default.

[[File:Rck2 3.png|400x400px]]

== Toolbar Functions ==
[[File:Rck2 5.png|578x578px]]

The main toolbar, located in the upper part of the Editor, will now have three more buttons related to the RPG Creation Kit:

* '''Load Last Save:''' allows you to Start playing in the Editor and automatically loads the latest savegame (or autosave) you have. It's an incredibly helpful tool that allows you to quickly jump in game to view your edits.
* '''Load Last Cell''': does the opposite. It loads the last cell that you've loaded via the Cell View or Cell Map View. It's best used along with the Load Last Save button t.
* '''Adjust Time Of Day (ToD) Preview:''' is a slider that sets the Time of Day for your selected "Time of Day Sky Material" (set in the Project Settings). It sets the "currentTime" value in the Sky's material and it updates the scene lighting in base of this value. It's useful to preview a Cell (or many cells) in the Editor at any given time of the day.

== Time of Day ==
The Time of Day feature adds the concept of time inside of the RCK.

Days consist of 24hrs and there's currently no convention for Days/Months/Years, which is something that can be extended from this system.

A GameObject named '''"TimeOfDayManager'''" has been added to the _WorldLoader_ scene, and it has a component with the same name as the Object that is, in fact, the manager of the time system.

[[File:Rck2 6.png|560x560px]]

* '''Current Time''' [0-24]: explicit the current time of the day. This can be set when the game starts, when a save game loads, and it can be arbitrarily set from other scripts. For example, the script "JustAnotherDeliveryStage10".
* '''Hours''' and '''Minutes''': are derived from the Current Time, and they're useful for you to read in order to create dynamic scenarios based on the current time (see next section "''Dynamic Responses to Current Time''") or to display the current time on the UI.
* '''Current Time Scale''': dictates ''how quickly'' time passes. The formula that runs on Update is is:<syntaxhighlight lang="csharp">
SetTime(currentTime + (currentTimeScale * Time.deltaTime));
</syntaxhighlight>A Time Scale of 1 means that one hour passes every second, so for the default value of 0.05, a full day (24hrs) 480 seconds or 8 minutes. You can also set this at runtime whenever you want, although runtime changes are not saved on the save-file (the value you set in the inspector will be loaded when a savegame is loaded).
*'''Skybox Material''': is a reference to the material that you're using in your world. If you want a different Skybox material you'll have to change this reference (to update it in game) and the reference in Project Settings (to allow the ToD slider to correctly preview the skybox in the editor). In the RCK default configuration there is only one Skybox Material that contains 3 Cubemaps that represent Day, Dusk, Night, that are blended in base of the Current Time Value. You can swap the Skybox Material reference if you want, even during runtime, but you'll also have to do so in the [https://docs.unity3d.com/ScriptReference/RenderSettings-skybox.html RenderSettings].

The next values "Sun & Moon" allows you to fine-control the lighting of your scenes as time passes.

* '''Sun Light:''' is a reference to your main Directional Light (sun) that is also in the _WorldLoader_ scene.
* '''Sun Color:''' is the sun's color.
* '''Sun Intensity:''' allows you to set a curve that controls the intensity of the Sun's light as time goes by. So the value at the beginning of the curve would be the sun's intensity at hour 0:00, while the last value is at the very last minute of the day 23:59.
* '''Ambient Color/Intensity:''' allows you to define gradients that controls the [https://docs.unity3d.com/speedtree-modeler/manual/light-object-reference.html ambience] of your scene at runtime. The gradient is also distributed over the currentTime, so you can have dark ambient settings at night and more light ones during the day.
* '''Fog Color/Density:''' allows you to do the same but to the fog setting of your scene.

The values set in here are to be thought as the "default" values.

'''However,''' you probably want control over ambience/fog for '''each [[worldspace]]''' and even for '''each [[cell]]'''.

[[File:Rck2 7.png|475x475px]]

The Worldspace data has also been given these properties, to allow you to customize your worldspaces as you wish.

* '''Global_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS:''' if set to true it will mean that the default 'Time of Day Manager' values we've set previously for Ambient/Fog will be '''overridden''' by the Worldspace when the player will be in that worldspace.
* The rest of the values are the same as explained previously, with some additional tweaks such as fog start/end and modes.

The same concept applies for individual Cells:

[[File:Rck2 9.png|581x581px]]

* '''Local_Override_ToD_Setting:''' determines whether to inherit the <code>TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS</code> setting from the parent Worldspace or use the local boolean <code>Local_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS</code> defined on this Cell. If Local_Override is false, <code>Local_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS has obviously no effect.</code>
* The rest of the values are the same as explained previously.

So the idea is that you would have ambient/fog responsive to the Time of Day (set at a worldspace level) for exterior worlds, and you can decide to override it for interiors (such as always-dark dungeons). But, you can also make interiors (such as houses with windows) whose Ambient lighting responds to time of day.

== Dynamic Responses to Current Time ==
This whole Time System goes well together with the [[Scripting|Scripting System]] of the RPG Creation Kit and in general with the component-based architecture of Unity.

We can query at anytime the Current Time of day, also as (Hour::Minute) and dynamically make things happen, or prevent things from happening. This allows you to create content that depends on time of day, such as dungeons that are only accessible at night, events that can only happen at a certain time of the day, and this also allows for Dynamic NPCs routines.

In the RCK demo we have 5 examples:

* '''NPCs equip torches at night.''' [RckAI_EquipTorchAtNight.cs]
* '''Shops in the city close at night.''' [CityInterior_LockShopsAtNight.cs]
* '''The "Killing Monsters" quest can be only completed during the night (22:00 - 05:00), because the door entrance will be locked during the day''' [Virrihael_LockUnlockVampiresDungeon.cs].
* '''Merchants in the City simulate stop working at night and simulate going in their houses''' [CityInterior_StallOwnersGoToSleep.cs].
* '''The windows of the houses in the city will be lit at night''' [CityInterior_TurnHouseLightsOn.cs].

Let's see the NPCs equip torches at night example.

You can attach the '''RckAI_EquipTorchAtNight''' component to any NPC prefab you have. Such as "CityGuard004" shown below.

[[File:Rck2 10.png|537x537px]]

This component acts as a "manager" or "controller" for the NPC actions that have to depend on time.

The logic for this example is very simple, if the CurrentTime is greater or equal of what we consider the start of the day (dayStartHour), and the CurrentTime is lesser than what we consider the start of the night (nightStartHour), we should not have a torch equipped.

Otherwise, we should equip a torch. This simple logic is present in the script "RckAI_EquipTorchAtNight", that subscribes to listen to '''OnHourChanges''' event.

So everytime there's an hour change we can run the check to equip/unequip the torch.<syntaxhighlight lang="csharp" line="1" start="1">
public void HandleOnHourChange(int curHour)
{
if (ai == null || ai.equipment == null || ai.isInOfflineMode || !ai.isAlive)
return;

bool isTorchEquipped = ai.equipment.currentTorchInHand != null;

// Equip torch logic
if (curHour >= dayStartHour && curHour < nightStartHour)
{
if (isTorchEquipped)
ai.equipment.Unequip(EquipmentSlots.LHand);
}
else if (!isTorchEquipped)
{
var torch = ai.inventory.GetItem("ITorch001");
if (torch != null)
ai.equipment.Equip(torch);
}
}
</syntaxhighlight>You can also subscribe functions to the '''onMinuteChanges''' or '''onTimeChanges''' to have more granular control.

The Scripts are placed on the most suitable GameObject you can think of:

* For RckAI Equip Torch, we place it on the NPC itself.
* For the Door that has to be locked at night, we could place it on the door itself. In my case I prefer to have a "TIME_DEPENDENT_SCRIPTS" GameObject in each Cell, so it will be attached to that game object.
* Same thing for both the houses window's light logic and merchants.

This idea is the whole foundation to build proper '''NPCs Schedules''', that I wish to create and formalize formalized in dedicated assets in a future update.

== XP, Leveling & New Attributes System ==
The Attributes System has been reworked to actually influence in-game actions, for both the player, NPCs and Creatures.

In addition to that, XP and Levels are now a thing. The player can earn XP by killing monsters, completing quests or via [[Scripting]], and also [[Events And Consequences|Events & Consequences]]. As you could expect, the player levels up and he's granted attributes points to improve his attributes. RckAI (and derived) also have a level now, that is defined by their attributes (the more the sum of the attributes values, the greater the level) and the level of the AI is used to compute the XP reward on kill.

Let's see how this is managed:

=== Default Values ===
The first thing that you should know are '''default values.'''

'''For the Player''', these are set in the RckSettings.cs file, under the name of '''<code>PLAYER_ATTRIBUTES_DEFAULT_X</code>'''where "X" is the attribute short name. By default all values are set to 25.

'''For the AI''' (when created via the RckAI Editor) they will have the values of the attributes of the '''RckAI_Prefab''' (located in your project).

=== Player XP and Level Up ===
The XP "curve" to level up is defined as a function the '''RckSettings''' file, under the name of "'''GetNextLevelXPValue(uint level)'''"''',''' and stands as the following:<syntaxhighlight lang="csharp" line="1">
// Calculates the XP needed to reach the given level
public static ulong GetNextLevelXPValue(uint level)
{
ulong xp = level * level * XP_NEXT_LEVEL_SCALING;
return xp;
}
</syntaxhighlight>So the value returned by this function is the '''amount of XP needed for a level up'''. This amount depends on the player's level.

You can of course change and tweak this function as much as you want.

=== Player Attributes Point per level ===
Regarding the player's level up, the RckSettings also defines these constants you may want to tweak:<syntaxhighlight lang="csharp">
public static float LEVELLING_UP_ALERT_MESSAGE_DURATION = 5;
public static uint LEVELLING_POINTS_PER_LEVEL = 5; // 5 attributes points per level
public static bool LEVELLING_LEVEL_2_SKILL_TUTORIAL_ENABLED = true;
</syntaxhighlight>

=== AI Level and XP Awarded On Kill ===
The AI level is automatically set while you tweak the AI's Attributes in the "RckAI Editor".

The level is calculated in base of a constant set in the RckSettings:<syntaxhighlight lang="csharp">
public static uint LEVELLING_AI_ATTRIBUTES_POINTS_PER_LEVEL = 5;
</syntaxhighlight>Every '''LEVELLING_AI_ATTRIBUTES_POINTS_PER_LEVEL''' (value) gave to the AI increases the AI level by 1.

AI Level is then used to calculate XP Reward:<syntaxhighlight lang="csharp">
public static ulong CalculateXPGainedOnAIKill(uint aiLevel)
{
ulong xp = aiLevel * XP_GAINED_ON_AI_KILL_BASE;
return xp;
}
</syntaxhighlight>You can edit "XP_GAINED_ON_KILL_BASE" default value as you wish.

The value returned by this function is also multiplied by the '''XpMultiplier''' that you can set for each AI:

[[File:Rck2 12.png|634x634px]]

Thanks to the '''Xp Mult''' I was able to tweak the value for all the AI the player would meet in the first tutorial dungeon and make sure that killing everything would gain him exactly 1 level.

=== Derived Attributes ===
Derived attributes (such as maxHealth, maxMana, etc.) are now effectively derived from the base attributes. For example, Constitution directly affects the max amount of HPs and Willpower affects the max value of Mana.

The formulas are explicited as static functions inside the RckSettings.cs file.

For example, max health is calculated as the following:<syntaxhighlight lang="csharp">
public static float GetMaxHealthCalculation(int attConstitution, int attStrength)
{
float constitutionModifier = 5.25f;
float strengthModifier = 0.5f;

float maxHealth = ATTRIBUTES_DEF_HEALTH + (attConstitution * constitutionModifier) + (attStrength * strengthModifier);
return maxHealth;
}
</syntaxhighlight>
'''ATTRIBUTES_DEF_HEALTH''' is by default '''1.0f'''.

There are now a lot of derived attributes, whose definitions are all in the RckSettings file. You can obviously add your own as well.

== Sprint Attacks / Skills ==
Sprint Attacks were added as an addition to the Combat System.

They are performed while the player sprints and holds the attack button. For the Demo you can perform sprint attacks while being unarmed or while using a one-handed weapon like a sword or a dagger.

Sprint Attacks are defined in the '''Weapon Charged Attacks''' list, inside the WeaponItem:

[[File:Rck2 13.png|558x558px]]

They should '''always''' stay at Index 1 as the combat system triggers "Attack Type Index 1" on the combination of keys that correspond to "Sprint + Charged Attack".

'''Is Full Body''': is an addition in the 2.0 version that allows you to setup attacks that override the whole character body, as opposed as only the upperbody.

In the same way, you can add new attacks/skills, such as "RIGHT_MOVEMENT + CHARGED_ATTACK" = triggers a specific attack animation.

You can see how the Sprint Attack is triggered in the '''PlayerCombat''' script, under the '''MeleeChargedAttack''' function. In there, by the very same logic, you can create new attacks/skills with different input combinations.

'''Attacks can now have movements properties''', i.e., take over movement. The sprint attack for example locks the player from moving and pushes him forward in conjuction with the animation. This logic is managed by Animation Events put on the FPS version of the animations, you can check the "FPSArms_OneHandedPowerAttackForward" animation to see how it works.

== Other ==
AI Aggro Lines

AI Perception Improvements

Sneak attacks

Every UI state can pause the game or not

File:Rck2 13.png

2026-02-05T19:00:13Z

Silvematt:

rck2_13

What's new in the RPG Creation Kit 2

2026-02-05T18:57:57Z

Silvematt: /* Derived Attributes */

In this page you'll find an explanation of the new systems and changes that arrived with the release of the '''RPG Creation Kit 2.0'''.

== Show/Hide Demo Files ==
[[File:RCK2 1.png|423x423px]]

The first change to the Editor Tools is the addition of a toggle named '''"Show Demo Files?"'''. When toggled on, the respective Editor (such as "Rck Object Viewer", "Cell View", "Quests", "Rck AI Editor", etc.) will show files related to the Rck Demo. As you can imagine, toggling it off will hide from the lists content related to the demo.

This will be pretty useful when you'll be deep into creating your own content and the Rck items will get in your way as you're trying to find or search for things.

Each asset that can be hidden has now a flag "IS_DEMO_FILE", that will act as the flag that hides/show results:

[[File:Rck 2.png|400x400px]]

So as you'll make new content it will be enough to disable this flag for your own items.

'''You can also set the default value''' for the '''"Show Demo Files?"''' toggle to be on/off whenever you open your project by going in "''Edit->Project Settings-RPG Creation Kit''" and setting the value of the toggle there. Setting it off will make sure that whenever you open a window like the "''Rck AI Editor''" the demo files will be set to be hidden by default.

[[File:Rck2 3.png|400x400px]]

== Toolbar Functions ==
[[File:Rck2 5.png|578x578px]]

The main toolbar, located in the upper part of the Editor, will now have three more buttons related to the RPG Creation Kit:

* '''Load Last Save:''' allows you to Start playing in the Editor and automatically loads the latest savegame (or autosave) you have. It's an incredibly helpful tool that allows you to quickly jump in game to view your edits.
* '''Load Last Cell''': does the opposite. It loads the last cell that you've loaded via the Cell View or Cell Map View. It's best used along with the Load Last Save button t.
* '''Adjust Time Of Day (ToD) Preview:''' is a slider that sets the Time of Day for your selected "Time of Day Sky Material" (set in the Project Settings). It sets the "currentTime" value in the Sky's material and it updates the scene lighting in base of this value. It's useful to preview a Cell (or many cells) in the Editor at any given time of the day.

== Time of Day ==
The Time of Day feature adds the concept of time inside of the RCK.

Days consist of 24hrs and there's currently no convention for Days/Months/Years, which is something that can be extended from this system.

A GameObject named '''"TimeOfDayManager'''" has been added to the _WorldLoader_ scene, and it has a component with the same name as the Object that is, in fact, the manager of the time system.

[[File:Rck2 6.png|560x560px]]

* '''Current Time''' [0-24]: explicit the current time of the day. This can be set when the game starts, when a save game loads, and it can be arbitrarily set from other scripts. For example, the script "JustAnotherDeliveryStage10".
* '''Hours''' and '''Minutes''': are derived from the Current Time, and they're useful for you to read in order to create dynamic scenarios based on the current time (see next section "''Dynamic Responses to Current Time''") or to display the current time on the UI.
* '''Current Time Scale''': dictates ''how quickly'' time passes. The formula that runs on Update is is:<syntaxhighlight lang="csharp">
SetTime(currentTime + (currentTimeScale * Time.deltaTime));
</syntaxhighlight>A Time Scale of 1 means that one hour passes every second, so for the default value of 0.05, a full day (24hrs) 480 seconds or 8 minutes. You can also set this at runtime whenever you want, although runtime changes are not saved on the save-file (the value you set in the inspector will be loaded when a savegame is loaded).
*'''Skybox Material''': is a reference to the material that you're using in your world. If you want a different Skybox material you'll have to change this reference (to update it in game) and the reference in Project Settings (to allow the ToD slider to correctly preview the skybox in the editor). In the RCK default configuration there is only one Skybox Material that contains 3 Cubemaps that represent Day, Dusk, Night, that are blended in base of the Current Time Value. You can swap the Skybox Material reference if you want, even during runtime, but you'll also have to do so in the [https://docs.unity3d.com/ScriptReference/RenderSettings-skybox.html RenderSettings].

The next values "Sun & Moon" allows you to fine-control the lighting of your scenes as time passes.

* '''Sun Light:''' is a reference to your main Directional Light (sun) that is also in the _WorldLoader_ scene.
* '''Sun Color:''' is the sun's color.
* '''Sun Intensity:''' allows you to set a curve that controls the intensity of the Sun's light as time goes by. So the value at the beginning of the curve would be the sun's intensity at hour 0:00, while the last value is at the very last minute of the day 23:59.
* '''Ambient Color/Intensity:''' allows you to define gradients that controls the [https://docs.unity3d.com/speedtree-modeler/manual/light-object-reference.html ambience] of your scene at runtime. The gradient is also distributed over the currentTime, so you can have dark ambient settings at night and more light ones during the day.
* '''Fog Color/Density:''' allows you to do the same but to the fog setting of your scene.

The values set in here are to be thought as the "default" values.

'''However,''' you probably want control over ambience/fog for '''each [[worldspace]]''' and even for '''each [[cell]]'''.

[[File:Rck2 7.png|475x475px]]

The Worldspace data has also been given these properties, to allow you to customize your worldspaces as you wish.

* '''Global_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS:''' if set to true it will mean that the default 'Time of Day Manager' values we've set previously for Ambient/Fog will be '''overridden''' by the Worldspace when the player will be in that worldspace.
* The rest of the values are the same as explained previously, with some additional tweaks such as fog start/end and modes.

The same concept applies for individual Cells:

[[File:Rck2 9.png|581x581px]]

* '''Local_Override_ToD_Setting:''' determines whether to inherit the <code>TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS</code> setting from the parent Worldspace or use the local boolean <code>Local_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS</code> defined on this Cell. If Local_Override is false, <code>Local_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS has obviously no effect.</code>
* The rest of the values are the same as explained previously.

So the idea is that you would have ambient/fog responsive to the Time of Day (set at a worldspace level) for exterior worlds, and you can decide to override it for interiors (such as always-dark dungeons). But, you can also make interiors (such as houses with windows) whose Ambient lighting responds to time of day.

== Dynamic Responses to Current Time ==
This whole Time System goes well together with the [[Scripting|Scripting System]] of the RPG Creation Kit and in general with the component-based architecture of Unity.

We can query at anytime the Current Time of day, also as (Hour::Minute) and dynamically make things happen, or prevent things from happening. This allows you to create content that depends on time of day, such as dungeons that are only accessible at night, events that can only happen at a certain time of the day, and this also allows for Dynamic NPCs routines.

In the RCK demo we have 5 examples:

* '''NPCs equip torches at night.''' [RckAI_EquipTorchAtNight.cs]
* '''Shops in the city close at night.''' [CityInterior_LockShopsAtNight.cs]
* '''The "Killing Monsters" quest can be only completed during the night (22:00 - 05:00), because the door entrance will be locked during the day''' [Virrihael_LockUnlockVampiresDungeon.cs].
* '''Merchants in the City simulate stop working at night and simulate going in their houses''' [CityInterior_StallOwnersGoToSleep.cs].
* '''The windows of the houses in the city will be lit at night''' [CityInterior_TurnHouseLightsOn.cs].

Let's see the NPCs equip torches at night example.

You can attach the '''RckAI_EquipTorchAtNight''' component to any NPC prefab you have. Such as "CityGuard004" shown below.

[[File:Rck2 10.png|537x537px]]

This component acts as a "manager" or "controller" for the NPC actions that have to depend on time.

The logic for this example is very simple, if the CurrentTime is greater or equal of what we consider the start of the day (dayStartHour), and the CurrentTime is lesser than what we consider the start of the night (nightStartHour), we should not have a torch equipped.

Otherwise, we should equip a torch. This simple logic is present in the script "RckAI_EquipTorchAtNight", that subscribes to listen to '''OnHourChanges''' event.

So everytime there's an hour change we can run the check to equip/unequip the torch.<syntaxhighlight lang="csharp" line="1" start="1">
public void HandleOnHourChange(int curHour)
{
if (ai == null || ai.equipment == null || ai.isInOfflineMode || !ai.isAlive)
return;

bool isTorchEquipped = ai.equipment.currentTorchInHand != null;

// Equip torch logic
if (curHour >= dayStartHour && curHour < nightStartHour)
{
if (isTorchEquipped)
ai.equipment.Unequip(EquipmentSlots.LHand);
}
else if (!isTorchEquipped)
{
var torch = ai.inventory.GetItem("ITorch001");
if (torch != null)
ai.equipment.Equip(torch);
}
}
</syntaxhighlight>You can also subscribe functions to the '''onMinuteChanges''' or '''onTimeChanges''' to have more granular control.

The Scripts are placed on the most suitable GameObject you can think of:

* For RckAI Equip Torch, we place it on the NPC itself.
* For the Door that has to be locked at night, we could place it on the door itself. In my case I prefer to have a "TIME_DEPENDENT_SCRIPTS" GameObject in each Cell, so it will be attached to that game object.
* Same thing for both the houses window's light logic and merchants.

This idea is the whole foundation to build proper '''NPCs Schedules''', that I wish to create and formalize formalized in dedicated assets in a future update.

== XP, Leveling & New Attributes System ==
The Attributes System has been reworked to actually influence in-game actions, for both the player, NPCs and Creatures.

In addition to that, XP and Levels are now a thing. The player can earn XP by killing monsters, completing quests or via [[Scripting]], and also [[Events And Consequences|Events & Consequences]]. As you could expect, the player levels up and he's granted attributes points to improve his attributes. RckAI (and derived) also have a level now, that is defined by their attributes (the more the sum of the attributes values, the greater the level) and the level of the AI is used to compute the XP reward on kill.

Let's see how this is managed:

=== Default Values ===
The first thing that you should know are '''default values.'''

'''For the Player''', these are set in the RckSettings.cs file, under the name of '''<code>PLAYER_ATTRIBUTES_DEFAULT_X</code>'''where "X" is the attribute short name. By default all values are set to 25.

'''For the AI''' (when created via the RckAI Editor) they will have the values of the attributes of the '''RckAI_Prefab''' (located in your project).

=== Player XP and Level Up ===
The XP "curve" to level up is defined as a function the '''RckSettings''' file, under the name of "'''GetNextLevelXPValue(uint level)'''"''',''' and stands as the following:<syntaxhighlight lang="csharp" line="1">
// Calculates the XP needed to reach the given level
public static ulong GetNextLevelXPValue(uint level)
{
ulong xp = level * level * XP_NEXT_LEVEL_SCALING;
return xp;
}
</syntaxhighlight>So the value returned by this function is the '''amount of XP needed for a level up'''. This amount depends on the player's level.

You can of course change and tweak this function as much as you want.

=== Player Attributes Point per level ===
Regarding the player's level up, the RckSettings also defines these constants you may want to tweak:<syntaxhighlight lang="csharp">
public static float LEVELLING_UP_ALERT_MESSAGE_DURATION = 5;
public static uint LEVELLING_POINTS_PER_LEVEL = 5; // 5 attributes points per level
public static bool LEVELLING_LEVEL_2_SKILL_TUTORIAL_ENABLED = true;
</syntaxhighlight>

=== AI Level and XP Awarded On Kill ===
The AI level is automatically set while you tweak the AI's Attributes in the "RckAI Editor".

The level is calculated in base of a constant set in the RckSettings:<syntaxhighlight lang="csharp">
public static uint LEVELLING_AI_ATTRIBUTES_POINTS_PER_LEVEL = 5;
</syntaxhighlight>Every '''LEVELLING_AI_ATTRIBUTES_POINTS_PER_LEVEL''' (value) gave to the AI increases the AI level by 1.

AI Level is then used to calculate XP Reward:<syntaxhighlight lang="csharp">
public static ulong CalculateXPGainedOnAIKill(uint aiLevel)
{
ulong xp = aiLevel * XP_GAINED_ON_AI_KILL_BASE;
return xp;
}
</syntaxhighlight>You can edit "XP_GAINED_ON_KILL_BASE" default value as you wish.

The value returned by this function is also multiplied by the '''XpMultiplier''' that you can set for each AI:

[[File:Rck2 12.png|634x634px]]

Thanks to the '''Xp Mult''' I was able to tweak the value for all the AI the player would meet in the first tutorial dungeon and make sure that killing everything would gain him exactly 1 level.

=== Derived Attributes ===
Derived attributes (such as maxHealth, maxMana, etc.) are now effectively derived from the base attributes. For example, Constitution directly affects the max amount of HPs and Willpower affects the max value of Mana.

The formulas are explicited as static functions inside the RckSettings.cs file.

For example, max health is calculated as the following:<syntaxhighlight lang="csharp">
public static float GetMaxHealthCalculation(int attConstitution, int attStrength)
{
float constitutionModifier = 5.25f;
float strengthModifier = 0.5f;

float maxHealth = ATTRIBUTES_DEF_HEALTH + (attConstitution * constitutionModifier) + (attStrength * strengthModifier);
return maxHealth;
}
</syntaxhighlight>
'''ATTRIBUTES_DEF_HEALTH''' is by default '''1.0f'''.

There are now a lot of derived attributes, whose definitions are all in the RckSettings file. You can obviously add your own as well.

== Sprint Attacks / Skills ==

== Class Selection ==

== Other ==
AI Aggro Lines

AI Perception Improvements

Sneak attacks

Every UI state can pause the game or not

What's new in the RPG Creation Kit 2

2026-02-05T18:54:02Z

Silvematt: /* Other */

In this page you'll find an explanation of the new systems and changes that arrived with the release of the '''RPG Creation Kit 2.0'''.

== Show/Hide Demo Files ==
[[File:RCK2 1.png|423x423px]]

The first change to the Editor Tools is the addition of a toggle named '''"Show Demo Files?"'''. When toggled on, the respective Editor (such as "Rck Object Viewer", "Cell View", "Quests", "Rck AI Editor", etc.) will show files related to the Rck Demo. As you can imagine, toggling it off will hide from the lists content related to the demo.

This will be pretty useful when you'll be deep into creating your own content and the Rck items will get in your way as you're trying to find or search for things.

Each asset that can be hidden has now a flag "IS_DEMO_FILE", that will act as the flag that hides/show results:

[[File:Rck 2.png|400x400px]]

So as you'll make new content it will be enough to disable this flag for your own items.

'''You can also set the default value''' for the '''"Show Demo Files?"''' toggle to be on/off whenever you open your project by going in "''Edit->Project Settings-RPG Creation Kit''" and setting the value of the toggle there. Setting it off will make sure that whenever you open a window like the "''Rck AI Editor''" the demo files will be set to be hidden by default.

[[File:Rck2 3.png|400x400px]]

== Toolbar Functions ==
[[File:Rck2 5.png|578x578px]]

The main toolbar, located in the upper part of the Editor, will now have three more buttons related to the RPG Creation Kit:

* '''Load Last Save:''' allows you to Start playing in the Editor and automatically loads the latest savegame (or autosave) you have. It's an incredibly helpful tool that allows you to quickly jump in game to view your edits.
* '''Load Last Cell''': does the opposite. It loads the last cell that you've loaded via the Cell View or Cell Map View. It's best used along with the Load Last Save button t.
* '''Adjust Time Of Day (ToD) Preview:''' is a slider that sets the Time of Day for your selected "Time of Day Sky Material" (set in the Project Settings). It sets the "currentTime" value in the Sky's material and it updates the scene lighting in base of this value. It's useful to preview a Cell (or many cells) in the Editor at any given time of the day.

== Time of Day ==
The Time of Day feature adds the concept of time inside of the RCK.

Days consist of 24hrs and there's currently no convention for Days/Months/Years, which is something that can be extended from this system.

A GameObject named '''"TimeOfDayManager'''" has been added to the _WorldLoader_ scene, and it has a component with the same name as the Object that is, in fact, the manager of the time system.

[[File:Rck2 6.png|560x560px]]

* '''Current Time''' [0-24]: explicit the current time of the day. This can be set when the game starts, when a save game loads, and it can be arbitrarily set from other scripts. For example, the script "JustAnotherDeliveryStage10".
* '''Hours''' and '''Minutes''': are derived from the Current Time, and they're useful for you to read in order to create dynamic scenarios based on the current time (see next section "''Dynamic Responses to Current Time''") or to display the current time on the UI.
* '''Current Time Scale''': dictates ''how quickly'' time passes. The formula that runs on Update is is:<syntaxhighlight lang="csharp">
SetTime(currentTime + (currentTimeScale * Time.deltaTime));
</syntaxhighlight>A Time Scale of 1 means that one hour passes every second, so for the default value of 0.05, a full day (24hrs) 480 seconds or 8 minutes. You can also set this at runtime whenever you want, although runtime changes are not saved on the save-file (the value you set in the inspector will be loaded when a savegame is loaded).
*'''Skybox Material''': is a reference to the material that you're using in your world. If you want a different Skybox material you'll have to change this reference (to update it in game) and the reference in Project Settings (to allow the ToD slider to correctly preview the skybox in the editor). In the RCK default configuration there is only one Skybox Material that contains 3 Cubemaps that represent Day, Dusk, Night, that are blended in base of the Current Time Value. You can swap the Skybox Material reference if you want, even during runtime, but you'll also have to do so in the [https://docs.unity3d.com/ScriptReference/RenderSettings-skybox.html RenderSettings].

The next values "Sun & Moon" allows you to fine-control the lighting of your scenes as time passes.

* '''Sun Light:''' is a reference to your main Directional Light (sun) that is also in the _WorldLoader_ scene.
* '''Sun Color:''' is the sun's color.
* '''Sun Intensity:''' allows you to set a curve that controls the intensity of the Sun's light as time goes by. So the value at the beginning of the curve would be the sun's intensity at hour 0:00, while the last value is at the very last minute of the day 23:59.
* '''Ambient Color/Intensity:''' allows you to define gradients that controls the [https://docs.unity3d.com/speedtree-modeler/manual/light-object-reference.html ambience] of your scene at runtime. The gradient is also distributed over the currentTime, so you can have dark ambient settings at night and more light ones during the day.
* '''Fog Color/Density:''' allows you to do the same but to the fog setting of your scene.

The values set in here are to be thought as the "default" values.

'''However,''' you probably want control over ambience/fog for '''each [[worldspace]]''' and even for '''each [[cell]]'''.

[[File:Rck2 7.png|475x475px]]

The Worldspace data has also been given these properties, to allow you to customize your worldspaces as you wish.

* '''Global_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS:''' if set to true it will mean that the default 'Time of Day Manager' values we've set previously for Ambient/Fog will be '''overridden''' by the Worldspace when the player will be in that worldspace.
* The rest of the values are the same as explained previously, with some additional tweaks such as fog start/end and modes.

The same concept applies for individual Cells:

[[File:Rck2 9.png|581x581px]]

* '''Local_Override_ToD_Setting:''' determines whether to inherit the <code>TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS</code> setting from the parent Worldspace or use the local boolean <code>Local_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS</code> defined on this Cell. If Local_Override is false, <code>Local_TOD_ENABLE_SKYBOX_AND_LIGHTING_EDITS has obviously no effect.</code>
* The rest of the values are the same as explained previously.

So the idea is that you would have ambient/fog responsive to the Time of Day (set at a worldspace level) for exterior worlds, and you can decide to override it for interiors (such as always-dark dungeons). But, you can also make interiors (such as houses with windows) whose Ambient lighting responds to time of day.

== Dynamic Responses to Current Time ==
This whole Time System goes well together with the [[Scripting|Scripting System]] of the RPG Creation Kit and in general with the component-based architecture of Unity.

We can query at anytime the Current Time of day, also as (Hour::Minute) and dynamically make things happen, or prevent things from happening. This allows you to create content that depends on time of day, such as dungeons that are only accessible at night, events that can only happen at a certain time of the day, and this also allows for Dynamic NPCs routines.

In the RCK demo we have 5 examples:

* '''NPCs equip torches at night.''' [RckAI_EquipTorchAtNight.cs]
* '''Shops in the city close at night.''' [CityInterior_LockShopsAtNight.cs]
* '''The "Killing Monsters" quest can be only completed during the night (22:00 - 05:00), because the door entrance will be locked during the day''' [Virrihael_LockUnlockVampiresDungeon.cs].
* '''Merchants in the City simulate stop working at night and simulate going in their houses''' [CityInterior_StallOwnersGoToSleep.cs].
* '''The windows of the houses in the city will be lit at night''' [CityInterior_TurnHouseLightsOn.cs].

Let's see the NPCs equip torches at night example.

You can attach the '''RckAI_EquipTorchAtNight''' component to any NPC prefab you have. Such as "CityGuard004" shown below.

[[File:Rck2 10.png|537x537px]]

This component acts as a "manager" or "controller" for the NPC actions that have to depend on time.

The logic for this example is very simple, if the CurrentTime is greater or equal of what we consider the start of the day (dayStartHour), and the CurrentTime is lesser than what we consider the start of the night (nightStartHour), we should not have a torch equipped.

Otherwise, we should equip a torch. This simple logic is present in the script "RckAI_EquipTorchAtNight", that subscribes to listen to '''OnHourChanges''' event.

So everytime there's an hour change we can run the check to equip/unequip the torch.<syntaxhighlight lang="csharp" line="1" start="1">
public void HandleOnHourChange(int curHour)
{
if (ai == null || ai.equipment == null || ai.isInOfflineMode || !ai.isAlive)
return;

bool isTorchEquipped = ai.equipment.currentTorchInHand != null;

// Equip torch logic
if (curHour >= dayStartHour && curHour < nightStartHour)
{
if (isTorchEquipped)
ai.equipment.Unequip(EquipmentSlots.LHand);
}
else if (!isTorchEquipped)
{
var torch = ai.inventory.GetItem("ITorch001");
if (torch != null)
ai.equipment.Equip(torch);
}
}
</syntaxhighlight>You can also subscribe functions to the '''onMinuteChanges''' or '''onTimeChanges''' to have more granular control.

The Scripts are placed on the most suitable GameObject you can think of:

* For RckAI Equip Torch, we place it on the NPC itself.
* For the Door that has to be locked at night, we could place it on the door itself. In my case I prefer to have a "TIME_DEPENDENT_SCRIPTS" GameObject in each Cell, so it will be attached to that game object.
* Same thing for both the houses window's light logic and merchants.

This idea is the whole foundation to build proper '''NPCs Schedules''', that I wish to create and formalize formalized in dedicated assets in a future update.

== XP, Leveling & New Attributes System ==
The Attributes System has been reworked to actually influence in-game actions, for both the player, NPCs and Creatures.

In addition to that, XP and Levels are now a thing. The player can earn XP by killing monsters, completing quests or via [[Scripting]], and also [[Events And Consequences|Events & Consequences]]. As you could expect, the player levels up and he's granted attributes points to improve his attributes. RckAI (and derived) also have a level now, that is defined by their attributes (the more the sum of the attributes values, the greater the level) and the level of the AI is used to compute the XP reward on kill.

Let's see how this is managed:

=== Default Values ===
The first thing that you should know are '''default values.'''

'''For the Player''', these are set in the RckSettings.cs file, under the name of '''<code>PLAYER_ATTRIBUTES_DEFAULT_X</code>'''where "X" is the attribute short name. By default all values are set to 25.

'''For the AI''' (when created via the RckAI Editor) they will have the values of the attributes of the '''RckAI_Prefab''' (located in your project).

=== Player XP and Level Up ===
The XP "curve" to level up is defined as a function the '''RckSettings''' file, under the name of "'''GetNextLevelXPValue(uint level)'''"''',''' and stands as the following:<syntaxhighlight lang="csharp" line="1">
// Calculates the XP needed to reach the given level
public static ulong GetNextLevelXPValue(uint level)
{
ulong xp = level * level * XP_NEXT_LEVEL_SCALING;
return xp;
}
</syntaxhighlight>So the value returned by this function is the '''amount of XP needed for a level up'''. This amount depends on the player's level.

You can of course change and tweak this function as much as you want.

=== Player Attributes Point per level ===
Regarding the player's level up, the RckSettings also defines these constants you may want to tweak:<syntaxhighlight lang="csharp">
public static float LEVELLING_UP_ALERT_MESSAGE_DURATION = 5;
public static uint LEVELLING_POINTS_PER_LEVEL = 5; // 5 attributes points per level
public static bool LEVELLING_LEVEL_2_SKILL_TUTORIAL_ENABLED = true;
</syntaxhighlight>

=== AI Level and XP Awarded On Kill ===
The AI level is automatically set while you tweak the AI's Attributes in the "RckAI Editor".

The level is calculated in base of a constant set in the RckSettings:<syntaxhighlight lang="csharp">
public static uint LEVELLING_AI_ATTRIBUTES_POINTS_PER_LEVEL = 5;
</syntaxhighlight>Every '''LEVELLING_AI_ATTRIBUTES_POINTS_PER_LEVEL''' (value) gave to the AI increases the AI level by 1.

AI Level is then used to calculate XP Reward:<syntaxhighlight lang="csharp">
public static ulong CalculateXPGainedOnAIKill(uint aiLevel)
{
ulong xp = aiLevel * XP_GAINED_ON_AI_KILL_BASE;
return xp;
}
</syntaxhighlight>You can edit "XP_GAINED_ON_KILL_BASE" default value as you wish.

The value returned by this function is also multiplied by the '''XpMultiplier''' that you can set for each AI:

[[File:Rck2 12.png|634x634px]]

Thanks to the '''Xp Mult''' I was able to tweak the value for all the AI the player would meet in the first tutorial dungeon and make sure that killing everything would gain him exactly 1 level.

=== Derived Attributes ===
Derived attributes (such as maxHealth, maxMana, etc.) are now effectively derived from the base attributes. For example, Constitution directly affects the max amount of HPs and Willpower affects the max value of Mana.

You can look at the '''EntityAttributes.CalculateFromAttributes''' function inside the EntityAttributes.cs script to see how these are applied.

== Sprint Attacks / Skills ==

== Class Selection ==

== Other ==
AI Aggro Lines

AI Perception Improvements

Sneak attacks

Every UI state can pause the game or not

File:Rck2 12.png

2026-02-05T18:52:54Z

Silvematt:

rck2_12

What's new in the RPG Creation Kit 2

2026-02-05T18:23:45Z

Silvematt: /* Dynamic Responses to Current Time */

File:Rck2 10.png

2026-02-05T18:09:38Z

Silvematt:

rck2_10

What's new in the RPG Creation Kit 2

2026-02-05T18:04:03Z

Silvematt:

File:Rck2 9.png

2026-02-05T17:56:58Z

Silvematt:

rck2_9

File:Rck2 8.png

2026-02-05T17:51:42Z

Silvematt:

rck2_8

What's new in the RPG Creation Kit 2

2026-02-05T17:51:19Z

Silvematt:

File:Rck2 7.png

2026-02-05T17:45:13Z

Silvematt:

rck2_7

What's new in the RPG Creation Kit 2

2026-02-05T17:23:42Z

Silvematt:

File:Rck2 6.png

2026-02-05T17:15:23Z

Silvematt:

rck2_6

What's new in the RPG Creation Kit 2

2026-02-05T17:12:05Z

Silvematt: /* Show/Hide Demo Files */

== Show/Hide Demo Files ==
[[File:RCK2 1.png|423x423px]]

The first change to the Editor Tools is the addition of a toggle named '''"Show Demo Files?"'''. When toggled on, the respective Editor (such as "Rck Object Viewer", "Cell View", "Quests", "Rck AI Editor", etc.) will show files related to the Rck Demo. As you can imagine, toggling it off will hide from the lists content related to the demo.

This will be pretty useful when you'll be deep into creating your own content and the Rck items will get in your way as you're trying to find or search for things.

Each asset that can be hidden has now a flag "IS_DEMO_FILE", that will act as the flag that hides/show results:

[[File:Rck 2.png|400x400px]]

So as you'll make new content it will be enough to disable this flag for your own items.

'''You can also set the default value''' for the '''"Show Demo Files?"''' toggle to be on/off whenever you open your project by going in "''Edit->Project Settings-RPG Creation Kit''" and setting the value of the toggle there. Setting it off will make sure that whenever you open a window like the "''Rck AI Editor''" the demo files will be set to be hidden by default.

[[File:Rck2 3.png|400x400px]]

== Toolbar Functions ==
[[File:Rck2 5.png|578x578px]]

The main toolbar, located in the upper part of the Editor, will now have three more buttons related to the RPG Creation Kit:

* '''Load Last Save:''' allows you to Start playing in the Editor and automatically loads the latest savegame (or autosave) you have. It's an incredibly helpful tool that allows you to quickly jump in game to view your edits.
* '''Load Last Cell''': does the opposite. It loads the last cell that you've loaded via the Cell View or Cell Map View. It's best used along with the Load Last Save button t.
* '''Adjust Time Of Day (ToD) Preview:''' is a slider that sets the Time of Day for your selected "Time of Day Sky Material" (set in the Project Settings). It sets the "currentTime" value in the Sky's material and it updates the scene lighting in base of this value. It's useful to preview a Cell (or many cells) in the Editor at any given time of the day.

== Time of Day ==

== NPCs routines ==
== XP, Leveling & New Attributes System ==
== Sprint Attacks / Skills ==

== Class Selection ==

== Other ==
AI Aggro Lines

AI Perception Improvements

Sneak attacks

Every UI state can pause the game or not

File:Rck2 5.png

2026-02-05T17:04:38Z

Silvematt:

rck2_5

File:Rck2 4.png

2026-02-05T17:02:18Z

Silvematt:

rck2_4

File:Rck2 3.png

2026-02-05T17:00:49Z

Silvematt:

rck2_3

File:Rck 2.png

2026-02-05T16:57:17Z

Silvematt:

rck_2

File:RCK2 1.png

2026-02-05T16:54:58Z

Silvematt:

RCK2_1

What's new in the RPG Creation Kit 2

2026-02-05T08:51:42Z

Silvematt: /* Show/Hide Demo Files */

== Show/Hide Demo Files ==
.

== Toolbar Functions ==

== Time of Day ==

== NPCs routines ==
== XP, Leveling & New Attributes System ==
== Sprint Attacks / Skills ==

== Class Selection ==

== Other ==
AI Aggro Lines

AI Perception Improvements

Sneak attacks

Every UI state can pause the game or not

What's new in the RPG Creation Kit 2

2026-02-05T08:51:24Z

Silvematt: Created page with " == Show/Hide Demo Files == . == Toolbar Functions == == Time of Day == == NPCs routines == . == XP, Leveling & New Attributes System == . == Sprint Attacks / Skills == == Class Selection == == Other == AI Aggro Lines AI Perception Improvements Sneak attacks Every UI state can pause the game or not"

== Show/Hide Demo Files ==
.

== Toolbar Functions ==

== Time of Day ==

== NPCs routines ==
.

== XP, Leveling & New Attributes System ==
.

== Sprint Attacks / Skills ==

== Class Selection ==

== Other ==
AI Aggro Lines

AI Perception Improvements

Sneak attacks

Every UI state can pause the game or not

Main Page

2026-02-05T07:00:38Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

''Latest RPG Creation Kit Version: '''2.0.'''''

'''If you're new to the RPG Creation Kit, see the:''' [[:Category:Getting Started|'''Getting Started''']] '''page.'''

'''Newest Tutorials'''
* [https://www.youtube.com/watch?v=llO1YsHaPtM <nowiki>[Video by OctoverseStudios] How to Add a New Race in RCK Using Synty Models</nowiki>]
*[[Converting Materials to HDRP]]
*[[Creating a New Race]]
*[[Creating Your First Worldspace]]
*[[Changing the New Game Starting Location]]
*[[Creating a New Persistent Reference AI]]
*[[Creating a New Looting Point]]
*[[Adding New Animations to NPCs dialogues]]
*[[Creating a New Creature AI]]
*[[Creating a New Melee Weapon]]
*[[Creating a New Armor Item]]

'''Other''' '''Tutorials'''

* [[Items Ownership, Metadata and Stealing]].
*[[Persistent References]]
*[[Mutable|Mutables]]
*[[Interactive Objects]].

[[Special:AllPages|View All Documentation Pages]]

'''Community Made Tutorials'''

The page below contains all the links to videos and articles of tutorials made by the community for the community.

* [[Community Made Tutorials]]

Community Made Tutorials

2025-07-19T19:03:20Z

Silvematt: /* [ARTICLE] Adding Visual Scripting to Quests by Warspawn */

This page contains all the links to videos and articles of tutorials made by the community for the community!

If you wish to make a tutorial about any part of the RPG Creation Kit, please do! And send it on [https://discord.gg/a2W97RtkDx Discord], it will be added to this page.

== [ARTICLE] Adding Visual Scripting to Quests by '''Warspawn''' ==
[https://drive.google.com/file/d/1BUqakOkdCKZYncLJvU9NsUOxDHZk0OYJ/view Link here]

== [VIDEO] Armor Tutorial for the RPG Creation Kit by '''Schaken-Mods''' ==
[https://www.youtube.com/watch?v=kA92OYAwUPs&ab_channel=Schaken Link here]
== [VIDEO] AI Pathing by '''Schaken-Mods''' ==
[https://www.youtube.com/watch?v=sfkN9_GTzOI Link here]
== [VIDEO] How To Create Consumable Items by '''Schaken-Mods''' ==
[https://www.youtube.com/watch?v=9w-Lc5rpRuc Link here]
== [VIDEO] How To Make A Misc Item by '''Schaken-Mods''' ==
[https://www.youtube.com/watch?v=En-yD0gx-dE Link here]

== [VIDEO] How to Add a New Race in RCK Using Synty Models by '''OctoverseStudios''' ==
[https://www.youtube.com/watch?v=llO1YsHaPtM Link here]

== [VIDEO] How to create a NPC by '''Warspawn''' ==
'''[https://www.youtube.com/watch?v=NM-__x0Hr0c&feature=youtu.be Link here]'''

== [VIDEO] Creating Custom Armor by '''Warspawn''' ==
[https://www.youtube.com/watch?v=tyNBVsXhm7Y Link here]

Main Page

2025-07-19T19:01:25Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

''Latest RPG Creation Kit Version: '''1.9.'''''

'''If you're new to the RPG Creation Kit, see the:'''

[[:Category:Getting Started|'''Getting Started''']] '''page.'''

'''Newest Tutorials'''

* [https://www.youtube.com/watch?v=llO1YsHaPtM <nowiki>[Video by OctoverseStudios] How to Add a New Race in RCK Using Synty Models</nowiki>]
*[[Converting Materials to HDRP]]
*[[Creating a New Race]]
*[[Creating Your First Worldspace]]
*[[Changing the New Game Starting Location]]
*[[Creating a New Persistent Reference AI]]
*[[Creating a New Looting Point]]
*[[Adding New Animations to NPCs dialogues]]
*[[Creating a New Creature AI]]
*[[Creating a New Melee Weapon]]
*[[Creating a New Armor Item]]

'''Other''' '''Tutorials'''

* [[Items Ownership, Metadata and Stealing]].
*[[Persistent References]]
*[[Mutable|Mutables]]
*[[Interactive Objects]].

[[Special:AllPages|View All Documentation Pages]]

'''Community Made Tutorials'''

The page below contains all the links to videos and articles of tutorials made by the community for the community.

* [[Community Made Tutorials]]

Converting Materials to HDRP

2025-07-17T21:36:50Z

Silvematt: /* Importing the RCK's Project Settings */

In this page I will explain how to correctly import the RPG Creation Kit in a fresh project that uses HDRP, and how to quickly fix all the pink materials references you may have.

== Importing the RCK's Project Settings ==
During [[Installing the RPG Creation Kit|installation]] you'll get prompted with this window, with every checkbox already checked like this:

[[File:U6 5.png|592x592px]]

If you've just created a new HDRP project and yet have to import the RPG Creation Kit, set the overrides as following:

[[File:Cmhdrp 1.png]]

So that the only boxes '''checked are:'''

* '''DynamicsManager.asset'''
* '''EditorBuildSettings.asset'''
* '''NavMeshAreas.asset'''
* '''TagManager.asset'''

And click '''Import'''. The Unity Editor will begin the import process which may take a while.

Once every asset is imported, you'll get the Text Mesh Pro import pop-up, '''import both TMP Essentials and Examples & Extra.'''

== First round of converting ==
Once the RPG Creation Kit has been imported, all the materials will try to fallback to legacy or non-HDRP materials, which will result in the material appearing as pink. If you open any Cell you may be presented with something like this:

[[File:Cmhdrp 2.png|763x763px]]

To start converting materials to HDRP, open on the toolbar '''Window->Rendering->HDRP Wizard.'''

Then scroll at the bottom and click on '''Convert All Built-In Materials to HDRP:'''

[[File:Cmhdrp 3.png]]

This will take sometime.

Once it's done, you'll notice that some materials have been fixed, but some are definitely still pink.

This is because some materials in the RPG Creation Kit use a custom shader. Let's fix this.

== Downloading the ShaderReplacerWindow ==
Head here and download this .cs script: https://drive.google.com/file/d/1-TKydhdZWpO56_65fAdrWQMcgTIMH-Ql/view?usp=drive_link

Once you've downloaded it, you need to import it in your project.

'''The important thing is that it has to sit in a folder named "Editor", you cannot just drop it anywhere.'''

For example, you can create an "Editor" folder in the root of your project's Asset folder, like this:

[[File:Cmhdrp 5.png]]

'''So it's Assets/Editor/ShaderReplacerWindow.'''

Once you've done that, the toolbar should have '''RPG Creation Kit->Rendering Pipelines->Shader Replacer.'''

[[File:Cmhdrp 6.png]]

'''Let's open the Shader Replacer window.'''

[[File:Cmhdrp 7.png|467x467px]]

== Replacing shaders (1/2) ==
We need to do two rounds of replacing:

'''First: set "Find Shader" to be "StandardDoubleSided"'''

[[File:Cmhdrp 8.png|830x830px]]

'''Second: set "Replace With" to be "Standard":'''

[[File:Cmhdrp 9.png|832x832px]]

Once this is set, click on the '''Fix All (Replace Shader)''' button:

[[File:Cmhdrp 10.png]]

Then, continue to the next section:

== Replacing Shaders (2/2) ==

'''Now you only need to change the Find Shader again, and set it to "Legacy Shaders/Diffuse".'''

'''Replace With should still be the same "Standard".'''

[[File:Cmhdrp 11.png|870x870px]]

'''Again, click on "Fix All (Replace Shaders).'''

== Final Conversion ==
Open again from the toolbar '''Window->Rendering->HDRP Wizard.'''

Then scroll at the bottom and click on '''Convert All Built-In Materials to HDRP:'''

[[File:Cmhdrp 3.png]]

Now, every material of the RPG Creation Kit should have been correctly converted to HDRP, and you most of the assets will display correctly.

[[File:Cmhdrp 12.png|880x880px]]

'''If you still see some pink assets''', you can manually set its material to standard in the Project Window, and run the '''HDRP Wizard''' conversion again.

File:Cmhdrp 12.png

2025-07-17T21:34:55Z

Silvematt:

cmhdrp_12

Converting Materials to HDRP

2025-07-17T21:34:05Z

Silvematt:

File:Cmhdrp 11.png

2025-07-17T21:31:41Z

Silvematt:

cmhdrp_11

File:Cmhdrp 10.png

2025-07-17T21:28:01Z

Silvematt:

cmhdrp_10

File:Cmhdrp 9.png

2025-07-17T21:27:03Z

Silvematt:

cmhdrp_9

File:Cmhdrp 8.png

2025-07-17T21:25:40Z

Silvematt:

cmhdrp_8

File:Cmhdrp 7.png

2025-07-17T21:23:17Z

Silvematt:

cmhdrp_7

File:Cmhdrp 6.png

2025-07-17T21:21:55Z

Silvematt:

cmhdrp_6

File:Cmhdrp 5.png

2025-07-17T21:20:32Z

Silvematt:

cmhdrp_5

File:Cmhdrp 3.png

2025-07-17T21:14:56Z

Silvematt:

cmhdrp_3

File:Cmhdrp 2.png

2025-07-17T21:13:15Z

Silvematt:

cmhdrp_2

Converting Materials to HDRP

2025-07-17T21:08:59Z

Silvematt: Created page with "In this page I will explain how to correctly import the RPG Creation Kit in a fresh project that uses HDRP, and how to quickly fix all the pink materials references you may have. == Importing the RCK's Project Settings == During installation you'll get prompted with this window, with every checkbox already checked like this: 592x592px If you've just created a new HDRP project and yet have to import the RPG Creatio..."

File:Cmhdrp 1.png

2025-07-17T21:07:10Z

Silvematt:

cmhdrp_1

Main Page

2025-07-17T20:55:21Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

''Latest RPG Creation Kit Version: '''1.9.'''''

'''If you're new to the RPG Creation Kit, see the:'''

[[:Category:Getting Started|'''Getting Started''']] '''page.'''

'''Newest Tutorials'''

* [[Converting Materials to HDRP]]
*[[Creating a New Race]]
*[[Creating Your First Worldspace]]
*[[Changing the New Game Starting Location]]
*[[Creating a New Persistent Reference AI]]
*[[Creating a New Looting Point]]
*[[Adding New Animations to NPCs dialogues]]
*[[Creating a New Creature AI]]
*[[Creating a New Melee Weapon]]
*[[Creating a New Armor Item]]

'''Other''' '''Tutorials'''

* [[Items Ownership, Metadata and Stealing]].
*[[Persistent References]]
*[[Mutable|Mutables]]
*[[Interactive Objects]].

[[Special:AllPages|View All Documentation Pages]]

'''Community Made Tutorials'''

The page below contains all the links to videos and articles of tutorials made by the community for the community.

* [[Community Made Tutorials]]

Creating a New Armor Item

2025-06-05T08:10:41Z

Silvematt: /* Video tutorial by Warspawn */

In this tutorial we are going to see how to add a new [[Armor Item]] for the base meshes of the Human race.

In particular we are going to add an helmet that both the Player and character will be able to equip. The process involves weight painting, which I'll show how to do with Blender (I use Blender 2.81). I'm going to use [https://sketchfab.com/3d-models/great-helm-620ca8f54ce64561829809a8b782e78c this model] on Sketchfab made by [https://sketchfab.com/FrenchBaguette Ole Gunnar Isager].

== Requirements & Premise ==
It is required to use Blender or any other 3D Modelling software of your choice and to download the RPG Creation Kit Basemeshes [https://drive.google.com/file/d/1R5c0DPCGQGky-iy4qfeKzS34mGVoUuYy/view?usp=sharing from this link].

Before going forward I have to do an important premise. In the RPG Creation Kit '''every equipment item must have the same armature of the basemesh.''' I'm going to show you how that is accomplished, but you should understand that every equipment item you make for a specific armature will work '''only with that armature''', so if you download a different 3D model for the Basemesh, unless the armature is the same as the RPG Creation Kit's Basemeshes the equipment item will not be correctly attached.

That means you need to pick an armature and '''stick with it''' for any other character you want the equipment to work with.

== Importing/Exporting in Blender ==
[[File:Cnap 1.png|thumb|The helmet slightly modified, placed on the Basemesh head.]]
The goal is to have the Helmet skinned for the Basemesh armature, and we need to do this for both the Male and Female models.

Let's start with the male, open the file "Base Male Human.blend" and Import the .fbx (or whatever else format you have) and move it near the head of the Basemesh. You may want to make some adjustments because it probably won't perfectly fit at the first try. I suggest you use proportional editing for doing that.

Now press ALT+H to reveal the armature, we need to set the helmet to be a parent of the armature, so click on the helmet, then hold shift and click on the armature and with both selected press CTRL+P and select "With Automatic Weights": Refer to the gif below:

[[File:Cna 2.gif|430x430px]]

And that's it. You can switch to pose mode to see the result. The helmet will move with the head. Notice that "With Automatic Weights" may not work perfectly for more complex objects so you may require to do some manual weight paint.
[[File:Cna 3.png|thumb|The project in Blender before exporting. Notice there is only the armature and helmet in the in red highlighted "Outline".]]
Great, we can export this since we have what we wanted, but before doing that, to save space delete everything else in the blend file to save up space. The head, the upperbody, hands, eyes and everything else is not needed. You should remain with just the armature and the helmet.

We can now export the Helmet as an .fbx, to do that click on File -> Export -> Fbx. Change the export settings to the red highlighted ones and name it "GreatHelmetMale":

[[File:Cna 1.png|601x601px]]

At this point, the helmet is ready to be imported in Unity. But this helmet is set to work only with the Male version of the Basemesh. So what you need to do is to repeat the complete process for the Female basemesh. Once you did that, you should have three files:

* GreatHelmet.fbx (not skinned).
*GreatHelmetMale.fbx (skinned for the Male mesh).
* GreatHelmetFemale.fbx (skinned for the Female mesh).

Once you have those, you can move to the next steps.

== Importing in Unity and creating Prefabs ==
[[File:Cna prefabs 1.gif|thumb|GIF that shows the creation of the Prefabs for the Great Helmet.]]
At this point import all the files in Unity and now we are going to create the prefabs for them.

Drop all three files (GreatHelmet.fbx - GreatHelmetMale.fbx - GreatHelmetFemale.fbx) inside a scene, create the materials and apply them to all three helmets.

After applying the material Prefab "GreatHelmet" in the Hierarchy as it is, then name it "GreatHelmetInWorld".

Open "GreatHelmetMale" and Prefab its child "GreatHelmet", then name it "GreatHelmetMaleSkinned".

Open "GreatHelmetFemale" and Prefab its child "GreatHelmet", then name it "GreatHelmetFemaleSkinned".

''Notice that the Skinned prefabs we are making have the component "'''SkinnedMeshRenderer"'''''<nowiki/>'''.'''

Refer to the gif on the right for visualizing the process.

At this point we can move forward to the last step, which is the actual creation of the [[Items|Item]]. You can delete the GameObjects we've dropped in the scene, we don't need them anymore.

== Creating the Armor Item ==
[[File:Cna iteminworld.gif|thumb|GIF that shows the creation of the [[Item In World]] for the GreatHelmet we are creating.]]
To create a New Armor Item, right click in the Project Window -> Create -> RPG Creation Kit -> Items -> ArmorItem

Name it "''[ARMOR] GreatHelmet''" and leave it for now, we are going to create the '''[[Item In World]]''' first. Drop the Prefab we've just made "GreatHelmetInWorld" in the scene, Reach for the top bar "RPG Creation Kit -> Create New -> Item In World" a window will open.

Drag and drop the "GreatHelmetInWorld" prefab we've just dropped in the scene in the "'''GameObject'''" field, you can edit the other settings as you may wish, I suggest you leave the default ones. Last thing to do is to setting the '''"Item Ref"''' to be the [[Armor Item]] we just created, then click on '''COMPELTE & CLOSE''' and make sure to Update the prefab.

Refer to the gif on the right for visualizing the process.

Great! The last step is to configure the [[Armor Item]], select it and look in the inspector for the "'''Configure Item'''" button, click it and a Window will open.

Set its ID to be '''unique''', I'll have it to be ''GreatHelmet001'' and its name to be ''Great Helmet.''

Look for the upper-right part of the Window, and let's set the:

* '''MaleBipedModel''' to be the ''GreatHelmetMaleSkinned''
* '''FemaleBipedModel''' to be the ''GreatHelmetFemaleSkinned''
* '''Both Items In World''' to be ''GreatHelemtInWorld''

The configure the rest of the settings as you place, '''check "Head" in the BipedObject''' (since we're making an Helmet that will cover the head) and also "'''Hide Hair'''":

[[File:Cnaf1.png|534x534px]]

Click '''OK''' to save, then reach for the topbar and '''UPDATE THE DATABASES''', to do that reach for the top bar "RPG Creation Kit -> Update All Databases".

Ok we've finished!
[[File:Cna 111.png|thumb|Remember to regenerate the GUID of any item you drop in the world.]]
Now you can drop the "''GreatHelmetItemInWorld''" wherever you want it place it. Do it now, I'll drop it in the Cell "Virrihael(0,1)". After dropping it in the scene look in the Inspector for the '''ItemInWorld Component''', right click on the Component's name and select "'''Regenerate GUIDStr'''" that will make that instance of the helmet unique throughout the whole game.

With that out of the way, we can load a savegame from the main menu and reach the point where we dropped the Helmet. You can take it, drop it, equip it and you can make NPCs equip it as well.

⠀

⠀

⠀

⠀
== Final Result ==
[[File:Cnavf 1.png|674x674px]]

[[File:Cnavf 2.png|676x676px]]

[[File:Cnavf 3.png|676x676px]]

== Files and Downloads ==
You can download all the files made in this tutorial [https://drive.google.com/file/d/1-69EfYzsxCxJIfoZFENxjF1WjU1Tv3mC/view?usp=sharing at this link].

Make sure to read the ''LICENSE.txt'' file!

== Video tutorial by Warspawn ==
https://www.youtube.com/watch?v=tyNBVsXhm7Y

Creating a New Armor Item

2025-06-05T08:10:34Z

Silvematt: /* Video tutorial by Warspawn */

Creating a New Armor Item

2025-06-05T08:09:55Z

Silvematt:

Main Page

2025-04-24T08:51:30Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

''Latest RPG Creation Kit Version: '''1.9.'''''

'''If you're new to the RPG Creation Kit, see the:'''

[[:Category:Getting Started|'''Getting Started''']] '''page.'''

'''Newest Tutorials'''

* [[Creating a New Race]]
*[[Creating Your First Worldspace]]
*[[Changing the New Game Starting Location]]
*[[Creating a New Persistent Reference AI]]
*[[Creating a New Looting Point]]
*[[Adding New Animations to NPCs dialogues]]
*[[Creating a New Creature AI]]
*[[Creating a New Melee Weapon]]
*[[Creating a New Armor Item]]

'''Other''' '''Tutorials'''

* [[Items Ownership, Metadata and Stealing]].
*[[Persistent References]]
*[[Mutable|Mutables]]
*[[Interactive Objects]].

[[Special:AllPages|View All Documentation Pages]]

'''Community Made Tutorials'''

The page below contains all the links to videos and articles of tutorials made by the community for the community.

* [[Community Made Tutorials]]

Main Page

2025-04-21T08:24:31Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

''Latest RPG Creation Kit Version: '''1.9.'''''

If you're new to the RPG Creation Kit, see the:

[[:Category:Getting Started|'''Getting Started''']] page.

'''Newest Tutorials'''

* [[Creating a New Race]]
*[[Creating Your First Worldspace]]
*[[Changing the New Game Starting Location]]
*[[Creating a New Persistent Reference AI]]
*[[Creating a New Looting Point]]
*[[Adding New Animations to NPCs dialogues]]
*[[Creating a New Creature AI]]
*[[Creating a New Melee Weapon]]
*[[Creating a New Armor Item]]

'''Other''' '''Tutorials'''

* [[Items Ownership, Metadata and Stealing]].
*[[Persistent References]]
*[[Mutable|Mutables]]
*[[Interactive Objects]].

[[Special:AllPages|View All Documentation Pages]]

'''Community Made Tutorials'''

The page below contains all the links to videos and articles of tutorials made by the community for the community.

* [[Community Made Tutorials]]

Creating a New Race

2025-02-15T14:03:23Z

Silvematt: /* Final Considerations */

[[File:Race 1.png|thumb|The "Human" Race used in the RPG Creation Kit .]]
In this tutorial we'll discuss an important topic you sooner or later will want to face when working with the RPG Creation Kit, which is Races. Before going on, you should have completed the [[:Category:Getting Started|Getting Started]] section, and at least tried to [[Creating a New Armor Item|create a new armor item]] for the default race. These tutorials will give you a proper understanding on how the RPG Creation Kit works so that you should not have any problems following along with this advanced topic.

A Race is essentially a complex humanoid 3D Model that acts as a base for your humanoid characters. Races define:

* '''Basemesh''': the actual 3D Model.
* '''Eye Colors''': set of materials you can use to make your characters eye color different.
* '''Hair Types''': set of 3D Models you can use as hair for your characters.
* '''Blendshapes''': used to deform the basemesh and create different characters.

You want to use a Race when you want the Player Character to be able to use a specific 3D model, or you want an RckAI to have all the functionality the player has like the Equipment System and Character Customization.

For AI that is simpler, meaning they don't need customization, hair or blendshapes, like normal creatures, you should use [[Creating a New Creature AI|Creature AI]].

A Race define both a Male and Female version of that Race, but you can also just create one of them and leaving the other blank if you only need one gender.

== Premises ==
Before we start, as the current RPG Creation Kit Version 1.9, you can create as many Races as you want. However, in order to make sure the Equipment System works correctly you need to follow two strict rules:

# '''All 3D Character Model has to use the same rig.'''
# '''The 3D Character Model mesh has to be split in:'''
## '''Head'''
## '''Torso'''
## '''Arms'''
## '''Hands'''
## '''Legs'''
## '''Feet'''

This is very important, and missing this step will result in your Race probably being playable and usable, but the Equipment system will not work with it correctly.

I recommend to either use the same rig as the Human race we use in the RCK, or to start from scratch by using one of your rig and sticking with it for all of your characters. Bear in mind that also the '''equipment''' '''models''' themselves have to use the same rig, as we've seen in the [[Creating a New Armor Item]] tutorial. If you haven't read that tutorial yet I '''strongly recommend doing it now before proceeding''', and to try to create an equipment Item for the RCK default character before attempting to create a new Race.

In this tutorial I will use a generic 3D Model, with his own rig and with the mesh that is in one piece, so we will see all the steps in order to convert it in a RCK-friendly model. I will use the RCK default character's rig, so I'll need to convert the new 3D Model to be able to use that rig. I'll also use Blender, although if you're familiar with another software the steps should be pretty similar.

First thing I'll need is the RPG Creation Kit Basemeshes's Rig, that you can find [https://drive.google.com/file/d/1R5c0DPCGQGky-iy4qfeKzS34mGVoUuYy/view at this link].

== Step 1: T-Pose, A-Pose? ==
The first problem you may stumble upon is the following: your rig is in A-Pose, but your character is in T-Pose (or vice-versa). Also, you may have both your rig in T-Pose or A-Pose, but they may be a little bit different.

In my case the 3D Model I'm using is in T-Pose, and the rig I want to use is in A-Pose:
[[File:Race 2.png|left|428x428px]]
[[File:Race 3.png|frameless|428x428px]]

As you can see, the rigs are quite different, and the resting pose is as well. This is probably your case too, and it will be the case for every Race you'll want to setup.
So '''the first step''' is to convert the '''resting pose''' of the character to '''match the rig I want to use.'''

Open your new 3D Model character in Blender and let's '''append''' the Rig from the RCK Human basemeshes.

Click on File->Append, then locate the "Base Male Human.blend" file and click on it. Go in the 'Objects' folder and click on "'''Unity compliant skeleton'''". Then, click on the blue '''Append''' button:

[[File:Race 10.png|638x638px]]

You will import only the '''rig''', which is what we're looking for, and you'll be presented with a situation similar to this:

[[File:Race 5.png|643x643px]]

Now, depending on your 3D Character model, the rig may be bigger or smaller, the point is this: while '''in object mode''' we need to scale the '''original character rig''' in order to match in size with the RCK rig we want to use. A good measure is the eyes bones, make them match with your character:
[[File:Race 6.png|left|thumb|Make sure to '''Apply All Transforms''' after resizing.]]
As you can see here, the eyes bone matches with the character, which means the size is correct, and I've also rendered the original rig as black sticks instead of octahedral. This will come handy soon.

'''Once you did this, make sure to click on the character's rig we've just resized and Apply All Transforms by clicking CTRL-A -> Apply All Transforms (while in Object Mode).'''

Now, the objective is to set '''the resting position of our model such that it matches the A-Pose rig we want to use.'''

So now what you need to do select the original character rig (drawn as sticks) and go into pose mode, then, you'll have to move the bones until they match the rig we want to use (now the only one drawn as octahedral).

You should both rotate and move the bones (by pressing G) in order to achieve a correct alignment, especially for the hands and fingers. Do not be afraid to stretch the model if it's needed.

My advice is to work on only one side of the character and then mirror the pose for the other side. You can also use 'X-Axis Mirror' which is super useful.

Apply extra patience to align the fingers of the hand, it's a process you only have to do once and if it's done poorly it will have its consequences later.
[[File:Race 12.png|thumb|348x348px|Hand aligned with the RCK rig, done by rotating and moving the original character rig in pose mode.]]
During my process, I found out that it's better to align the spine and chest first, then the legs and at the very end the arms and hands.

Anyways, here's my finished result:

[[File:Race 13.png|597x597px]]

Now for the last thing to do is to '''apply the original armature, in order to set this pose as the model rest pose.'''

Select your mesh and in the modifiers window apply the armature modifier (of the original rig).

Now we can delete the original rig, nothing should break and the 3d model should keep this pose we've just made.

Last thing is to '''parent the new rig with the mesh''', click on the mesh first, then shift select the armature and press CTRL+P, "With Automatic Weight" should give a good enough result, which you can always modify later.

The hardest and maybe the most annoying part is done!

== Step 2: Splitting the Mesh ==
[[File:Race 14.png|thumb|300x300px|Separating the head.]]
Now we will split the mesh in the 6 sections I've mentioned before:

*'''Head'''
* '''Torso'''
* '''Arms'''
* '''Hands'''
* '''Legs'''
* '''Feet'''

You can very easily do that by going in Edit mode, selecting the vertices of each section, and then click 'P' to separate. Select '''Separate By Selection.'''

Repeat this process for every part, you can use the RCK basemeshes as reference for the split points.

[[File:Gifrace1.gif|left|thumb|'''GIF, CLICK TO VIEW''']]
If your model also have eyes, mouth, tongue, eyelashes, just keep them as separated meshes.

If you want, you can also add blendshapes for the head mesh, in order to be able to create different versions of this model which will allow you to create different NPCs.

This step is optional, but you probably don't want the very same character for different NPCs, so creating different blendshapes that allow you to scale/move the vertices of the head is recommended.

You can always do it later, I'll just create three blendshapes:

'''Eyes Up/Down'''

'''Nose Up/Down'''

'''Lips Up/Down'''

In this way I'll be also able to show you the blendshapes edits in the RCK AI Window later.

Our model is finally ready! For the next step, we'll export the model and import it in the RPG Creation Kit.

.

.

== Step 3: Exporting the model ==
Simply export the 3D Model as an FBX with these settings:

[[File:Race 15.png|834x834px]]

Make sure ''''Selected Objects'''<nowiki/>' is disabled, and use '''FBX Units Scale''' as 'Scaling'.

Then, just import the just exported 'MyNewRace.fbx' and its textures in the RCK.

If you did everything correctly the model will be of the right size, which should be very close to the RCK's default characters in my case:

[[File:Rck 16.png|522x522px]]

'''Also make sure to set the "Animation Type" as 'Humanoid' in the Rig tab of the 3d model imported in Unity.'''

We did the hard part! Let's move on.

== Step 4: Setting up the Character in Unity ==
The next step is to setup the 3D Model to have all the components and sub-objects needed in order to work properly in the RPG Creation Kit. We'll create a prefab that represents the base for all the characters that will use this race.

Search for "CHARACTER_BaseHumanMale" in your Unity Project. Essentially, we'll just mirror the "CHARACTER_BaseHumanMale" components onto our new character.

First of all, I will rename my new 3D Model, now in the scene, "'''CHARACTER_BaseNewRaceMale'''".
[[File:Race20.png|thumb|Process of attaching a mesh to the base character.]]
Secondly, I don't want him to be naked by default, but have an underwear. So what I will do is to '''duplicate the underwear of the default Human, and parent it to the CHARACTER_BaseNewRaceMale.'''

You'll notice that the duplicated underwear model doesn't really move, not even if you try to drag it around, that's because it's attached to the other mesh.

Add a 'AttachToMesh' component to the underwear object we've just duplicated, and set the "Attach To" field to the Legs of the '''CHARACTER_BaseNewRaceMale''' object. Finally, right click on the "Attach To Mesh (Script)" component and select "'''Attach to mesh'''":

If you did Step 1,2,3 correctly, the underwear mesh will correctly attach to the new character:

[[File:Race21.png|600x600px]]

'''Awesome!''' This means every other piece of equipment will correctly attach to the new character, because we've exported and rigged him correctly.

'''Important note: for the majority of equipment pieces you should not have clipping''' (equipment clipping through the character's body), because the way the RCK works is that it will '''hide the body when it's completely covered by the equipment piece'''.

So if we're wearing a cuirass that covers the whole upper body, there's no point in rendering the upperbody underneath it.

However, for some items like the underwear itself, and maybe helmets as well, you don't want to disable the mesh that it is only partially covered by the piece of the equipment item. So the item may clip through the new character body. The reason is simple, the items were originally made for the default character model and no matter how similar your new race model looks, it will be different in some ways. There are many ways to fix this, here are two I'd consider:

# '''Add blendshapes to the equipment piece itself (recommended)''': you can make blendshapes on item, in this case the underwear itself to make it shrink/expand, and move in all directions. In this way, when you attach it to your new character (and any new characters you will create) you'll always be able to modify it and correctly adapt it to the new body. And it will work for how many races you will ever want to add.
# '''Add blendshapes to the body parts themselves:''' you could make blendshapes, for example, on the waist, legs, lower legs, arms, etc, that will shrink the mesh in order for the item mesh to cover the body part appropriately. This probably works as well, but if the race models are different enough it may not work correctly and you'll wish you could move the mesh itself.

It's time to add the components/objects needed for the RPG Creation Kit to correctly recognize the Race. We'll focus on the CHARACTER_BaseNewRaceMale object we have in the scene.

'''First of all, you need an Animator with the Avatar set as your character's new avatar, which is created when you set the 3D Model Rig as Humanoid''', in the .fbx import tab. It should have been added by default by Unity, but if it's not, add it manually.

Next, we'll need some other things:

=== BodyData ===
Click on your CHARACTER_BaseNewRaceMale object, at this point you should just have as components the "Animator" with the character's Avatar. Let's add a '''BodyData''' component and set it up, the properties are pretty self-explanatory, I've added few arrows just to be extra clear:

[[File:Race22.png|649x649px]]

You can keep the Hair Index, Eye Index and Hair as they are, they serve as the 'defaults' for your race. In this case we have no hair and default eye color.

If you want your base character to also have default hair, you can attach the hair mesh the same way you attached the underwear. Bear in mind that your Hair 3d model '''has to be rigged as well, and the process is the very same of [[Creating a New Armor Item|creating any other equipment]],''' it's just that it's hair instead of a helmet!

Once you filled everything, let's move on!

=== AISounds ===
Click on your CHARACTER_BaseNewRaceMale object, at this point you should just have as components the "Animator" and the "BodyData".

Let's add a '''AISounds''' component to it, it will allow you to define sounds that the character will emit when hit by a weapon or when he dies:

[[File:Race23.png|352x352px]]

=== Ragdoll ===
Also add a "Ragdoll (RPG Creation Kit)" component and fill its "Animator" field:

[[File:Race24.png|484x484px]]

We need to define the actual ragdoll, that will allow us to not only allow the character to die via ragdoll, but to '''also define the hitboxes of the character itself''', so that weapons can hit him. We'll do this later, for now let's keep adding the rest of the needed objects and component.

=== HeadPos ===
[[File:Race25.png|thumb|322x322px|HeadPos location in the Character hierarchy.]]
Now we need to add a new object to our character. The "'''HeadPos'''" object is just an empty object placed on the head of the character that has few components on it. It serves the purpose of keeping track of where the head of the Character is, for example, so the player camera can look at that position when he is in dialogue with him

'''You need to place this new object as a child of the Head bone,''' which is under the rig. I underline that it's not the head mesh''', but the head bone.'''

Create a new empty game object and name it exactly '''"HeadPos"''' (without quotes). Look at the image on the right.

Now, we need to add few things to this new HeadPos object:

# '''Set its Tag to be "RPG Creation Kit/Ignore Weapons".'''
# '''Set its Layer to be "NPC".'''
# '''Add a Box Collider component and edit it so that it fits its face.'''
# '''Add a 'AIHeadPos' component.'''

Overall, it should look like this:

[[File:Race27.png|659x659px]]

=== LootingPoint ===
The LootingPoint objects allows the player to loot the character's body when he's dead. It's essentially an empty game object with a CapsuleCollider (defining the area the player has to look at in order to loot) and a script.

Instead of creating it from scratch, you can just duplicate the LootingPoint of the "''CHARACTER_BaseHumanMale''", located in the Hierarchy:

[[File:Race30.png|592x592px]]

Press CTRL+D to duplicate it and move the duplicated object, "LootingPoint_01", to our new character's bone '''hips'''.

It needs to be in the Hips bone because we want the CapsuleCollider to follow the ragdoll when the character falls to the ground.

So your setup should look like this, both the "Looting Point" and "Capsule Collider" need to be disabled by default:

[[File:Race31.png|827x827px]]

Don't worry about the "Test" value as the "Point Name", it will be replaced by the NPC name during runtime.

=== Actual Ragdoll and HitBoxes ===
Let's get back on adding the Ragdoll to our new character.

Click on CHARACTER_BaseNewRaceMale in the Hierarchy, then click on "GameObject -> 3D Object -> Ragdoll" to open the Ragdoll wizard:

[[File:Race41.png|865x865px]]

Next, you'll need to set all the bones as asked by the Create Ragdoll Wizard:
[[File:Race42.png|left|thumb|All bones set.]]

Great, now what should have happened is that Unity automatically added rigidbodies, colliders and joints to these parts. Now we have to do an important step, which is flagging these new colliders as BodyParts.

Select them all at once with CTRL+RIGHT CLICK, first of all you may need to adjust the colliders a little bit to match the 3D model.

Secondly, while '''all are selected you need to do these steps:'''

'''1. Change the objects 'Tag' to "RPG Creation Kit/BodyPart".'''

'''2. Change the objects 'Layer' to "BodyPart",''' if it asks you to change children as well, select "No, this object only"'''.'''

'''3. Add a new "BodyPart" component on the objects.'''

You should have this situation now:

[[File:Race43.png|648x648px]]

Great, we're almost done.

Now you need to select each bone individually and update the '''<nowiki/>'This Body Part'''' field in the '''BodyPart''' we've just added.

For example, on the 'Hips' you want to select "Chest" as body part, on the 'Head', select "Head", etc.

This allows the Kit to scale damage appropriately for each body parts, so you can set damage multipliers.

=== Last things ===
Before going on, we have to do two more things, set the '''Eyes''' and '''Mouth meshes''' of our character as '''child of the 'Head' mesh:'''

[[File:Race45.png]]

If you also have other meshes that should be in the head, like eyeleash or tongue, make sure to set them as child of Head as well.

'''Next, add a 'HeadBlendshapesManager'''' component to the Head mesh itself, and set the "Head Mesh" and "Mouth Mesh" fields appropriately:

[[File:Race47.png|886x886px]]

Leave the rest of the fields empty, we'll talk about them later.

Once you've did that, we've finally finished setting up the character, and we are ready for the next step!

== Step 5: Creating the Race ==
Now it's time to create the actual Race object.

'''Make a prefab of the CHARACTER_BaseNewRaceMale''' object we've worked on. '''Make sure to set the Prefab Transform Position and rotation to be (0,0,0).'''

Also, '''make a prefab of only the 'Eyes' mesh''', and name it something like "'''MyNewRaceEyesDefault".''' You should create a new "Race Eyes" asset, Click on "Create->RPG Creation Kit->Character->New Eyes" and configure it such that the Mesh is the Prefab we've just created.

Next, go inside the Project Window and right click on an empty space. Click on "Create->RPG Creation Kit->Character->New Race" to create a new Race Asset. Name it the name of your race, I'll name it "MyNewRace". Go in the inspector and '''Update the ID to "MyNewRace"''', or any other ID you want to give it.

Then, click on the '''<nowiki/>'Configure Race'''' button, it will bring up the '''Race Editor.'''

In the '''General''' tab, you can set the default attributes for new characters that will use this race.

'''Let's go in BodyData''' and fill some properties. We only have the Male version of this race, so we'll only have to fill that.

'''As "MaleModel"''', set the '''CHARACTER_BaseNewRaceMale prefab''' we've just created.

'''As "Male FPS"''', set the '''"FPS_MaleHuman"''' prefab you'll find in the project window. We'll talk about the FPS Arms later.

'''In 'Eyes Types', add a new Entry and select the eyes you've just created.''' So you don't have a blank list of eyes.

So you should have this situation:

[[File:Race50.png|812x812px]]

In the '''FaceData''' you'll be able to see all the Blendshapes you've created for your head mesh, I have the three I've created:

* '''Eyes Up/Down'''

* '''Nose Up/Down'''

* '''Lips Up/Down'''

Now, click on '''<nowiki/>'SAVE & CLOSE'''' and '''[[Databases|Update All the Databases]],''' to do that, click on the toolbar "RPG Creation Kit -> Update all Databases".

And we're practically done! Let's test the new race now.

== Testing the New Race ==
We'll try to create a new player character that will use this new race.

Open the '''_CharacterCreation_''' scene and highlight the "Character Creation Manager" GameObject.

You'll notice it has a "Character Creation Manager" Component, here we need to add the new Race as a '''Playable Race:'''

[[File:Race51.png|863x863px]]

With this done, now start the game from the main menu and try to change the race, if you did everything correctly everything should work fine:

[[File:Race52.png|758x758px]]

[[File:Race53.png|763x763px]]

'''Likewise, you can now create NPCs using this new race:'''

[[File:Race61.png|785x785px]]

[[File:Race60.png|788x788px]]

== Potential Issues ==
Here I'll list some common issues you may stumble upon:

=== Eyes are looking weird ===
Most likely you're using an Eyes asset from another race. Make sure the Eyes are the ones of your new character.

=== Clipping with Equipment ===
It's likely that when you've created the new character with the new race and went in third person, your character body clipped with the equipment.

Now, we'll discuss this properly in the next chapter "Final Considerations", but the reason why this is happening is because by default the RCK Items do not disable the body underneath it, because it's not really needed for the Demo.

Search for '''"[ARMOR] Leather_Curiass",''' which is the default armor your character has when starting the demo. Then, click on '''Body Options''' for the '''Male Biped Model''', here you will be able to hide body parts when this item is equipped.

[[File:Race62.png|686x686px]]

You can ignore the "Add new Blendshapes" button, it will be used for a feature that will be added in a next update.

This should fix your issue, but if your character is different enough from the default character, you may still face other issues, like the equipment being a bit offset from the body. We'll explore this topic in the next chapter.

=== When the NPCs using the New Race die, the ragdoll is weird/bugged ===
This probably happens because when you made the Ragdoll and Hitboxes, you left one or more overlaps between the body parts. Make sure the colliders are on their own and they do not enter each other, otherwise when your characters go ragdoll there will be a collision to resolve that results in a buggy ragdoll death.

== Final Considerations ==
When you're choosing your 3D models you'll want to use as races in your game, it's not a very good decision to choose models that are too different from each other. You can see this in games like Oblivion and Fallout, although the textures are different, the actual 3D models, especially for the bodies, are all very similar if not the same.

In my case, since I've used MakeHuman to make the original Race, it would have been a good choice for me too keep using that program to create new races, but for this tutorial I've preferred to start from a model that's very similar to what you'll commonly have when downloading a 3D model. We've seen when I've added the underwear mesh, I suggested to add blendshapes to the equipment itself in order to move it and scale it around the new character's body.

So my advice would be sticking with one type of body, changing textures and faces so that you won't have issues with your equipment.

Now, let's return to my character, most of the equipment items fit perfectly, but some do not. In particular, if I try to equip the "Guards" helmet, some of the head will clip out of the helmet, and I just can't hide the head underneath it because it will also hide the eyes that I want the character to be able to see.

As of the current v1.9, there's not an easy fix for this. The only thing you can really do is to adjust your character model in Blender, but this is not a final solution since that adjustment may make another helmet incompatible. That's why it's a good idea to use the very same proportions for all your races. Then, if you want some characters to be taller/smaller than others, you can always scale them afterwards, but making them all the same proportions will ensure all the equipment will be compatible.

However, since I always want to let users do as much as possible, as a next update I'll add a feature that will allow you to edit blendshapes on your equipment items and of your character bodies on a per-item-basis. That means if you have blendshapes that scale the head of your character, you'll be able to define the scale factor when an helmet, for example, is equipped (that would elegantly solve the Guard helmet problem I've explained earlier).

Or, if you have an armor that should be moved a bit forward for a specific race, you'll be able to also set that in the Body Options window (this is the same principle of moving the underwear mesh, but for every possible items that can be equipped at runtime).

Although these will ensure compatibility between different character models, '''still''', you should follow the advice of having similar bodies. So take a good chunk of time to go through all the possible models you could use for races in your game and if you plan on using a software like Daz Genesis, MakeHuman, or any other, it's a good idea to keep using that for all your races.

Creating a New Race

2025-02-15T14:02:58Z

Silvematt: /* Premises */

[[File:Race 1.png|thumb|The "Human" Race used in the RPG Creation Kit .]]
In this tutorial we'll discuss an important topic you sooner or later will want to face when working with the RPG Creation Kit, which is Races. Before going on, you should have completed the [[:Category:Getting Started|Getting Started]] section, and at least tried to [[Creating a New Armor Item|create a new armor item]] for the default race. These tutorials will give you a proper understanding on how the RPG Creation Kit works so that you should not have any problems following along with this advanced topic.

A Race is essentially a complex humanoid 3D Model that acts as a base for your humanoid characters. Races define:

* '''Basemesh''': the actual 3D Model.
* '''Eye Colors''': set of materials you can use to make your characters eye color different.
* '''Hair Types''': set of 3D Models you can use as hair for your characters.
* '''Blendshapes''': used to deform the basemesh and create different characters.

You want to use a Race when you want the Player Character to be able to use a specific 3D model, or you want an RckAI to have all the functionality the player has like the Equipment System and Character Customization.

For AI that is simpler, meaning they don't need customization, hair or blendshapes, like normal creatures, you should use [[Creating a New Creature AI|Creature AI]].

A Race define both a Male and Female version of that Race, but you can also just create one of them and leaving the other blank if you only need one gender.

== Premises ==
Before we start, as the current RPG Creation Kit Version 1.9, you can create as many Races as you want. However, in order to make sure the Equipment System works correctly you need to follow two strict rules:

# '''All 3D Character Model has to use the same rig.'''
# '''The 3D Character Model mesh has to be split in:'''
## '''Head'''
## '''Torso'''
## '''Arms'''
## '''Hands'''
## '''Legs'''
## '''Feet'''

This is very important, and missing this step will result in your Race probably being playable and usable, but the Equipment system will not work with it correctly.

I recommend to either use the same rig as the Human race we use in the RCK, or to start from scratch by using one of your rig and sticking with it for all of your characters. Bear in mind that also the '''equipment''' '''models''' themselves have to use the same rig, as we've seen in the [[Creating a New Armor Item]] tutorial. If you haven't read that tutorial yet I '''strongly recommend doing it now before proceeding''', and to try to create an equipment Item for the RCK default character before attempting to create a new Race.

In this tutorial I will use a generic 3D Model, with his own rig and with the mesh that is in one piece, so we will see all the steps in order to convert it in a RCK-friendly model. I will use the RCK default character's rig, so I'll need to convert the new 3D Model to be able to use that rig. I'll also use Blender, although if you're familiar with another software the steps should be pretty similar.

First thing I'll need is the RPG Creation Kit Basemeshes's Rig, that you can find [https://drive.google.com/file/d/1R5c0DPCGQGky-iy4qfeKzS34mGVoUuYy/view at this link].

== Step 1: T-Pose, A-Pose? ==
The first problem you may stumble upon is the following: your rig is in A-Pose, but your character is in T-Pose (or vice-versa). Also, you may have both your rig in T-Pose or A-Pose, but they may be a little bit different.

In my case the 3D Model I'm using is in T-Pose, and the rig I want to use is in A-Pose:
[[File:Race 2.png|left|428x428px]]
[[File:Race 3.png|frameless|428x428px]]

As you can see, the rigs are quite different, and the resting pose is as well. This is probably your case too, and it will be the case for every Race you'll want to setup.
So '''the first step''' is to convert the '''resting pose''' of the character to '''match the rig I want to use.'''

Open your new 3D Model character in Blender and let's '''append''' the Rig from the RCK Human basemeshes.

Click on File->Append, then locate the "Base Male Human.blend" file and click on it. Go in the 'Objects' folder and click on "'''Unity compliant skeleton'''". Then, click on the blue '''Append''' button:

[[File:Race 10.png|638x638px]]

You will import only the '''rig''', which is what we're looking for, and you'll be presented with a situation similar to this:

[[File:Race 5.png|643x643px]]

Now, depending on your 3D Character model, the rig may be bigger or smaller, the point is this: while '''in object mode''' we need to scale the '''original character rig''' in order to match in size with the RCK rig we want to use. A good measure is the eyes bones, make them match with your character:
[[File:Race 6.png|left|thumb|Make sure to '''Apply All Transforms''' after resizing.]]
As you can see here, the eyes bone matches with the character, which means the size is correct, and I've also rendered the original rig as black sticks instead of octahedral. This will come handy soon.

'''Once you did this, make sure to click on the character's rig we've just resized and Apply All Transforms by clicking CTRL-A -> Apply All Transforms (while in Object Mode).'''

Now, the objective is to set '''the resting position of our model such that it matches the A-Pose rig we want to use.'''

So now what you need to do select the original character rig (drawn as sticks) and go into pose mode, then, you'll have to move the bones until they match the rig we want to use (now the only one drawn as octahedral).

You should both rotate and move the bones (by pressing G) in order to achieve a correct alignment, especially for the hands and fingers. Do not be afraid to stretch the model if it's needed.

My advice is to work on only one side of the character and then mirror the pose for the other side. You can also use 'X-Axis Mirror' which is super useful.

Apply extra patience to align the fingers of the hand, it's a process you only have to do once and if it's done poorly it will have its consequences later.
[[File:Race 12.png|thumb|348x348px|Hand aligned with the RCK rig, done by rotating and moving the original character rig in pose mode.]]
During my process, I found out that it's better to align the spine and chest first, then the legs and at the very end the arms and hands.

Anyways, here's my finished result:

[[File:Race 13.png|597x597px]]

Now for the last thing to do is to '''apply the original armature, in order to set this pose as the model rest pose.'''

Select your mesh and in the modifiers window apply the armature modifier (of the original rig).

Now we can delete the original rig, nothing should break and the 3d model should keep this pose we've just made.

Last thing is to '''parent the new rig with the mesh''', click on the mesh first, then shift select the armature and press CTRL+P, "With Automatic Weight" should give a good enough result, which you can always modify later.

The hardest and maybe the most annoying part is done!

== Step 2: Splitting the Mesh ==
[[File:Race 14.png|thumb|300x300px|Separating the head.]]
Now we will split the mesh in the 6 sections I've mentioned before:

*'''Head'''
* '''Torso'''
* '''Arms'''
* '''Hands'''
* '''Legs'''
* '''Feet'''

You can very easily do that by going in Edit mode, selecting the vertices of each section, and then click 'P' to separate. Select '''Separate By Selection.'''

Repeat this process for every part, you can use the RCK basemeshes as reference for the split points.

[[File:Gifrace1.gif|left|thumb|'''GIF, CLICK TO VIEW''']]
If your model also have eyes, mouth, tongue, eyelashes, just keep them as separated meshes.

If you want, you can also add blendshapes for the head mesh, in order to be able to create different versions of this model which will allow you to create different NPCs.

This step is optional, but you probably don't want the very same character for different NPCs, so creating different blendshapes that allow you to scale/move the vertices of the head is recommended.

You can always do it later, I'll just create three blendshapes:

'''Eyes Up/Down'''

'''Nose Up/Down'''

'''Lips Up/Down'''

In this way I'll be also able to show you the blendshapes edits in the RCK AI Window later.

Our model is finally ready! For the next step, we'll export the model and import it in the RPG Creation Kit.

.

.

== Step 3: Exporting the model ==
Simply export the 3D Model as an FBX with these settings:

[[File:Race 15.png|834x834px]]

Make sure ''''Selected Objects'''<nowiki/>' is disabled, and use '''FBX Units Scale''' as 'Scaling'.

Then, just import the just exported 'MyNewRace.fbx' and its textures in the RCK.

If you did everything correctly the model will be of the right size, which should be very close to the RCK's default characters in my case:

[[File:Rck 16.png|522x522px]]

'''Also make sure to set the "Animation Type" as 'Humanoid' in the Rig tab of the 3d model imported in Unity.'''

We did the hard part! Let's move on.

== Step 4: Setting up the Character in Unity ==
The next step is to setup the 3D Model to have all the components and sub-objects needed in order to work properly in the RPG Creation Kit. We'll create a prefab that represents the base for all the characters that will use this race.

Search for "CHARACTER_BaseHumanMale" in your Unity Project. Essentially, we'll just mirror the "CHARACTER_BaseHumanMale" components onto our new character.

First of all, I will rename my new 3D Model, now in the scene, "'''CHARACTER_BaseNewRaceMale'''".
[[File:Race20.png|thumb|Process of attaching a mesh to the base character.]]
Secondly, I don't want him to be naked by default, but have an underwear. So what I will do is to '''duplicate the underwear of the default Human, and parent it to the CHARACTER_BaseNewRaceMale.'''

You'll notice that the duplicated underwear model doesn't really move, not even if you try to drag it around, that's because it's attached to the other mesh.

Add a 'AttachToMesh' component to the underwear object we've just duplicated, and set the "Attach To" field to the Legs of the '''CHARACTER_BaseNewRaceMale''' object. Finally, right click on the "Attach To Mesh (Script)" component and select "'''Attach to mesh'''":

If you did Step 1,2,3 correctly, the underwear mesh will correctly attach to the new character:

[[File:Race21.png|600x600px]]

'''Awesome!''' This means every other piece of equipment will correctly attach to the new character, because we've exported and rigged him correctly.

'''Important note: for the majority of equipment pieces you should not have clipping''' (equipment clipping through the character's body), because the way the RCK works is that it will '''hide the body when it's completely covered by the equipment piece'''.

So if we're wearing a cuirass that covers the whole upper body, there's no point in rendering the upperbody underneath it.

However, for some items like the underwear itself, and maybe helmets as well, you don't want to disable the mesh that it is only partially covered by the piece of the equipment item. So the item may clip through the new character body. The reason is simple, the items were originally made for the default character model and no matter how similar your new race model looks, it will be different in some ways. There are many ways to fix this, here are two I'd consider:

# '''Add blendshapes to the equipment piece itself (recommended)''': you can make blendshapes on item, in this case the underwear itself to make it shrink/expand, and move in all directions. In this way, when you attach it to your new character (and any new characters you will create) you'll always be able to modify it and correctly adapt it to the new body. And it will work for how many races you will ever want to add.
# '''Add blendshapes to the body parts themselves:''' you could make blendshapes, for example, on the waist, legs, lower legs, arms, etc, that will shrink the mesh in order for the item mesh to cover the body part appropriately. This probably works as well, but if the race models are different enough it may not work correctly and you'll wish you could move the mesh itself.

It's time to add the components/objects needed for the RPG Creation Kit to correctly recognize the Race. We'll focus on the CHARACTER_BaseNewRaceMale object we have in the scene.

'''First of all, you need an Animator with the Avatar set as your character's new avatar, which is created when you set the 3D Model Rig as Humanoid''', in the .fbx import tab. It should have been added by default by Unity, but if it's not, add it manually.

Next, we'll need some other things:

=== BodyData ===
Click on your CHARACTER_BaseNewRaceMale object, at this point you should just have as components the "Animator" with the character's Avatar. Let's add a '''BodyData''' component and set it up, the properties are pretty self-explanatory, I've added few arrows just to be extra clear:

[[File:Race22.png|649x649px]]

You can keep the Hair Index, Eye Index and Hair as they are, they serve as the 'defaults' for your race. In this case we have no hair and default eye color.

If you want your base character to also have default hair, you can attach the hair mesh the same way you attached the underwear. Bear in mind that your Hair 3d model '''has to be rigged as well, and the process is the very same of [[Creating a New Armor Item|creating any other equipment]],''' it's just that it's hair instead of a helmet!

Once you filled everything, let's move on!

=== AISounds ===
Click on your CHARACTER_BaseNewRaceMale object, at this point you should just have as components the "Animator" and the "BodyData".

Let's add a '''AISounds''' component to it, it will allow you to define sounds that the character will emit when hit by a weapon or when he dies:

[[File:Race23.png|352x352px]]

=== '''Ragdoll''' ===
Also add a "Ragdoll (RPG Creation Kit)" component and fill its "Animator" field:

[[File:Race24.png|484x484px]]

We need to define the actual ragdoll, that will allow us to not only allow the character to die via ragdoll, but to '''also define the hitboxes of the character itself''', so that weapons can hit him. We'll do this later, for now let's keep adding the rest of the needed objects and component.

=== '''HeadPos''' ===
[[File:Race25.png|thumb|322x322px|HeadPos location in the Character hierarchy.]]
Now we need to add a new object to our character. The "'''HeadPos'''" object is just an empty object placed on the head of the character that has few components on it. It serves the purpose of keeping track of where the head of the Character is, for example, so the player camera can look at that position when he is in dialogue with him

'''You need to place this new object as a child of the Head bone,''' which is under the rig. I underline that it's not the head mesh''', but the head bone.'''

Create a new empty game object and name it exactly '''"HeadPos"''' (without quotes). Look at the image on the right.

Now, we need to add few things to this new HeadPos object:

# '''Set its Tag to be "RPG Creation Kit/Ignore Weapons".'''
# '''Set its Layer to be "NPC".'''
# '''Add a Box Collider component and edit it so that it fits its face.'''
# '''Add a 'AIHeadPos' component.'''

Overall, it should look like this:

[[File:Race27.png|659x659px]]

=== LootingPoint ===
The LootingPoint objects allows the player to loot the character's body when he's dead. It's essentially an empty game object with a CapsuleCollider (defining the area the player has to look at in order to loot) and a script.

Instead of creating it from scratch, you can just duplicate the LootingPoint of the "''CHARACTER_BaseHumanMale''", located in the Hierarchy:

[[File:Race30.png|592x592px]]

Press CTRL+D to duplicate it and move the duplicated object, "LootingPoint_01", to our new character's bone '''hips'''.

It needs to be in the Hips bone because we want the CapsuleCollider to follow the ragdoll when the character falls to the ground.

So your setup should look like this, both the "Looting Point" and "Capsule Collider" need to be disabled by default:

[[File:Race31.png|827x827px]]

Don't worry about the "Test" value as the "Point Name", it will be replaced by the NPC name during runtime.

=== Actual Ragdoll and HitBoxes ===
Let's get back on adding the Ragdoll to our new character.

Click on CHARACTER_BaseNewRaceMale in the Hierarchy, then click on "GameObject -> 3D Object -> Ragdoll" to open the Ragdoll wizard:

[[File:Race41.png|865x865px]]

Next, you'll need to set all the bones as asked by the Create Ragdoll Wizard:
[[File:Race42.png|left|thumb|All bones set.]]

Great, now what should have happened is that Unity automatically added rigidbodies, colliders and joints to these parts. Now we have to do an important step, which is flagging these new colliders as BodyParts.

Select them all at once with CTRL+RIGHT CLICK, first of all you may need to adjust the colliders a little bit to match the 3D model.

Secondly, while '''all are selected you need to do these steps:'''

'''1. Change the objects 'Tag' to "RPG Creation Kit/BodyPart".'''

'''2. Change the objects 'Layer' to "BodyPart",''' if it asks you to change children as well, select "No, this object only"'''.'''

'''3. Add a new "BodyPart" component on the objects.'''

You should have this situation now:

[[File:Race43.png|648x648px]]

Great, we're almost done.

Now you need to select each bone individually and update the '''<nowiki/>'This Body Part'''' field in the '''BodyPart''' we've just added.

For example, on the 'Hips' you want to select "Chest" as body part, on the 'Head', select "Head", etc.

This allows the Kit to scale damage appropriately for each body parts, so you can set damage multipliers.

=== Last things ===
Before going on, we have to do two more things, set the '''Eyes''' and '''Mouth meshes''' of our character as '''child of the 'Head' mesh:'''

[[File:Race45.png]]

If you also have other meshes that should be in the head, like eyeleash or tongue, make sure to set them as child of Head as well.

'''Next, add a 'HeadBlendshapesManager'''' component to the Head mesh itself, and set the "Head Mesh" and "Mouth Mesh" fields appropriately:

[[File:Race47.png|886x886px]]

Leave the rest of the fields empty, we'll talk about them later.

Once you've did that, we've finally finished setting up the character, and we are ready for the next step!

== Step 5: Creating the Race ==
Now it's time to create the actual Race object.

'''Make a prefab of the CHARACTER_BaseNewRaceMale''' object we've worked on. '''Make sure to set the Prefab Transform Position and rotation to be (0,0,0).'''

Also, '''make a prefab of only the 'Eyes' mesh''', and name it something like "'''MyNewRaceEyesDefault".''' You should create a new "Race Eyes" asset, Click on "Create->RPG Creation Kit->Character->New Eyes" and configure it such that the Mesh is the Prefab we've just created.

Next, go inside the Project Window and right click on an empty space. Click on "Create->RPG Creation Kit->Character->New Race" to create a new Race Asset. Name it the name of your race, I'll name it "MyNewRace". Go in the inspector and '''Update the ID to "MyNewRace"''', or any other ID you want to give it.

Then, click on the '''<nowiki/>'Configure Race'''' button, it will bring up the '''Race Editor.'''

In the '''General''' tab, you can set the default attributes for new characters that will use this race.

'''Let's go in BodyData''' and fill some properties. We only have the Male version of this race, so we'll only have to fill that.

'''As "MaleModel"''', set the '''CHARACTER_BaseNewRaceMale prefab''' we've just created.

'''As "Male FPS"''', set the '''"FPS_MaleHuman"''' prefab you'll find in the project window. We'll talk about the FPS Arms later.

'''In 'Eyes Types', add a new Entry and select the eyes you've just created.''' So you don't have a blank list of eyes.

So you should have this situation:

[[File:Race50.png|812x812px]]

In the '''FaceData''' you'll be able to see all the Blendshapes you've created for your head mesh, I have the three I've created:

* '''Eyes Up/Down'''

* '''Nose Up/Down'''

* '''Lips Up/Down'''

Now, click on '''<nowiki/>'SAVE & CLOSE'''' and '''[[Databases|Update All the Databases]],''' to do that, click on the toolbar "RPG Creation Kit -> Update all Databases".

And we're practically done! Let's test the new race now.

== Testing the New Race ==
We'll try to create a new player character that will use this new race.

Open the '''_CharacterCreation_''' scene and highlight the "Character Creation Manager" GameObject.

You'll notice it has a "Character Creation Manager" Component, here we need to add the new Race as a '''Playable Race:'''

[[File:Race51.png|863x863px]]

With this done, now start the game from the main menu and try to change the race, if you did everything correctly everything should work fine:

[[File:Race52.png|758x758px]]

[[File:Race53.png|763x763px]]

'''Likewise, you can now create NPCs using this new race:'''

[[File:Race61.png|785x785px]]

[[File:Race60.png|788x788px]]

== Potential Issues ==
Here I'll list some common issues you may stumble upon:

=== Eyes are looking weird ===
Most likely you're using an Eyes asset from another race. Make sure the Eyes are the ones of your new character.

=== Clipping with Equipment ===
It's likely that when you've created the new character with the new race and went in third person, your character body clipped with the equipment.

Now, we'll discuss this properly in the next chapter "Final Considerations", but the reason why this is happening is because by default the RCK Items do not disable the body underneath it, because it's not really needed for the Demo.

Search for '''"[ARMOR] Leather_Curiass",''' which is the default armor your character has when starting the demo. Then, click on '''Body Options''' for the '''Male Biped Model''', here you will be able to hide body parts when this item is equipped.

[[File:Race62.png|686x686px]]

You can ignore the "Add new Blendshapes" button, it will be used for a feature that will be added in a next update.

This should fix your issue, but if your character is different enough from the default character, you may still face other issues, like the equipment being a bit offset from the body. We'll explore this topic in the next chapter.

=== When the NPCs using the New Race die, the ragdoll is weird/bugged ===
This probably happens because when you made the Ragdoll and Hitboxes, you left one or more overlaps between the body parts. Make sure the colliders are on their own and they do not enter each other, otherwise when your characters go ragdoll there will be a collision to resolve that results in a buggy ragdoll death.

== Final Considerations ==
When you're choosing your 3D models you'll want to use as races in your game, it's not a very good decision to choose models that are too different from each other. You can see this in games like Oblivion and Fallout, although the textures are different, the actual 3D models, especially for the bodies, are all very similar if not the same.

In my case, since I've used MakeHuman to make the original Race, it would have been a good choice for me too keep using that program to create new races, but for this tutorial I've preferred to start from a model that's very similar to what you'll commonly have when downloading a 3D model. We've seen when I've added the underwear mesh, I suggested to add blendshapes to the equipment itself in order to move it and scale it around the new character's body.

So my advice would be sticking with one type of body, changing textures and faces so that you won't have issues with your equipment.

Now, let's return to my character, most of the equipment items fit perfectly, but some do not. In particular, if I try to equip the "Guards" helmet, some of the head will clip out of the helmet, and I just can't hide the head underneath it because it will also hide the eyes that I want the character to be able to see.

As of the current v1.9, there's not an easy fix for this. The only thing you can really do is to adjust your character model in Blender, but this is not a final solution since that adjustment may make another helmet incompatible. That's why it's a good idea to use the very same proportions for all your races. Then, if you want some characters to be taller/smaller than others, you can always scale them afterwards, but making them all the same proportions will ensure all the equipment will be compatible.

However, since I always want to let users do as much as possible, as a next update I'll add a feature that will allow you to edit blendshapes on your equipment items and of your character bodies on a per-item-basis. That means if you have blendshapes that scale the head of your character, you'll be able to define the scale factor when an helmet, for example, is equipped (that would elegantly solve the Guard helmet problem I've explained earlier).

Or, if you have an armor that should be moved a bit forward for a specific race, you'll be able to also set that in the Body Options window (this is the same principle of moving the underwear mesh, but for every possible items that can be equipped at runtime).

Although these will ensure compatibility between different character models, '''still''', you should follow the advice of having similar bodies. So take a good chunk of time to go through all the possible models you could use for races in your game and if you plan on using a software like Daz Genesis, MakeHuman, or any other, it's a good idea to keep using that for all your races.

Creating a New Race

2025-02-15T14:01:08Z

Silvematt: /* Final Considerations */

[[File:Race 1.png|thumb|The "Human" Race used in the RPG Creation Kit .]]
In this tutorial we'll discuss an important topic you sooner or later will want to face when working with the RPG Creation Kit, which is Races. Before going on, you should have completed the [[:Category:Getting Started|Getting Started]] section, and at least tried to [[Creating a New Armor Item|create a new armor item]] for the default race. These tutorials will give you a proper understanding on how the RPG Creation Kit works so that you should not have any problems following along with this advanced topic.

A Race is essentially a complex humanoid 3D Model that acts as a base for your humanoid characters. Races define:

* '''Basemesh''': the actual 3D Model.
* '''Eye Colors''': set of materials you can use to make your characters eye color different.
* '''Hair Types''': set of 3D Models you can use as hair for your characters.
* '''Blendshapes''': used to deform the basemesh and create different characters.

You want to use a Race when you want the Player Character to be able to use a specific 3D model, or you want an RckAI to have all the functionality the player has like the Equipment System and Character Customization.

For AI that is simpler, meaning they don't need customization, hair or blendshapes, like normal creatures, you should use [[Creating a New Creature AI|Creature AI]].

A Race define both a Male and Female version of that Race, but you can also just create one of them and leaving the other blank if you only need one gender.

== Premises ==
Before we start, as the current RPG Creation Kit Version 1.9, you can create as many Races as you want. However, in order to make sure the Equipment System works correctly you need to follow two strict rules:

# '''All 3D Character Model has to use the same rig.'''
# '''The 3D Character Model mesh has to be split in:'''
## '''Head'''
## '''Torso'''
## '''Arms'''
## '''Hands'''
## '''Legs'''
## '''Feet'''

This is very important, and missing this step will result in your Race probably being playable and usable, but the Equipment system will not work with it correctly.

I recommend to either use the same rig as the Human race we use in the RCK, or to start from scratch by using one of your rig and sticking with it for all of your characters. Bear in mind that also the '''equipment''' '''models''' themselves have to use the same rig, as we've seen in the [[Creating a New Armor Item]] tutorial. If you haven't read that tutorial yet I '''strongly recommend doing it now before proceeding''', and to try to create an equipment Item for the RCK default character before attempting to create a new Race.

In this tutorial I will use a generic 3D Model, with his own rig and with the mesh that is in one piece, so we will see all the steps in order to convert it in a RCK-friendly model. I will use the RCK default character's rig, so I'll need to convert the new 3D Model to be able to use that rig. I'll also use Blender, although if you're familiar with another software the steps should be pretty similar.

First thing I'll need is the RPG Creation Kit Basemeshes's Rig, that you can find [https://drive.google.com/file/d/1R5c0DPCGQGky-iy4qfeKzS34mGVoUuYy/view at this link].

== Step 1: T-Pose, A-Pose? ==
The first problem you may stumble upon is the following: your rig is in A-Pose, but your character is in T-Pose (or vice-versa). Also, you may have both your rig in T-Pose or A-Pose, but they may be a little bit different.

In my case the 3D Model I'm using is in T-Pose, and the rig I want to use is in A-Pose:
[[File:Race 2.png|left|428x428px]]
[[File:Race 3.png|frameless|428x428px]]

As you can see, the rigs are quite different, and the resting pose is as well. This is probably your case too, and it will be the case for every Race you'll want to setup.
So '''the first step''' is to convert the '''resting pose''' of the character to '''match the rig I want to use.'''

Open your new 3D Model character in Blender and let's '''append''' the Rig from the RCK Human basemeshes.

Click on File->Append, then locate the "Base Male Human.blend" file and click on it. Go in the 'Objects' folder and click on "'''Unity compliant skeleton'''". Then, click on the blue '''Append''' button:

[[File:Race 10.png|638x638px]]

You will import only the '''rig''', which is what we're looking for, and you'll be presented with a situation similar to this:

[[File:Race 5.png|643x643px]]

Now, depending on your 3D Character model, the rig may be bigger or smaller, the point is this: while '''in object mode''' we need to scale the '''original character rig''' in order to match in size with the RCK rig we want to use. A good measure is the eyes bones, make them match with your character:
[[File:Race 6.png|left|thumb|Make sure to '''Apply All Transforms''' after resizing.]]
As you can see here, the eyes bone matches with the character, which means the size is correct, and I've also rendered the original rig as black sticks instead of octahedral. This will come handy soon.

'''Once you did this, make sure to click on the character's rig we've just resized and Apply All Transforms by clicking CTRL-A -> Apply All Transforms (while in Object Mode).'''

Now, the objective is to set '''the resting position of our model such that it matches the A-Pose rig we want to use.'''

So now what you need to do select the original character rig (drawn as sticks) and go into pose mode, then, you'll have to move the bones until they match the rig we want to use (now the only one drawn as octahedral).

You should both rotate and move the bones (by pressing G) in order to achieve a correct alignment, especially for the hands and fingers. Do not be afraid to stretch the model if it's needed.

My advice is to work on only one side of the character and then mirror the pose for the other side. You can also use 'X-Axis Mirror' which is super useful.

Apply extra patience to align the fingers of the hand, it's a process you only have to do once and if it's done poorly it will have its consequences later.
[[File:Race 12.png|thumb|348x348px|Hand aligned with the RCK rig, done by rotating and moving the original character rig in pose mode.]]
During my process, I found out that it's better to align the spine and chest first, then the legs and at the very end the arms and hands.

Anyways, here's my finished result:

[[File:Race 13.png|597x597px]]

Now for the last thing to do is to '''apply the original armature, in order to set this pose as the model rest pose.'''

Select your mesh and in the modifiers window apply the armature modifier (of the original rig).

Now we can delete the original rig, nothing should break and the 3d model should keep this pose we've just made.

Last thing is to '''parent the new rig with the mesh''', click on the mesh first, then shift select the armature and press CTRL+P, "With Automatic Weight" should give a good enough result, which you can always modify later.

The hardest and maybe the most annoying part is done!

== Step 2: Splitting the Mesh ==
[[File:Race 14.png|thumb|300x300px|Separating the head.]]
Now we will split the mesh in the 6 sections I've mentioned before:

*'''Head'''
* '''Torso'''
* '''Arms'''
* '''Hands'''
* '''Legs'''
* '''Feet'''

You can very easily do that by going in Edit mode, selecting the vertices of each section, and then click 'P' to separate. Select '''Separate By Selection.'''

Repeat this process for every part, you can use the RCK basemeshes as reference for the split points.

[[File:Gifrace1.gif|left|thumb|'''GIF, CLICK TO VIEW''']]
If your model also have eyes, mouth, tongue, eyelashes, just keep them as separated meshes.

If you want, you can also add blendshapes for the head mesh, in order to be able to create different versions of this model which will allow you to create different NPCs.

This step is optional, but you probably don't want the very same character for different NPCs, so creating different blendshapes that allow you to scale/move the vertices of the head is recommended.

You can always do it later, I'll just create three blendshapes:

'''Eyes Up/Down'''

'''Nose Up/Down'''

'''Lips Up/Down'''

In this way I'll be also able to show you the blendshapes edits in the RCK AI Window later.

Our model is finally ready! For the next step, we'll export the model and import it in the RPG Creation Kit.

.

.

== Step 3: Exporting the model ==
Simply export the 3D Model as an FBX with these settings:

[[File:Race 15.png|834x834px]]

Make sure ''''Selected Objects'''<nowiki/>' is disabled, and use '''FBX Units Scale''' as 'Scaling'.

Then, just import the just exported 'MyNewRace.fbx' and its textures in the RCK.

If you did everything correctly the model will be of the right size, which should be very close to the RCK's default characters in my case:

[[File:Rck 16.png|522x522px]]

'''Also make sure to set the "Animation Type" as 'Humanoid' in the Rig tab of the 3d model imported in Unity.'''

We did the hard part! Let's move on.

== Step 4: Setting up the Character in Unity ==
The next step is to setup the 3D Model to have all the components and sub-objects needed in order to work properly in the RPG Creation Kit. We'll create a prefab that represents the base for all the characters that will use this race.

Search for "CHARACTER_BaseHumanMale" in your Unity Project. Essentially, we'll just mirror the "CHARACTER_BaseHumanMale" components onto our new character.

First of all, I will rename my new 3D Model, now in the scene, "'''CHARACTER_BaseNewRaceMale'''".
[[File:Race20.png|thumb|Process of attaching a mesh to the base character.]]
Secondly, I don't want him to be naked by default, but have an underwear. So what I will do is to '''duplicate the underwear of the default Human, and parent it to the CHARACTER_BaseNewRaceMale.'''

You'll notice that the duplicated underwear model doesn't really move, not even if you try to drag it around, that's because it's attached to the other mesh.

Add a 'AttachToMesh' component to the underwear object we've just duplicated, and set the "Attach To" field to the Legs of the '''CHARACTER_BaseNewRaceMale''' object. Finally, right click on the "Attach To Mesh (Script)" component and select "'''Attach to mesh'''":

If you did Step 1,2,3 correctly, the underwear mesh will correctly attach to the new character:

[[File:Race21.png|600x600px]]

'''Awesome!''' This means every other piece of equipment will correctly attach to the new character, because we've exported and rigged him correctly.

'''Important note: for the majority of equipment pieces you should not have clipping''' (equipment clipping through the character's body), because the way the RCK works is that it will '''hide the body when it's completely covered by the equipment piece'''.

So if we're wearing a cuirass that covers the whole upper body, there's no point in rendering the upperbody underneath it.

However, for some items like the underwear itself, and maybe helmets as well, you don't want to disable the mesh that it is only partially covered by the piece of the equipment item. So the item may clip through the new character body. The reason is simple, the items were originally made for the default character model and no matter how similar your new race model looks, it will be different in some ways. There are many ways to fix this, here are two I'd consider:

# '''Add blendshapes to the equipment piece itself (recommended)''': you can make blendshapes on item, in this case the underwear itself to make it shrink/expand, and move in all directions. In this way, when you attach it to your new character (and any new characters you will create) you'll always be able to modify it and correctly adapt it to the new body. And it will work for how many races you will ever want to add.
# '''Add blendshapes to the body parts themselves:''' you could make blendshapes, for example, on the waist, legs, lower legs, arms, etc, that will shrink the mesh in order for the item mesh to cover the body part appropriately. This probably works as well, but if the race models are different enough it may not work correctly and you'll wish you could move the mesh itself.

It's time to add the components/objects needed for the RPG Creation Kit to correctly recognize the Race. We'll focus on the CHARACTER_BaseNewRaceMale object we have in the scene.

'''First of all, you need an Animator with the Avatar set as your character's new avatar, which is created when you set the 3D Model Rig as Humanoid''', in the .fbx import tab. It should have been added by default by Unity, but if it's not, add it manually.

Next, we'll need some other things:

=== BodyData ===
Click on your CHARACTER_BaseNewRaceMale object, at this point you should just have as components the "Animator" with the character's Avatar. Let's add a '''BodyData''' component and set it up, the properties are pretty self-explanatory, I've added few arrows just to be extra clear:

[[File:Race22.png|649x649px]]

You can keep the Hair Index, Eye Index and Hair as they are, they serve as the 'defaults' for your race. In this case we have no hair and default eye color.

If you want your base character to also have default hair, you can attach the hair mesh the same way you attached the underwear. Bear in mind that your Hair 3d model '''has to be rigged as well, and the process is the very same of [[Creating a New Armor Item|creating any other equipment]],''' it's just that it's hair instead of a helmet!

Once you filled everything, let's move on!

=== AISounds ===
Click on your CHARACTER_BaseNewRaceMale object, at this point you should just have as components the "Animator" and the "BodyData".

Let's add a '''AISounds''' component to it, it will allow you to define sounds that the character will emit when hit by a weapon or when he dies:

[[File:Race23.png|352x352px]]

=== '''Ragdoll''' ===
Also add a "Ragdoll (RPG Creation Kit)" component and fill its "Animator" field:

[[File:Race24.png|484x484px]]

We need to define the actual ragdoll, that will allow us to not only allow the character to die via ragdoll, but to '''also define the hitboxes of the character itself''', so that weapons can hit him. We'll do this later, for now let's keep adding the rest of the needed objects and component.

=== '''HeadPos''' ===
[[File:Race25.png|thumb|322x322px|HeadPos location in the Character hierarchy.]]
Now we need to add a new object to our character. The "'''HeadPos'''" object is just an empty object placed on the head of the character that has few components on it. It serves the purpose of keeping track of where the head of the Character is, for example, so the player camera can look at that position when he is in dialogue with him

'''You need to place this new object as a child of the Head bone,''' which is under the rig. I underline that it's not the head mesh''', but the head bone.'''

Create a new empty game object and name it exactly '''"HeadPos"''' (without quotes). Look at the image on the right.

Now, we need to add few things to this new HeadPos object:

# '''Set its Tag to be "RPG Creation Kit/Ignore Weapons".'''
# '''Set its Layer to be "NPC".'''
# '''Add a Box Collider component and edit it so that it fits its face.'''
# '''Add a 'AIHeadPos' component.'''

Overall, it should look like this:

[[File:Race27.png|659x659px]]

=== LootingPoint ===
The LootingPoint objects allows the player to loot the character's body when he's dead. It's essentially an empty game object with a CapsuleCollider (defining the area the player has to look at in order to loot) and a script.

Instead of creating it from scratch, you can just duplicate the LootingPoint of the "''CHARACTER_BaseHumanMale''", located in the Hierarchy:

[[File:Race30.png|592x592px]]

Press CTRL+D to duplicate it and move the duplicated object, "LootingPoint_01", to our new character's bone '''hips'''.

It needs to be in the Hips bone because we want the CapsuleCollider to follow the ragdoll when the character falls to the ground.

So your setup should look like this, both the "Looting Point" and "Capsule Collider" need to be disabled by default:

[[File:Race31.png|827x827px]]

Don't worry about the "Test" value as the "Point Name", it will be replaced by the NPC name during runtime.

=== Actual Ragdoll and HitBoxes ===
Let's get back on adding the Ragdoll to our new character.

Click on CHARACTER_BaseNewRaceMale in the Hierarchy, then click on "GameObject -> 3D Object -> Ragdoll" to open the Ragdoll wizard:

[[File:Race41.png|865x865px]]

Next, you'll need to set all the bones as asked by the Create Ragdoll Wizard:
[[File:Race42.png|left|thumb|All bones set.]]

Great, now what should have happened is that Unity automatically added rigidbodies, colliders and joints to these parts. Now we have to do an important step, which is flagging these new colliders as BodyParts.

Select them all at once with CTRL+RIGHT CLICK, first of all you may need to adjust the colliders a little bit to match the 3D model.

Secondly, while '''all are selected you need to do these steps:'''

'''1. Change the objects 'Tag' to "RPG Creation Kit/BodyPart".'''

'''2. Change the objects 'Layer' to "BodyPart",''' if it asks you to change children as well, select "No, this object only"'''.'''

'''3. Add a new "BodyPart" component on the objects.'''

You should have this situation now:

[[File:Race43.png|648x648px]]

Great, we're almost done.

Now you need to select each bone individually and update the '''<nowiki/>'This Body Part'''' field in the '''BodyPart''' we've just added.

For example, on the 'Hips' you want to select "Chest" as body part, on the 'Head', select "Head", etc.

This allows the Kit to scale damage appropriately for each body parts, so you can set damage multipliers.

=== Last things ===
Before going on, we have to do two more things, set the '''Eyes''' and '''Mouth meshes''' of our character as '''child of the 'Head' mesh:'''

[[File:Race45.png]]

If you also have other meshes that should be in the head, like eyeleash or tongue, make sure to set them as child of Head as well.

'''Next, add a 'HeadBlendshapesManager'''' component to the Head mesh itself, and set the "Head Mesh" and "Mouth Mesh" fields appropriately:

[[File:Race47.png|886x886px]]

Leave the rest of the fields empty, we'll talk about them later.

Once you've did that, we've finally finished setting up the character, and we are ready for the next step!

== Step 5: Creating the Race ==
Now it's time to create the actual Race object.

'''Make a prefab of the CHARACTER_BaseNewRaceMale''' object we've worked on. '''Make sure to set the Prefab Transform Position and rotation to be (0,0,0).'''

Also, '''make a prefab of only the 'Eyes' mesh''', and name it something like "'''MyNewRaceEyesDefault".''' You should create a new "Race Eyes" asset, Click on "Create->RPG Creation Kit->Character->New Eyes" and configure it such that the Mesh is the Prefab we've just created.

Next, go inside the Project Window and right click on an empty space. Click on "Create->RPG Creation Kit->Character->New Race" to create a new Race Asset. Name it the name of your race, I'll name it "MyNewRace". Go in the inspector and '''Update the ID to "MyNewRace"''', or any other ID you want to give it.

Then, click on the '''<nowiki/>'Configure Race'''' button, it will bring up the '''Race Editor.'''

In the '''General''' tab, you can set the default attributes for new characters that will use this race.

'''Let's go in BodyData''' and fill some properties. We only have the Male version of this race, so we'll only have to fill that.

'''As "MaleModel"''', set the '''CHARACTER_BaseNewRaceMale prefab''' we've just created.

'''As "Male FPS"''', set the '''"FPS_MaleHuman"''' prefab you'll find in the project window. We'll talk about the FPS Arms later.

'''In 'Eyes Types', add a new Entry and select the eyes you've just created.''' So you don't have a blank list of eyes.

So you should have this situation:

[[File:Race50.png|812x812px]]

In the '''FaceData''' you'll be able to see all the Blendshapes you've created for your head mesh, I have the three I've created:

* '''Eyes Up/Down'''

* '''Nose Up/Down'''

* '''Lips Up/Down'''

Now, click on '''<nowiki/>'SAVE & CLOSE'''' and '''[[Databases|Update All the Databases]],''' to do that, click on the toolbar "RPG Creation Kit -> Update all Databases".

And we're practically done! Let's test the new race now.

== Testing the New Race ==
We'll try to create a new player character that will use this new race.

Open the '''_CharacterCreation_''' scene and highlight the "Character Creation Manager" GameObject.

You'll notice it has a "Character Creation Manager" Component, here we need to add the new Race as a '''Playable Race:'''

[[File:Race51.png|863x863px]]

With this done, now start the game from the main menu and try to change the race, if you did everything correctly everything should work fine:

[[File:Race52.png|758x758px]]

[[File:Race53.png|763x763px]]

'''Likewise, you can now create NPCs using this new race:'''

[[File:Race61.png|785x785px]]

[[File:Race60.png|788x788px]]

== Potential Issues ==
Here I'll list some common issues you may stumble upon:

=== Eyes are looking weird ===
Most likely you're using an Eyes asset from another race. Make sure the Eyes are the ones of your new character.

=== Clipping with Equipment ===
It's likely that when you've created the new character with the new race and went in third person, your character body clipped with the equipment.

Now, we'll discuss this properly in the next chapter "Final Considerations", but the reason why this is happening is because by default the RCK Items do not disable the body underneath it, because it's not really needed for the Demo.

Search for '''"[ARMOR] Leather_Curiass",''' which is the default armor your character has when starting the demo. Then, click on '''Body Options''' for the '''Male Biped Model''', here you will be able to hide body parts when this item is equipped.

[[File:Race62.png|686x686px]]

You can ignore the "Add new Blendshapes" button, it will be used for a feature that will be added in a next update.

This should fix your issue, but if your character is different enough from the default character, you may still face other issues, like the equipment being a bit offset from the body. We'll explore this topic in the next chapter.

=== '''When the NPCs using the New Race die, the ragdoll is weird/bugged''' ===
This probably happens because when you made the Ragdoll and Hitboxes, you left one or more overlaps between the body parts. Make sure the colliders are on their own and they do not enter each other, otherwise when your characters go ragdoll there will be a collision to resolve that results in a buggy ragdoll death.

== Final Considerations ==
When you're choosing your 3D models you'll want to use as races in your game, it's not a very good decision to choose models that are too different from each other. You can see this in games like Oblivion and Fallout, although the textures are different, the actual 3D models, especially for the bodies, are all very similar if not the same.

In my case, since I've used MakeHuman to make the original Race, it would have been a good choice for me too keep using that program to create new races, but for this tutorial I've preferred to start from a model that's very similar to what you'll commonly have when downloading a 3D model. We've seen when I've added the underwear mesh, I suggested to add blendshapes to the equipment itself in order to move it and scale it around the new character's body.

So my advice would be sticking with one type of body, changing textures and faces so that you won't have issues with your equipment.

Now, let's return to my character, most of the equipment items fit perfectly, but some do not. In particular, if I try to equip the "Guards" helmet, some of the head will clip out of the helmet, and I just can't hide the head underneath it because it will also hide the eyes that I want the character to be able to see.

As of the current v1.9, there's not an easy fix for this. The only thing you can really do is to adjust your character model in Blender, but this is not a final solution since that adjustment may make another helmet incompatible. That's why it's a good idea to use the very same proportions for all your races. Then, if you want some characters to be taller/smaller than others, you can always scale them afterwards, but making them all the same proportions will ensure all the equipment will be compatible.

However, since I always want to let users do as much as possible, as a next update I'll add a feature that will allow you to edit blendshapes on your equipment items and of your character bodies on a per-item-basis. That means if you have blendshapes that scale the head of your character, you'll be able to define the scale factor when an helmet, for example, is equipped (that would elegantly solve the Guard helmet problem I've explained earlier).

Or, if you have an armor that should be moved a bit forward for a specific race, you'll be able to also set that in the Body Options window (this is the same principle of moving the underwear mesh, but for every possible items that can be equipped at runtime).

Although these will ensure compatibility between different character models, '''still''', you should follow the advice of having similar bodies. So take a good chunk of time to go through all the possible models you could use for races in your game and if you plan on using a software like Daz Genesis, MakeHuman, or any other, it's a good idea to keep using that for all your races.