RPG Creation Kit - User contributions [en]

Main Page

2026-07-18T21:41:50Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

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

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

'''Newest Tutorials'''
* [[Crafting & Enchanting]]
*[[Loot Tables]]
*[[What's new in the RPG Creation Kit 2|What's New in the RPG Creation Kit 2]]
*[[NPC Action Point|NPC Action Points]]
*[[Rck AI Editor]]
*[[Door|Doors]]
*[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]]

Door

2026-07-18T21:41:44Z

Silvematt: /* Doors and the Save System */

[[File:Door !1.png|thumb|218x218px|A Door in the RPG Creation Kit. ]]
'''Doors''' are interactive Objects that the Player and NPCs can open, close and travel through. In the RPG Creation Kit there are two kinds of Doors:

*'''Opening Doors:''' regular doors that simply open and close in place, playing an animation.
*'''Teleport Doors:''' doors that bring the Player and AI to another [[Cell]], such as the entrance of a house that leads to its Interior cell. These are what physically connects your world together.

A Door is a GameObject with the '''"Door"''' component and the ''"RPG Creation Kit/Door"'' tag. You can find ready-to-use prefabs in ''Prefab Library/Doors/'' ('''WoodenDoor_Prefab''' and '''EmptyDoor''', which is useful as a starting point for your own new doors).
==The Door component==
[[File:Door 2.png|868x868px]]
*'''Obj Reference ID:''' the '''UNIQUE ID''' of this Door. It is used to register the Door in the Cell, to save its state, and to lock/unlock it from scripts. You can generate a new one by right-clicking on the component and selecting ''"Regenerate objReference".''
*'''Persistent Reference / Persistent Reference ID:''' whether this Door is a [[Persistent References|Persistent Reference]], for the special cases where a Door has to be accessible at anytime (for example when an AI far away from it needs to use it).
*'''Animation:''' the Animation component of the door, it must contain an '''"Open"''' and a '''"Close"''' clip. Leave it blank for doors that don't physically open, like teleport doors.
*'''Ground Pivot:''' a point on the walkable surface in front of the door. It is the point an AI has to reach before being able to teleport to the linked cell. This can be blank, but if it is, the AI won't be able to use this door.
*'''Locked? / Lock Level / Key:''' see the Locked Doors section.
*'''Teleports? / To Cell / Teleport Marker:''' see the Teleport Doors section.
*'''Door Sounds:''' the AudioClips played when the door opens ('''Open'''), when it opens after being unlocked with the key ('''Unlocked Open'''), when the Player tries to open it while locked ('''Locked Open''') and when it closes ('''Close''').
*'''Linked Door:''' see the Teleport Doors section.

==Opening Doors==

An Opening Door is the simple case: the Player interacts with it and the "Open" or "Close" animation is played. All you have to set is the '''Animation''' reference and a unique '''Obj Reference ID'''. NPCs interact with these doors too: when an AI walking its path bumps into a closed Opening Door, it will play its open-door animation, force the door open and continue on its way.

==Teleport Doors==

A Teleport Door connects two Cells. When the Player uses it, the interaction text will show the destination (es, ''"E) Door to: Vera's Farmhouse"''), the destination Cell gets loaded and the Player appears next to the door on the other side. Setting one up goes like this:

#Enable '''Teleports?''' and assign the destination Cell in '''To Cell'''.
#Once the To Cell is set, the '''Linked Door''' dropdown fills up with the Obj Reference IDs of all the Doors found in the destination Cell: pick the one this door is connected to. If the list looks outdated, press the refresh button next to it.
#Adjust the '''Teleport Marker''': it is where the Player will appear when arriving through the ''linked'' door, shown in the Scene View as a cube gizmo with a blue arrow pointing forward. Place it just in front of the door, on the ground, with the arrow facing away from it.

Remember that the link goes both ways, so the door on the other side must be set up in the same manner, with its To Cell and Linked Door pointing back to this one (this is not strictly mandatory, but the only case I can think of not doing that would be some magical puzzle you'd want to make).

The Teleport Marker child is created automatically when you add the Door component, so you only have to move it in place. The inspector also offers two extremely convenient buttons, '''View Linked Door''' and '''View Linked Teleport Marker''', which open the destination Cell and select the linked object for you, so you can check both sides of the connection without hunting for them manually.

''Note: a Teleport Door doesn't need an Animation, the screen fades while the destination loads. You can leave the Animation field blank.''

==Locked Doors and Keys==

A Door can be '''Locked'''. When the Player tries to open a locked door:

*If its inventory contains the '''Key''' (a [[Key Item]] assigned in the Key field), the door unlocks and opens, playing the '''Unlocked Open''' sound.
*If it doesn't, an [[Alert Message]] tells the Player he doesn't have the key, and the '''Locked Open''' sound is played.

The '''Lock Level''' (from VeryEasy to Impossible) defines how hard the lock is. It is part of the door state and is stored in the SaveFile, but keep in mind that at the moment the Player can only get through a locked door with its Key. Maybe in a future update we'll have a lockpicking mechanic based on the Lock Level.

Doors can also be locked and unlocked at runtime, without the Player being involved:

*'''From a script:''' the [[RCKFunctions]] methods '''LockDoor(doorID, lockLevel)''' and '''UnlockDoor(doorID)''' work on any door, '''loaded or not''': if the door is not loaded, the SaveFile is edited directly, and the door will reflect the change the next time it loads. A good example is the ''CityInterior_LockShopsAtNight'' script of the Demo, which locks the doors of the shops during the night and unlocks them in the morning.
*'''From a Consequence:''' the [[Events And Consequences|Consequences System]] has the dedicated '''LockDoor''' and '''UnlockDoor''' Consequence types, so you can do the same from your quests without writing code.

==Doors and the Save System==

You don't have to do anything for doors to persist other than making sure every door has an '''UNIQUE Obj Reference ID.''' Every time a Door is opened, closed, locked or unlocked, its state ('''isOpened, isLocked, Lock Level''', even the current point of the animation) is saved in the SaveFile under its Obj Reference ID. When the Cell loads again, the door restores itself from that data, so a door left open stays open.

Since the saved state of a Door is just a few variables, it is also the classic example of an object you can edit while it is '''not loaded.''' The LockDoor/UnlockDoor functions above create the save data on the fly if the Player has never interacted with that door. This is discussed more in depth in the [[Persistent References]] page.

==Registering the Door in the Cell==

Like the other objects with an ID, Doors are registered in the '''All Doors''' dictionary of the '''"Cell Information"''' component of their Cell. After placing your Doors, run [[Update the Cells|Update the Cell]] and they will be registered automatically by their Obj Reference ID. This registration is what allows the rest of the kit (RCKFunctions, Consequences, AI) to find a door by its ID, so don't forget it!

Door

2026-07-18T21:40:33Z

Silvematt: Created page with "A Door in the RPG Creation Kit. '''Doors''' are interactive Objects that the Player and NPCs can open, close and travel through. In the RPG Creation Kit there are two kinds of Doors: *'''Opening Doors:''' regular doors that simply open and close in place, playing an animation. *'''Teleport Doors:''' doors that bring the Player and AI to another Cell, such as the entrance of a house that leads to its Interior cell. These are what..."

[[File:Door !1.png|thumb|218x218px|A Door in the RPG Creation Kit. ]]
'''Doors''' are interactive Objects that the Player and NPCs can open, close and travel through. In the RPG Creation Kit there are two kinds of Doors:

*'''Opening Doors:''' regular doors that simply open and close in place, playing an animation.
*'''Teleport Doors:''' doors that bring the Player and AI to another [[Cell]], such as the entrance of a house that leads to its Interior cell. These are what physically connects your world together.

A Door is a GameObject with the '''"Door"''' component and the ''"RPG Creation Kit/Door"'' tag. You can find ready-to-use prefabs in ''Prefab Library/Doors/'' ('''WoodenDoor_Prefab''' and '''EmptyDoor''', which is useful as a starting point for your own new doors).
==The Door component==
[[File:Door 2.png|868x868px]]
*'''Obj Reference ID:''' the '''UNIQUE ID''' of this Door. It is used to register the Door in the Cell, to save its state, and to lock/unlock it from scripts. You can generate a new one by right-clicking on the component and selecting ''"Regenerate objReference".''
*'''Persistent Reference / Persistent Reference ID:''' whether this Door is a [[Persistent References|Persistent Reference]], for the special cases where a Door has to be accessible at anytime (for example when an AI far away from it needs to use it).
*'''Animation:''' the Animation component of the door, it must contain an '''"Open"''' and a '''"Close"''' clip. Leave it blank for doors that don't physically open, like teleport doors.
*'''Ground Pivot:''' a point on the walkable surface in front of the door. It is the point an AI has to reach before being able to teleport to the linked cell. This can be blank, but if it is, the AI won't be able to use this door.
*'''Locked? / Lock Level / Key:''' see the Locked Doors section.
*'''Teleports? / To Cell / Teleport Marker:''' see the Teleport Doors section.
*'''Door Sounds:''' the AudioClips played when the door opens ('''Open'''), when it opens after being unlocked with the key ('''Unlocked Open'''), when the Player tries to open it while locked ('''Locked Open''') and when it closes ('''Close''').
*'''Linked Door:''' see the Teleport Doors section.

==Opening Doors==

An Opening Door is the simple case: the Player interacts with it and the "Open" or "Close" animation is played. All you have to set is the '''Animation''' reference and a unique '''Obj Reference ID'''. NPCs interact with these doors too: when an AI walking its path bumps into a closed Opening Door, it will play its open-door animation, force the door open and continue on its way.

==Teleport Doors==

A Teleport Door connects two Cells. When the Player uses it, the interaction text will show the destination (es, ''"E) Door to: Vera's Farmhouse"''), the destination Cell gets loaded and the Player appears next to the door on the other side. Setting one up goes like this:

#Enable '''Teleports?''' and assign the destination Cell in '''To Cell'''.
#Once the To Cell is set, the '''Linked Door''' dropdown fills up with the Obj Reference IDs of all the Doors found in the destination Cell: pick the one this door is connected to. If the list looks outdated, press the refresh button next to it.
#Adjust the '''Teleport Marker''': it is where the Player will appear when arriving through the ''linked'' door, shown in the Scene View as a cube gizmo with a blue arrow pointing forward. Place it just in front of the door, on the ground, with the arrow facing away from it.

Remember that the link goes both ways, so the door on the other side must be set up in the same manner, with its To Cell and Linked Door pointing back to this one (this is not strictly mandatory, but the only case I can think of not doing that would be some magical puzzle you'd want to make).

The Teleport Marker child is created automatically when you add the Door component, so you only have to move it in place. The inspector also offers two extremely convenient buttons, '''View Linked Door''' and '''View Linked Teleport Marker''', which open the destination Cell and select the linked object for you, so you can check both sides of the connection without hunting for them manually.

''Note: a Teleport Door doesn't need an Animation, the screen fades while the destination loads. You can leave the Animation field blank.''

==Locked Doors and Keys==

A Door can be '''Locked'''. When the Player tries to open a locked door:

*If its inventory contains the '''Key''' (a [[Key Item]] assigned in the Key field), the door unlocks and opens, playing the '''Unlocked Open''' sound.
*If it doesn't, an [[Alert Message]] tells the Player he doesn't have the key, and the '''Locked Open''' sound is played.

The '''Lock Level''' (from VeryEasy to Impossible) defines how hard the lock is. It is part of the door state and is stored in the SaveFile, but keep in mind that at the moment the Player can only get through a locked door with its Key. Maybe in a future update we'll have a lockpicking mechanic based on the Lock Level.

Doors can also be locked and unlocked at runtime, without the Player being involved:

*'''From a script:''' the [[RCKFunctions]] methods '''LockDoor(doorID, lockLevel)''' and '''UnlockDoor(doorID)''' work on any door, '''loaded or not''': if the door is not loaded, the SaveFile is edited directly, and the door will reflect the change the next time it loads. A good example is the ''CityInterior_LockShopsAtNight'' script of the Demo, which locks the doors of the shops during the night and unlocks them in the morning.
*'''From a Consequence:''' the [[Events And Consequences|Consequences System]] has the dedicated '''LockDoor''' and '''UnlockDoor''' Consequence types, so you can do the same from your quests without writing code.

==Doors and the Save System==

You don't have to do anything for doors to persist. Every time a Door is opened, closed, locked or unlocked, its state ('''isOpened, isLocked, Lock Level''', even the current point of the animation) is saved in the SaveFile under its Obj Reference ID. When the Cell loads again, the door restores itself from that data, so a door left open stays open.

Since the saved state of a Door is just a few variables, it is also the classic example of an object you can edit while it is '''not loaded.''' The LockDoor/UnlockDoor functions above create the save data on the fly if the Player has never interacted with that door. This is discussed more in depth in the [[Persistent References]] page.

==Registering the Door in the Cell==

Like the other objects with an ID, Doors are registered in the '''All Doors''' dictionary of the '''"Cell Information"''' component of their Cell. After placing your Doors, run [[Update the Cells|Update the Cell]] and they will be registered automatically by their Obj Reference ID. This registration is what allows the rest of the kit (RCKFunctions, Consequences, AI) to find a door by its ID, so don't forget it!

File:Door 2.png

2026-07-18T21:34:01Z

Silvematt:

door_2

File:Door !1.png

2026-07-18T21:32:54Z

Silvematt:

door_!1

Rck AI Editor

2026-07-18T12:51:40Z

Silvematt:

The '''Rck AI Editor''' is the tool used to create and edit the NPCs of your game. You can open it from the toolbar, under '''RPG Creation Kit > RckAI Editor'''.

[[File:Rckaieditor 1.png|583x583px]]

In the RPG Creation Kit, NPCs exist as '''prefabs''' stored in ''Assets/RPG Creation Kit/Prefab Library/AI/''. The Rck AI Editor works directly on those prefabs: everything you change and save from this window is applied to the prefab itself, so every instance of that NPC placed in your [[Cell|Cells]] will reflect the changes.

For a complete walkthrough on how to create an NPC and add it to the game, refer to the [[NPCs Creation]] tutorial. This page instead describes the editor itself and everything you can do with it.

''Note: Creatures and Mounts have their own versions of this tool, the '''CreatureAI Editor''' and the '''MountAI Editor''', which you can find under the same menu. They work pretty much in the same way.''

==The AI List==

On the left side of the window you can find the list of all the RckAI prefabs of the project, ordered by their Entity ID. From here you can:

*'''Search''' for a specific NPC by its Entity ID using the search bar (the bar turns yellow while a filter is active).
*'''Show/Hide the Demo Files''' with the "Show Demo Files?" toggle, so the NPCs of the Demo don't get in the way while you work on your own game.
*'''Refresh''' the list with the refresh button, in case you've added or removed prefabs outside of the editor.

Clicking on an NPC selects it and loads it in the right side of the window, where you can edit it through the tabs. The '''Select Prefab''' button selects the prefab of the current NPC in the Project Window, in case you need to access it directly.

By '''right-clicking''' on the list you can:

*'''New:''' creates a new RckAI prefab with default settings, named ''[RckAI] NewRckAI''.
*'''Duplicate Selected:''' creates a copy of the selected NPC, appending "Copy" to its Entity ID.
*'''Delete Selected:''' deletes the selected NPC after a confirmation dialog. If the NPC was a [[Persistent References|Persistent Reference]], it is also unregistered automatically.

==The RckAI Tab==

This is the main tab, it defines who the NPC is:

[[File:Rckaieditor 2.png|632x632px]]

*'''Entity ID:''' the '''UNIQUE ID''' of this NPC. It is used to look it up in the AI Database, it names the prefab, and if the NPC is a Persistent Reference it is used as its Ref ID as well.
*'''Entity Name:''' the name of the NPC, it's what will be displayed in game.
*'''Race:''' the [[Creating a New Race|Race]] of this NPC.
*'''Is Male?:''' whether the NPC is male or female, it determines which model of the Race is used.
*'''Is Essential?:''' if enabled, this NPC can never die: when its health reaches 0 it will heal back to 100% of his health.
*'''Use Ragdoll?:''' whether the NPC uses a ragdoll when it dies or an animation.
*'''Persistent Reference?:''' whether this NPC is a [[Persistent References|Persistent Reference]]. You just have to tick this, the registration is handled automatically when you save.
*'''Animation Controller:''' the Animator Controller the NPC will use.
*'''Look At Enabled?:''' whether the NPC turns its head to look at things (the Player, other NPCs...).
*'''Looting Corpse?:''' whether the Player can loot the corpse of this NPC once it is dead. If enabled, '''Looting Equipment?''' also lets the Player take what the NPC had equipped.
*'''Helps members of same faction?:''' if enabled, the NPC will join the fight when a member of one of its [[Faction|Factions]] is attacked nearby.

Below, the '''STATS''' section contains the Attributes and the Derived Attributes of the NPC. When you edit an Attribute (Strength, Constitution, Willpower...), the derived values such as Max Health, Max Mana, Max Stamina, Max Encumbrance and the Level of the NPC are '''recalculated automatically''' using the formulas defined in ''RCKSettings''. You can also see a preview of the '''Xp OnKill''', the amount of XP the Player will be awarded for killing this NPC, which you can adjust with the '''Xp Mult''' multiplier.

==The Face Tab==

This tab lets you customize the appearance of the NPC, it requires a Race to be assigned first.

[[File:Rckaieditor 3.png]]

On the left you can find the list of all the '''Face Blendshapes''' of the head model: select one and adjust it with the slider (from -100 to 100) while watching the result in the preview. The '''Random Face''' button generates a random combination of all the blendshapes, which is a nice starting point, while '''Reset Face''' sets everything back to zero.

At the bottom you can pick the '''Hair''' and the '''Eyes''' of the NPC, chosen among the types defined in its Race.

==The Inventory Tab==

Here you define what the NPC owns and what it has equipped:

[[File:Rckaeditori 5.png]]

*'''Can be pick-pocketed?:''' whether the Player can attempt to pickpocket this NPC.
*'''Items:''' the content of the NPC's inventory.
*'''Set Ownership / Clear Ownership:''' these buttons set (or clear) the ownership metadata of every item in the inventory, marking them as owned by this NPC. See [[Items Ownership, Metadata and Stealing]] for what this implies.
*'''Equipped Items:''' the items the NPC has equipped. You can equip an item of the inventory by clicking the '''arrow button''' next to it, or remove one from the equipment with the '''X''' button.

'''''Note: only equip Armors and Weapons, and have only one weapon and one armor piece equipped at a time.'''''

==The Spells Tab==

Here you can set the '''Spell In Use''' (the spell the NPC will cast in combat) and the list of the '''Spells''' this NPC knows.

[[File:Rckeditorai 6.png]]

==The Behaviour Tab==

This tab defines how the NPC behaves in the world:

[[File:Rckeditorai 7.png]]

*'''Use BT?:''' whether this NPC uses [[Behaviour|Behaviour Trees]].
*'''Tick Rate:''' how often the Behaviour Tree is ticked (every frame, every X frames, or every X seconds in realtime or game time). NPCs that don't need to react quickly can use a slower tick rate to save performances.
*'''Purpose Behaviour:''' the Behaviour Tree the NPC runs while it is not in combat.
*'''Combat Behaviour:''' the Behaviour Tree the NPC runs while it is in combat.

The '''Player Damage Tolerance''' settings define how forgiving the NPC is when the Player hits it:

*'''PDT Hits:''' the amount of hits the NPC will tolerate from the Player before turning hostile.
*'''PDT Timeslice:''' the time window (in seconds) in which the hits are counted. If this time passes without reaching the amount of hits, the count is forgiven and starts over.

Below, the '''DIALOGUE''' section:

*'''Use Dialogue System?:''' whether this NPC can talk to others or be talked to.
*'''Current Dialogue:''' the [[Dialogues|Dialogue Graph]] the NPC is currently using.
*'''Default Dialogue:''' the Dialogue Graph the NPC will fall back to.
*'''Rotate towards?:''' whether the NPC rotates towards its interlocutor during a conversation.
*'''Follows outside of Cell?:''' whether the NPC can follow its target even outside of its Cell. It's generally used to chase the player between cells if he gets in a fight with an NPC.

==The Factions Tab==

Here you can set the list of [[Faction|Factions]] this NPC belongs to. Factions determine how the NPC reacts to the Player and to other NPCs, and who it will help in a fight.

==Saving==

At the bottom of the window there are three buttons: '''SAVE''', '''SAVE & CLOSE''' and '''CANCEL'''.

It is important to understand that the editor works on a copy of the prefab loaded in memory, so '''nothing is applied until you press SAVE''' (or SAVE & CLOSE). Pressing CANCEL closes the window and discards everything you've changed since the last save.

Alert Message

2026-07-18T11:35:30Z

Silvematt:

The '''Alert Message''' is the pop-up text used to notify the Player that something happened in the game. It's what appears on screen when you gain XP ("+100 XP"), when you receive items ("Iron Bow added!"), when you learn a new spell ("You learn: Fireball") and in many other situations.

[[File:Alertmsg 1.png]]

The Alert Message is part of the Player's UI, you can find it inside the ''RckPlayer'' prefab, and it is exposed as a singleton ('''AlertMessage.instance'''), so it is accessible at anytime from anywhere in your code.

==Showing an Alert Message from a script==

To show an Alert Message, all you have to do is call '''InitAlertMessage()''' on the instance:

<pre>
AlertMessage.instance.InitAlertMessage("Here goes your message.", AlertMessage.DEFAULT_MESSAGE_DURATION_MEDIUM);
</pre>

The method takes the following parameters:

*'''Text:''' the message to display.
*'''Duration:''' how long (in seconds) the message stays on screen. You can pass any value you want, but for consistency you may want to use one of the default durations defined in the AlertMessage class: '''DEFAULT_MESSAGE_DURATION_SHORT''' (1.5s), '''DEFAULT_MESSAGE_DURATION_MEDIUM''' (3s) and '''DEFAULT_MESSAGE_DURATION_LONG''' (5s).
*'''Allow Duplication (optional):''' see the section below.

You can call it from any of your gameplay code: [[Item Script|Item Scripts]], [[Quest Script|Quest Scripts]], [[Result Scripts]] and so on. Since the duration runs on '''unscaled time''', the message will behave correctly even while the game is paused, for example when the Player has the inventory open.

==The Alerts Queue==

Only one Alert Message can be displayed at a time. If you init a message while another one is already on screen, the new one is not lost: it is added to a '''queue''', and it will be displayed as soon as the current one (and the ones queued before it) expires.

There is one exception: if the message you are initing has the '''same text''' of the one currently displayed, it is discarded. This avoids stacking a wall of identical pop-ups when the Player repeats the same action quickly (buying five items in a row would queue five "Transaction Completed!" otherwise). If for some reason you do want the same message to be queued multiple times, pass '''true''' to the '''allowDuplication''' parameter.

==Showing an Alert Message from a Consequence==

You don't necessarily need a script to show an Alert Message: the [[Events And Consequences|Consequences System]] has a dedicated Consequence type for it, called '''AlertMessage'''.

Just add a new Consequence, set its type to AlertMessage and fill the '''Alert Message''' text and the '''duration'''. When the Consequence fires, the pop-up will be displayed. See [[Creating A New Consequence]] if you don't know how Consequences work.

Usually Alert Messages are mostly used with consequences inside the Dialogues:

[[File:Alertmsg 2.png]]

==Customizing the look==

The pop-up itself is a UI element with an '''AlertMessageUIElement''' component, which simply holds a reference to the TextMeshPro text that gets filled with the message. To change how the Alert Message looks (font, size, position, background...), edit that UI element inside the ''RckPlayer'' prefab.

==Alert Message vs Tutorial Alert Message==

Don't confuse the Alert Message with the '''Tutorial Alert Message''': they are two different things.

The Alert Message is a passive notification, it appears, stays on screen for its duration and disappears by itself, without ever interrupting the Player.

The Tutorial Alert Message ('''TutorialAlertMessage.instance''') is the message box used for the tutorials of the Demo: calling '''OpenMessage()''' pauses the game, unlocks the cursor and displays a window that the Player has to close with a button before continuing. There is also an '''OpenMessageAfterDialogueEnds()''' version that waits for the current conversation to end before popping up. Use it when the Player really has to read what you are saying, and use the regular Alert Message for everything else.

Here is an example of the Tutorial Alert Message in use:

[[File:Tutorialalertmessage.png]]

Alert Message

2026-07-18T11:35:22Z

Silvematt: Created page with "The '''Alert Message''' is the pop-up text used to notify the Player that something happened in the game. It's what appears on screen when you gain XP ("+100 XP"), when you receive items ("Iron Bow added!"), when you learn a new spell ("You learn: Fireball") and in many other situations. File:Alertmsg 1.pngThe Alert Message is part of the Player's UI, you can find it inside the ''RckPlayer'' prefab, and it is exposed as a singleton ('''AlertMessage.instance'''), so..."

The '''Alert Message''' is the pop-up text used to notify the Player that something happened in the game. It's what appears on screen when you gain XP ("+100 XP"), when you receive items ("Iron Bow added!"), when you learn a new spell ("You learn: Fireball") and in many other situations.

[[File:Alertmsg 1.png]]The Alert Message is part of the Player's UI, you can find it inside the ''RckPlayer'' prefab, and it is exposed as a singleton ('''AlertMessage.instance'''), so it is accessible at anytime from anywhere in your code.

==Showing an Alert Message from a script==

To show an Alert Message, all you have to do is call '''InitAlertMessage()''' on the instance:

<pre>
AlertMessage.instance.InitAlertMessage("Here goes your message.", AlertMessage.DEFAULT_MESSAGE_DURATION_MEDIUM);
</pre>

The method takes the following parameters:

*'''Text:''' the message to display.
*'''Duration:''' how long (in seconds) the message stays on screen. You can pass any value you want, but for consistency you may want to use one of the default durations defined in the AlertMessage class: '''DEFAULT_MESSAGE_DURATION_SHORT''' (1.5s), '''DEFAULT_MESSAGE_DURATION_MEDIUM''' (3s) and '''DEFAULT_MESSAGE_DURATION_LONG''' (5s).
*'''Allow Duplication (optional):''' see the section below.

You can call it from any of your gameplay code: [[Item Script|Item Scripts]], [[Quest Script|Quest Scripts]], [[Result Scripts]] and so on. Since the duration runs on '''unscaled time''', the message will behave correctly even while the game is paused, for example when the Player has the inventory open.

==The Alerts Queue==

Only one Alert Message can be displayed at a time. If you init a message while another one is already on screen, the new one is not lost: it is added to a '''queue''', and it will be displayed as soon as the current one (and the ones queued before it) expires.

There is one exception: if the message you are initing has the '''same text''' of the one currently displayed, it is discarded. This avoids stacking a wall of identical pop-ups when the Player repeats the same action quickly (buying five items in a row would queue five "Transaction Completed!" otherwise). If for some reason you do want the same message to be queued multiple times, pass '''true''' to the '''allowDuplication''' parameter.

==Showing an Alert Message from a Consequence==

You don't necessarily need a script to show an Alert Message: the [[Events And Consequences|Consequences System]] has a dedicated Consequence type for it, called '''AlertMessage'''.

Just add a new Consequence, set its type to AlertMessage and fill the '''Alert Message''' text and the '''duration'''. When the Consequence fires, the pop-up will be displayed. See [[Creating A New Consequence]] if you don't know how Consequences work.

Usually Alert Messages are mostly used with consequences inside the Dialogues:

[[File:Alertmsg 2.png]]

==Customizing the look==

The pop-up itself is a UI element with an '''AlertMessageUIElement''' component, which simply holds a reference to the TextMeshPro text that gets filled with the message. To change how the Alert Message looks (font, size, position, background...), edit that UI element inside the ''RckPlayer'' prefab.

==Alert Message vs Tutorial Alert Message==

Don't confuse the Alert Message with the '''Tutorial Alert Message''': they are two different things.

The Alert Message is a passive notification, it appears, stays on screen for its duration and disappears by itself, without ever interrupting the Player.

The Tutorial Alert Message ('''TutorialAlertMessage.instance''') is the message box used for the tutorials of the Demo: calling '''OpenMessage()''' pauses the game, unlocks the cursor and displays a window that the Player has to close with a button before continuing. There is also an '''OpenMessageAfterDialogueEnds()''' version that waits for the current conversation to end before popping up. Use it when the Player really has to read what you are saying, and use the regular Alert Message for everything else.

Here is an example of the Tutorial Alert Message in use:

[[File:Tutorialalertmessage.png]]

File:Tutorialalertmessage.png

2026-07-18T11:34:24Z

Silvematt:

tutorialalertmessage

File:Alertmsg 2.png

2026-07-18T11:32:32Z

Silvematt:

alertmsg_2

File:Alertmsg 1.png

2026-07-18T11:29:29Z

Silvematt:

alertmsg_1

Main Page

2026-07-18T11:24:53Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

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

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

'''Newest Tutorials'''
* [[Crafting & Enchanting]]
*[[Loot Tables]]
*[[What's new in the RPG Creation Kit 2|What's New in the RPG Creation Kit 2]]
*[[NPC Action Point|NPC Action Points]]
*[[Rck AI Editor]]
*[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]]

Rck AI Editor

2026-07-18T11:24:36Z

Silvematt: Created page with "The '''Rck AI Editor''' is the tool used to create and edit the NPCs of your game. You can open it from the toolbar, under '''RPG Creation Kit > RckAI Editor'''. 583x583px In the RPG Creation Kit, NPCs exist as '''prefabs''' stored in ''Assets/RPG Creation Kit/Prefab Library/AI/''. The Rck AI Editor works directly on those prefabs: everything you change and save from this window is applied to the prefab itself, so every instance of that NPC p..."

The '''Rck AI Editor''' is the tool used to create and edit the NPCs of your game. You can open it from the toolbar, under '''RPG Creation Kit > RckAI Editor'''.

[[File:Rckaieditor 1.png|583x583px]]

In the RPG Creation Kit, NPCs exist as '''prefabs''' stored in ''Assets/RPG Creation Kit/Prefab Library/AI/''. The Rck AI Editor works directly on those prefabs: everything you change and save from this window is applied to the prefab itself, so every instance of that NPC placed in your [[Cell|Cells]] will reflect the changes.

For a complete walkthrough on how to create an NPC and add it to the game, refer to the [[NPCs Creation]] tutorial. This page instead describes the editor itself and everything you can do with it.

''Note: Creatures and Mounts have their own versions of this tool, the '''CreatureAI Editor''' and the '''MountAI Editor''', which you can find under the same menu. They work pretty much in the same way.''

==The AI List==

On the left side of the window you can find the list of all the RckAI prefabs of the project, ordered by their Entity ID. From here you can:

*'''Search''' for a specific NPC by its Entity ID using the search bar (the bar turns yellow while a filter is active).
*'''Show/Hide the Demo Files''' with the "Show Demo Files?" toggle, so the NPCs of the Demo don't get in the way while you work on your own game.
*'''Refresh''' the list with the refresh button, in case you've added or removed prefabs outside of the editor.

Clicking on an NPC selects it and loads it in the right side of the window, where you can edit it through the tabs. The '''Select Prefab''' button selects the prefab of the current NPC in the Project Window, in case you need to access it directly.

By '''right-clicking''' on the list you can:

*'''New:''' creates a new RckAI prefab with default settings, named ''[RckAI] NewRckAI''.
*'''Duplicate Selected:''' creates a copy of the selected NPC, appending "Copy" to its Entity ID.
*'''Delete Selected:''' deletes the selected NPC after a confirmation dialog. If the NPC was a [[Persistent References|Persistent Reference]], it is also unregistered automatically.

==The RckAI Tab==

This is the main tab, it defines who the NPC is:

[[File:Rckaieditor 2.png|632x632px]]

*'''Entity ID:''' the '''UNIQUE ID''' of this NPC. It is used to look it up in the AI Database, it names the prefab, and if the NPC is a Persistent Reference it is used as its Ref ID as well.
*'''Entity Name:''' the name of the NPC, it's what will be displayed in game.
*'''Race:''' the [[Creating a New Race|Race]] of this NPC.
*'''Is Male?:''' whether the NPC is male or female, it determines which model of the Race is used.
*'''Is Essential?:''' if enabled, this NPC can never die: when its health reaches 0 it will heal back to 100% of his health.
*'''Use Ragdoll?:''' whether the NPC uses a ragdoll when it dies or an animation.
*'''Persistent Reference?:''' whether this NPC is a [[Persistent References|Persistent Reference]]. You just have to tick this, the registration is handled automatically when you save.
*'''Animation Controller:''' the Animator Controller the NPC will use.
*'''Look At Enabled?:''' whether the NPC turns its head to look at things (the Player, other NPCs...).
*'''Looting Corpse?:''' whether the Player can loot the corpse of this NPC once it is dead. If enabled, '''Looting Equipment?''' also lets the Player take what the NPC had equipped.
*'''Helps members of same faction?:''' if enabled, the NPC will join the fight when a member of one of its [[Faction|Factions]] is attacked nearby.

Below, the '''STATS''' section contains the Attributes and the Derived Attributes of the NPC. When you edit an Attribute (Strength, Constitution, Willpower...), the derived values such as Max Health, Max Mana, Max Stamina, Max Encumbrance and the Level of the NPC are '''recalculated automatically''' using the formulas defined in ''RCKSettings''. You can also see a preview of the '''Xp OnKill''', the amount of XP the Player will be awarded for killing this NPC, which you can adjust with the '''Xp Mult''' multiplier.

==The Face Tab==

This tab lets you customize the appearance of the NPC, it requires a Race to be assigned first.

[[File:Rckaieditor 3.png]]On the left you can find the list of all the '''Face Blendshapes''' of the head model: select one and adjust it with the slider (from -100 to 100) while watching the result in the preview. The '''Random Face''' button generates a random combination of all the blendshapes, which is a nice starting point, while '''Reset Face''' sets everything back to zero.

At the bottom you can pick the '''Hair''' and the '''Eyes''' of the NPC, chosen among the types defined in its Race.

==The Inventory Tab==

Here you define what the NPC owns and what it has equipped:

[[File:Rckaeditori 5.png]]

*'''Can be pick-pocketed?:''' whether the Player can attempt to pickpocket this NPC.
*'''Items:''' the content of the NPC's inventory.
*'''Set Ownership / Clear Ownership:''' these buttons set (or clear) the ownership metadata of every item in the inventory, marking them as owned by this NPC. See [[Items Ownership, Metadata and Stealing]] for what this implies.
*'''Equipped Items:''' the items the NPC has equipped. You can equip an item of the inventory by clicking the '''arrow button''' next to it, or remove one from the equipment with the '''X''' button.

'''''Note: only equip Armors and Weapons, and have only one weapon and one armor piece equipped at a time.'''''

==The Spells Tab==

Here you can set the '''Spell In Use''' (the spell the NPC will cast in combat) and the list of the '''Spells''' this NPC knows.

[[File:Rckeditorai 6.png]]

==The Behaviour Tab==

This tab defines how the NPC behaves in the world:

[[File:Rckeditorai 7.png]]

*'''Use BT?:''' whether this NPC uses [[Behaviour|Behaviour Trees]].
*'''Tick Rate:''' how often the Behaviour Tree is ticked (every frame, every X frames, or every X seconds in realtime or game time). NPCs that don't need to react quickly can use a slower tick rate to save performances.
*'''Purpose Behaviour:''' the Behaviour Tree the NPC runs while it is not in combat.
*'''Combat Behaviour:''' the Behaviour Tree the NPC runs while it is in combat.

The '''Player Damage Tolerance''' settings define how forgiving the NPC is when the Player hits it:

*'''PDT Hits:''' the amount of hits the NPC will tolerate from the Player before turning hostile.
*'''PDT Timeslice:''' the time window (in seconds) in which the hits are counted. If this time passes without reaching the amount of hits, the count is forgiven and starts over.

Below, the '''DIALOGUE''' section:

*'''Use Dialogue System?:''' whether this NPC can talk to others or be talked to.
*'''Current Dialogue:''' the [[Dialogues|Dialogue Graph]] the NPC is currently using.
*'''Default Dialogue:''' the Dialogue Graph the NPC will fall back to.
*'''Rotate towards?:''' whether the NPC rotates towards its interlocutor during a conversation.
*'''Follows outside of Cell?:''' whether the NPC can follow its target even outside of its Cell. It's generally used to chase the player between cells if he gets in a fight with an NPC.

==The Factions Tab==

Here you can set the list of [[Faction|Factions]] this NPC belongs to. Factions determine how the NPC reacts to the Player and to other NPCs, and who it will help in a fight.

==Saving==

At the bottom of the window there are three buttons: '''SAVE''', '''SAVE & CLOSE''' and '''CANCEL'''.

It is important to understand that the editor works on a copy of the prefab loaded in memory, so '''nothing is applied until you press SAVE''' (or SAVE & CLOSE). Pressing CANCEL closes the window and discards everything you've changed since the last save.

File:Rckeditorai 7.png

2026-07-18T11:21:53Z

Silvematt:

rckeditorai_7

File:Rckeditorai 6.png

2026-07-18T11:21:22Z

Silvematt:

rckeditorai_6

File:Rckaeditori 5.png

2026-07-18T11:19:42Z

Silvematt:

rckaeditori_5

File:Rckaieditor 3.png

2026-07-18T11:18:54Z

Silvematt:

rckaieditor_3

File:Rckaieditor 2.png

2026-07-18T11:15:00Z

Silvematt:

rckaieditor_2

File:Rckaieditor 1.png

2026-07-18T11:02:42Z

Silvematt:

rckaieditor_1

Main Page

2026-07-18T10:55:26Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

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

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

'''Newest Tutorials'''
* [[Crafting & Enchanting]]
*[[Loot Tables]]
*[[What's new in the RPG Creation Kit 2|What's New in the RPG Creation Kit 2]]
*[[NPC Action Point|NPC Action Points]]
*[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]]

NPC Action Point

2026-07-18T10:54:55Z

Silvematt: Created page with "An NPC Action Point placed in the first dungeon that allows the NPC to rest on a chair. '''NPC Action Points''' are special Objects placed in the world that NPCs can use to '''perform actions''', such as sitting on a chair, leaning on a wall or a counter, working on a farm or sleeping in a bed. They are what makes NPCs feel alive while they are not doing anything else, instead of standing still or wandering around, an NPC can reach..."

[[File:Actionp 1.png|thumb|260x260px|An NPC Action Point placed in the first dungeon that allows the NPC to rest on a chair.]]
'''NPC Action Points''' are special Objects placed in the world that NPCs can use to '''perform actions''', such as sitting on a chair, leaning on a wall or a counter, working on a farm or sleeping in a bed.

They are what makes NPCs feel alive while they are not doing anything else, instead of standing still or wandering around, an NPC can reach an Action Point, play an animation on it and stay there until its [[Behaviour]] tells it to do something else.

You can find some ready-to-use Action Points in the '''Prefab Library''', such as ''NPCActionPoint_Farm001'', ''NPCActionPoint_LeanOnCounter'', ''NPCActionPoint_LeanOnWallFromFront'' and ''Chair04_ActionPoint,'' and you can obviously create your own with your custom animations.

==How Action Points work==

An Action Point is a GameObject with the '''"NPC Action Point"''' component attached to it. When an NPC is told to use an Action Point (usually from its Behaviour Tree), the following happens:

#The NPC walks to the '''Pivot Point''' of the Action Point using the NavMesh.
#Once it is close enough, the NPC gets fixed in place, its position and rotation are adjusted to match exactly the Pivot Point.
#The NPC plays the '''Npc Action''' animation (for example, the sitting down animation).
#In the AI's Animator, the Npc Action will finish playing and go straight to a single (or multiple) idle loop animations.
#When the NPC has to leave the point, it plays the '''Npc Action Return''' animation (for example, getting up from the chair) and returns to its normal behaviour.

While an NPC is using or reaching an Action Point, the point is flagged as '''occupied''', so no other NPC will pick it. If the NPC enters in combat while reaching or using the point, he will stop using the Action Point and go into the combat behavior.

==The NPC Action Point component==

[[File:Actionp 2.png|861x861px]]
*'''Action Point ID:''' the '''UNIQUE ID''' of this Action Point, it is used to register the point in the [[Cell]] and to reference it from Behaviour Trees. You can generate a new one by right-clicking on the component and selecting '''"Regenerate ID"'''.
*'''Action Type:''' the type of action this point represents ('''Rest, Eat, Sleep, Mount'''). It acts as a tag, so it is possible to search for points of a given type (for example, an NPC that wants to find a place to Eat).
*'''Show Dummies:''' if enabled, the Dummies will be shown in the Scene View while the Action Point is selected (see the section below).
*'''Dummy First Keyframe / Dummy Last Keyframe:''' references to the two Dummies used to preview the animation in the Editor.
*'''Is Occupied:''' runtime flag that states whether an NPC is currently using (or reaching) this point.
*'''Pivot Point:''' the transform the NPC will be placed on before playing the animation. '''The placement of the Pivot Point is what makes the animation look right''', if your NPC sits in the air or inside the chair, this is what you have to adjust.
*'''Npc Action:''' the animation the NPC plays when it starts using the point (sitting down, leaning on the wall...).
*'''Npc Action Return:''' the animation the NPC plays when it stops using the point (getting up, detaching from the wall...).
*'''Entity Using This Point:''' runtime reference to the Entity that is currently using this point.
*'''Spawn Dynamic Object:''' if enabled, a Dynamic Object will be spawned in one of the NPC's hands while it is performing the action (see the Dynamic Objects section).
As you may have noticed, the "loop" animation that plays after the Npc Action is nowhere to be seen here. That (or those) are set in the TPSBase Animator itself:

[[File:Npcaction 3.png|960x960px]]

==Placing an Action Point with the Dummies==

Placing an Action Point by trial and error would be pretty tedious, you would have to enter Play Mode every time just to check if the NPC sits correctly. This is what the '''Dummies''' are for.

An Action Point has two Dummies as children: one is sampled at the '''first keyframe''' of the Npc Action animation, the other one at the '''last keyframe'''. With '''Show Dummies''' enabled, selecting the Action Point in the Scene View will show you exactly where the NPC will stand when it starts the action and where it will end up once the animation is over.

[[File:Actionp 1.png|260x260px]]

So, to place an Action Point on a chair for example, all you have to do is drag one of the prefabs near the chair, select it, and move it until the last keyframe Dummy sits correctly on the chair. The Dummies are automatically disabled when the game starts, so you don't have to worry about them being visible in game.

==Registering the Action Point in the Cell==

Action Points live inside [[Cell|Cells]], and every Cell holds a dictionary of all the Action Points it contains (you can see it in the '''"Cell Information"''' component, in the '''All Action Points''' dictionary). NPCs will search this dictionary when they are looking for a point to use.

You do not have to fill this dictionary by hand, after placing your Action Points in the Cell, simply run [[Update the Cells|Update the Cell]] and they will be registered automatically by their Action Point ID.

''Note: Make sure every point has a unique ID, you can use the "Regenerate ID" context menu for that.''

==Making an NPC use an Action Point==

NPCs use Action Points through their [[Behaviour|Behaviour Trees]].

You'll probably only want to switch their Behavior Tree to one of these Behaviors:

* '''SBTP_UseCurrentActionPoint:''' The NPC will go and use the Action Point that he has assigned in his RckAI component.
* '''SBTP_UseCurrentActionPointNoLookAt:''' Same thing as above, but the LookAt will be disabled for the AI using the action point (used for example on the blacksmith, to avoid him move his body if someone gets closer and mess the animation).
* Something like '''SBPT_FarmersLeftVirrhiael01''': where you can assign an array of actions points and the NPCs will randomly pick some.

Behaviors will be calling one of the following methods with an '''Invoke Method''' node:

*'''GetAndUseActionPoint:''' the NPC asks its current Cell for a '''random unoccupied''' Action Point and uses it. If every point of the Cell is occupied, the flag '''failedGettingActionPoint''' is set to true, so you can handle this case in the Behaviour Tree.
*'''UseCurrentActionPoint:''' the NPC uses the Action Point that is currently assigned in the '''Action Point''' field of its AI Movements. This is useful when you want a specific NPC to always use a specific point, like the farmers of the Demo.
*'''UseArrayActionPoint:''' takes an array of Action Point IDs as parameter, the NPC will pick a random unoccupied point among them. Useful when an NPC should choose between a set of points you've defined (for example, only the chairs of the tavern and not the leaning on the counter action).
*'''StopUsingNPCActionPoint:''' the NPC leaves the point, playing the Npc Action Return animation. If the ''immediate'' parameter is set to true, the NPC will skip the return animation and go back to its locomotion instantly.
*'''StopUsingNPCActionPointImmediate:''' same as above with immediate always true, in case you cannot pass a parameter.

You can also check flags such as '''isReachingActionPoint''', '''isUsingActionPoint''', '''leavingActionPoint''' and '''failedGettingActionPoint''' in your Behaviour Trees conditions to know at which state of the process the NPC is.

==Dynamic Objects==

Some actions look much better with a prop in the NPC's hands, think of the farmers of the Demo working the fields with their farming tool or the blacksmith working on his weapons with his hammer. That tool does not exist in the NPC's inventory, it is a '''Dynamic Object''' spawned by the Action Point itself.

[[File:Crafting.png|595x595px]]

To set it up, enable '''Spawn Dynamic Object''' and set:

*'''Dynamic Object:''' the prefab to spawn (the tool, like DoSmithingHammerPrefab). Its Prefab position should be set such that it will be correctly placed to the choosen Dynamic Object Bone.
*'''Dynamic Object Bone:''' the hand where the object will be attached ('''Rhand''' or '''Lhand''').
*'''Dynamic Object Sound:''' an optional AudioClip to play during the action (requires the Dynamic Object to have an AudioSource).
*'''Dynamic Object Particles:''' optional particles to play during the action.

The spawning is driven by '''Animation Events''' placed on the Npc Action animation clip, so that the object appears and plays sounds and particles in sync with the animation. The events you can call are: ''DynamicObjectStartAnimationEvent'', ''DynamicObjectEndAnimationEvent'', ''DynamicObjectPlaySoundAnimationEvent'' and ''DynamicObjectPlayParticlesEvent''. You can see how they are placed by looking at the animation used by the Blacksmith:

* '''DoSmithingEnter:''' will have ''DynamicObjectStartAnimationEvent'' that will allow us to spawn the Dynamic Object.
* '''DoSmithingLoop:''' will have ''DynamicObjectPlaySoundAnimationEvent'' to play a sound at a certain frame, and ''DynamicObjectPlayParticlesEvent'' to fire the particles at a certain frame.
* '''DoSmithingRelease:''' will have ''DynamicObjectEndAnimationEvent'' to destroy the Dynamic Object.

==Scripting custom Action Points==

The NPC Action Point component exposes a few virtual methods you can override to create your own kind of Action Point for more complex scenarios:

*'''OnUserAssigned:''' called as soon as an NPC picks this point, so when it starts reaching it (it does not mean it is using it yet).
*'''OnUserUses:''' called when the NPC starts playing the enter animation on the point.
*'''OnUserIsLeaving:''' called when the NPC starts playing the return animation.
*'''OnUserHasLeft:''' called when the NPC has completely been released from the point.
*'''OnUserForceLeaves:''' called when the NPC gets reset and should no longer reach or use the point (for example, when it enters in combat).

A good example of this inside the kit is the '''Mountup Point''', which is a special Action Point placed on Mounts that NPCs use to get on the saddle. Note that Mountup Points are excluded from the Cell's Action Points dictionary, they are handled by the Mounts system.

File:Crafting.png

2026-07-18T10:50:27Z

Silvematt:

Crafting

File:Npcaction 3.png

2026-07-18T10:43:31Z

Silvematt:

npcaction_3

File:Actionp 2.png

2026-07-18T10:36:06Z

Silvematt:

actionp_2

File:Actionp 1.png

2026-07-18T10:31:42Z

Silvematt:

actionp_1

Crafting & Enchanting

2026-07-18T00:46:57Z

Silvematt: Created page with "In this tutorial we are going to take a look at the new '''Crafting''' and '''Enchanting''' systems, features that came with '''Update 2.1'''. Crafting allows the Player to turn ingredients into new items at a Crafting Station, Enchanting allows the Player to apply magical effects to weapons and armors at an Enchanting Station. Both systems are recipe based, so all you have to do is create the recipe assets and place a station in the world. ==How..."

In this tutorial we are going to take a look at the new '''Crafting''' and '''Enchanting''' systems, features that came with '''Update 2.1'''.

Crafting allows the Player to turn ingredients into new items at a Crafting Station, Enchanting allows the Player to apply [[Effect On Entity|magical effects]] to weapons and armors at an Enchanting Station. Both systems are recipe based, so all you have to do is create the recipe assets and place a station in the world.

==How Crafting Works==

A Crafting Recipe is an asset that describes an output item and the ingredients needed to create it. The Player interacts with a Crafting Station in the world, selects one of the recipes available on that station, chooses how many times to craft it and presses the craft button. The ingredients are removed from his Inventory and the output item is added to it.

The ingredients can also be stolen items, in that case the stolen ones are consumed first, and the crafted item is always "clean" (see [[Items Ownership, Metadata and Stealing]]).

==Creating a Crafting Recipe==

Right click in the Project Window and select '''Create > RPG Creation Kit > Crafting > New Crafting Recipe'''.

[[File:Craft 1.png|816x816px]]

For each recipe you can set:

*'''Recipe ID''': the unique ID of the recipe.
*'''Recipe Name''': the name shown in the crafting UI.
*'''Recipe Icon''': the icon shown in the crafting UI.
*'''Output Item''': the item the Player will receive.
*'''Output Amount''': how many of the output item are given per craft.
*'''Ingredients''': the list of the required items, for each one you can set the item and the amount.
'''Important''': after creating a Crafting Recipe, you have to [[Databases|update the database]].

==Creating a Crafting Station==

Now we need a station in the world where the Player can use our recipes. Take any 3D Model, such as a forge or a cooking pot, and:

1) Set its Tag to "RPG Creation Kit/Crafting Station".

2) Add a Physical Collider (non-trigger) to it.

3) Add a "Crafting Station" component to it.

The component has the following fields:

[[File:Craft 2.png|807x807px]]

*'''Station ID''': the unique ID of the station.
*'''Station Name''': the name shown at the top of the crafting panel.
*'''On Use Sound''': the sound played when the Player opens the station.
*'''Available Recipes''': the list of the Crafting Recipes this station offers.

Different stations can offer different recipes, so you can have a forge that crafts weapons and a cooking pot that crafts food, just by referencing different recipes in this list. You can also have different stations with different recipes, and exploit the use of [[Mutable|Mutables]] to mutate stations into more powerful ones, for example as the player progresses in the game.

At this point, it is a good idea to make this object a Prefab, so when you want to add a new station you will only have to set its unique ID.

Looking at the station in game will show the interact prompt, pressing it opens the crafting panel. The panel shows all the recipes of the station, you can search them by name, and for each ingredient you will see how many you have and how many you need (in green if you have enough, in red if you don't).

With the + and - buttons you can craft the same recipe multiple times at once.

[[File:Craft 3.png|932x932px]]

==How Enchanting Works==

Enchanting applies an '''Enchanting Recipe''' to a weapon or an armor of the Player. An enchanted item:

*Gets a suffix appended to its name, for example "Iron Helmet" becomes "Iron Helmet of the Magi".
*Grants its effects to the Player as long as the item is equipped.
*Gets its value increased, both in the inventory and in the merchant prices.
*Shows an enchanted icon in the inventory, and it will not stack with non-enchanted copies of the same item.

An item can only have one enchantment. The enchantment is stored on the item itself, so it survives saving and loading, dropping the item in the world, selling it to a merchant and buying it back.

==Creating an Enchanting Recipe==

Right click in the Project Window and select '''Create > RPG Creation Kit > Enchanting > New Enchanting Recipe'''.

[[File:Craft 5.png|844x844px]]

For each recipe you can set:

*'''Recipe ID''': the unique ID of the recipe.
*'''Recipe Name''': the name shown in the enchanting UI.
*'''Recipe Icon''': the icon shown in the enchanting UI.
*'''Enchantment Suffix''': the text appended to the name of the enchanted item.
*'''Added Value''': golds added to the base value of the item while it is enchanted.
*'''Applies To''': if the recipe can be applied to Weapons, Armors or Both.
*'''Ingredients''': the materials consumed from the Inventory when enchanting.
*'''Effects''': the constant effects granted while the enchanted item is equipped. Only the Fortify and Damage types are allowed (Attribute, Health, Stamina and Mana), the duration is ignored since the effect is constant.
*'''Items Granted On Disenchant''': the items that may be given back to the Player when the item is disenchanted, each entry has its own probability (0-100%).

'''Important''': after creating an Enchanting Recipe, you have to [[Databases|update the database]].

==Creating an Enchanting Station==

The Enchanting Station works exactly like the Crafting Station:

1) Set the Tag of your 3D Model to "RPG Creation Kit/Enchanting Station".

2) Add a Physical Collider (non-trigger) to it.

3) Add an "Enchanting Station" component to it.

[[File:Craft 6.png|915x915px]]

The component has the following fields:

*'''Station ID''': the unique ID of the station.
*'''Station Name''': the name shown at the top of the enchanting panel.
*'''On Use Sound''': the sound played when the Player opens the station.
*'''On Enchanted Sound''': the sound played when an item is enchanted.
*'''On Disenchanted Sound''': the sound played when an item is disenchanted.
*'''Available Recipes''': the list of the Enchanting Recipes this station offers.

==Enchanting and Disenchanting In Game==

The enchanting panel has two tabs.

[[File:Craft 4.png|959x959px]]

In the '''Enchant''' tab the left list shows all the weapons and armors of the Player that can be enchanted, the right list shows the recipes of the station that are compatible with the selected item. For each ingredient you will see how many you have and how many you need, and the recipes you can afford are shown first.

In the '''Disenchant''' tab you can select an enchanted item and destroy it to get back some of the materials, based on the "Items Granted On Disenchant" of its recipe. '''Equipped items are not shown in this list''', you have to unequip them first. Disenchanting destroys the item.

If you want to prevent a specific item from being enchanted (such as a quest item or the torch), just disable the '''Is Enchantable''' checkbox on the item asset.

File:Craft 6.png

2026-07-18T00:44:53Z

Silvematt:

craft_6

File:Craft 5.png

2026-07-18T00:42:35Z

Silvematt:

craft_5

File:Craft 4.png

2026-07-18T00:38:35Z

Silvematt:

craft_4

File:Craft 3.png

2026-07-18T00:34:38Z

Silvematt:

craft_3

File:Craft 2.png

2026-07-18T00:31:15Z

Silvematt:

craft_2

File:Craft 1.png

2026-07-18T00:30:12Z

Silvematt:

craft_1

Effect On Entity

2026-07-18T00:16:17Z

Silvematt: Created page with "In this page we are going to take a look at <nowiki>''Effects On Entity''</nowiki>, the system the RPG Creation Kit uses to alter the Health, Stamina, Mana and Attributes of an entity. If you ever made a Health Potion, a poison or an enchanted sword, you already used them. Effects are a building block used all over the kit, so it is a good idea to understand how they work. ==Where Effects Are Used== You will find an "Effects" list in three places mainly: *'''Consumabl..."

In this page we are going to take a look at <nowiki>''Effects On Entity''</nowiki>, the system the RPG Creation Kit uses to alter the Health, Stamina, Mana and Attributes of an entity. If you ever made a Health Potion, a poison or an enchanted sword, you already used them. Effects are a building block used all over the kit, so it is a good idea to understand how they work.

==Where Effects Are Used==

You will find an "Effects" list in three places mainly:

*'''Consumable Items''': the effects are executed on the entity that uses the item, this is how potions and food work.
*'''Spells''': a spell has two lists, "On Caster Effects" executed on who casts the spell, and "On Target Effects" executed on who is hit by it.
*'''Enchanting Recipes''': the effects are constant and stay active as long as the enchanted item is equipped (see [[Crafting & Enchanting]]).

Effects work on any entity that has an "Entity Attributes" component, so they apply to the Player but also to NPCs and creatures.

==The Fields==

[[File:Eoe 1.png|773x773px]]

For each effect you can set:

*'''Effect Type''': what the effect does, see the list below.
*'''On Attribute''': only used by the Attribute types, it is the attribute to alter (Strength, Dexterity, Agility, Constitution, Speed, Endurance, Charisma...).
*'''Duration''': the duration of the effect in seconds, see below since the meaning changes a bit depending on the type.
*'''Magnitude''': the strength of the effect, how many points are added, removed or recovered.
*'''Icon''': the icon shown in the effects UI.
*'''Show In Effects UI''': if the effect should appear in the effects UI of the Player.

==Effect Types==

The types are divided in three families, each one available for Health, Stamina, Mana and Attributes.

===Restore===

Restore recovers the current value, it is the classic potion effect. With a Duration of 0 the whole Magnitude is recovered instantly, with a Duration greater than 0 the Magnitude is spread over the seconds of the duration, so a "Restore Health" with Magnitude 50 and Duration 5 heals 10 points per second for 5 seconds. Restore used on an attribute is not really used or useful as of now.

===Fortify===

Fortify temporarily raises a value: the Max Health, Max Stamina, Max Mana or an Attribute is increased by the Magnitude as soon as the effect starts, and Duration expires. A "Fortify Strength" with Magnitude 5 and Duration 60 gives +5 Strength for one minute.

If you set the Duration to 0, the bonus is applied instantly and never removed, so you can use it to create permanent rewards, such as an elixir that gives +1 Str, or an Ogre Root (if you get this reference, you're a real one!).

===Damage===

Damage is the opposite:
*'''Damage Health / Stamina / Mana''' lower Magnitude spread over the Duration exactly like Restore. This is how you make a poison that deals its damage over several seconds. With a Duration of 0 the whole damage is applied instantly.
*'''Damage Attribute''' lowers an Attribute by the Magnitude for the Duration, then gives it back, like a curse that weakens the target for a while.

==The Effects UI==

[[File:Eoe 2.png]]

When an effect with a duration is running, it can show on screen in the effects UI and the active effects are also listed in the "Active Effects" section of the Character tab of the inventory. The icon is not referenced directly, but by its ID in the Icons Database.

So if you want a new icon for your effect, remember add it first to the "Icons Database File" asset otherwise the icon will not be found in the dropdown list:

[[File:Eoe 3.png|911x911px]]

Two things to keep in mind:
*Effects are paused while the game is pause out a poison by sitting in the inventory or any other menu.
*Active effects are written on the Save File, so an effect that is halfway through its duration will resume from that point when the game is loaded.

==A Note About Enchantments==
Enchanting Recipes only accept the Fortify and Damage types, because the effect of an enchantment is constant: it is applied when the item is equipped and removed when it is unequipped, and the Duration is ignored. "Restore" types cannot be used.

File:Eoe 3.png

2026-07-18T00:09:21Z

Silvematt:

eoe_3

File:Eoe 2.png

2026-07-18T00:06:47Z

Silvematt:

eoe_2

File:Eoe 1.png

2026-07-18T00:00:42Z

Silvematt:

eoe_1

Loot Tables

2026-07-17T23:52:33Z

Silvematt: Created page with "In this tutorial we are going to take a look at the new '''Loot Tables''', which allow you to fill your Looting Points (chests, corpses, containers) with randomly generated items instead of placing every item by hand. You can also make the loot scale with the level of the Player. ==How Loot Tables Work== A Loot Table is an asset that describes what a container ''may'' contain. When the Player opens a Looting Point for the first time, th..."

In this tutorial we are going to take a look at the new '''Loot Tables''', which allow you to fill your [[Creating a New Looting Point|Looting Points]] (chests, corpses, containers) with randomly generated items instead of placing every item by hand. You can also make the loot scale with the level of the Player.

==How Loot Tables Work==

A Loot Table is an asset that describes what a container ''may'' contain. When the Player opens a Looting Point for the first time, the table is rolled and the result is placed inside its Inventory. The roll happens only once: the result is written on the Save File, so if the Player closes and reopens the container he will always find the same items.

There are two types of assets:

*'''Loot Table''': a list of guaranteed items plus a pool of random picks based on weights.
*'''Leveled Loot Table''': a set of Loot Tables divided in level brackets (for example levels 1-10 use one table, 11-20 another one). When it is rolled, it will use the table of the bracket that matches the current level of the Player.

A Loot Table can also contain other Loot Tables: an entry of the pool can point to another table instead of an item. This is very useful to create for example a generic "Random Potion" table and reuse it in many different chest tables.

==Creating a Loot Table==

Right click in the Project Window and select '''Create > RPG Creation Kit > Loot > New Loot Table'''.

The inspector has two sections:

[[File:Loottable 1.png|805x805px]]

===Always Granted===

The items you put in the "Guaranteed Items" list are added every time the table is rolled. For each entry you can set:

*'''Item''': the item to grant.
*'''Min Amount / Max Amount''': the amount is picked randomly between these two values. If you set Min Amount to 0, sometimes the entry will grant nothing.

===Weighted Rolls===

This is the random part of the table:

*'''Rolls Min / Rolls Max''': how many times the pool is rolled. Each roll picks one entry from the pool.
*'''Pool''': the list of the possible picks. For each entry you can set:
**'''Item''': the item granted if this entry is picked. Set this OR Nested Table, not both.
**'''Nested Table''': another Loot Table to roll instead of granting an item. If you set this, the nested table is rolled with its own settings, and the Min/Max Amount of this entry are ignored.
**'''Weight''': how likely this entry is compared to the others. Weights are relative, they are not percentages: if you have two entries with weight 3 and weight 1, the first one is picked 75% of the times. An entry with weight 0 is never picked.
**'''Min Amount / Max Amount''': the amount granted when this entry is picked.

Be aware about circular dependency (table A contains table B which contains table A), the Editor will warn you in the Console and the roll will stop at 8 levels of depth instead of freezing the game.

==Testing a Table==

You don't need to enter Play Mode to test your table: right click on the Loot Table component in the inspector and select "Test Roll". The rolled items and amounts will be printed in the Console. Roll it a few times to get an idea of what the table produces.

[[File:Loottable 2.png]]

[[File:Loottable 3.png]]

==Creating a Leveled Loot Table==

Right click in the Project Window and select '''Create > RPG Creation Kit > Loot > New Leveled Loot Table'''.

[[File:Loottable 4.png|916x916px]]

A Leveled Loot Table is just a list of "Brackets", for each one you can set:

*'''Min Level / Max Level''': the range of Player levels of this bracket.
*'''Table''': the Loot Table used for that range.

When the container is opened, the bracket that contains the current level of the Player is used. If the level of the Player is outside every bracket, the nearest one is used (so a level 50 Player will still get the loot of your 21-30 bracket if that is the highest one you made). If two brackets overlap, the first one wins and the Editor will warn you in the Console.

To test it, set the "Test Roll Level" field in the inspector, then right click on the component and select "Test Roll At Test Level": the Console will show you which table that level resolves to, followed by a test roll of it.

==Using a Loot Table on a Looting Point==

A Loot Table does nothing by itself, you have to attach it to a Looting Point with the "LootFromTable" component.

1) Select a GameObject that already has a "Looting Point" component (see [[Creating a New Looting Point]] if you don't have one).

2) Add a "LootFromTable" component to it.

3) Reference your Loot Table or Leveled Loot Table in the '''Loot Table''' field.

[[File:Loottable 5.png|918x918px]]

The component has two options:

*'''Additive''': if true, the rolled items are added on top of the items you placed by hand in the Inventory of the Looting Point. If false, the Inventory is cleared before the roll, so the container will only have what the table generates.
*'''Apply Ownership''': if true, the rolled items get the ownership metadata of the Looting Point, so taking them from an owned container counts as stealing, exactly like the items placed by hand (see [[Items Ownership, Metadata and Stealing]]).

The roll happens right before the looting panel opens the first time the Player interacts with the container, using the level of the Player at that moment, and it is then saved on the Save File.

Important: the Looting Point must have '''Has To Load And Save''' enabled. If it is disabled nothing is written on the Save File and the loot will re-roll every time the Player opens the container, the Editor will warn you about this in the Console.

==Result==

Opening the chest in game will now show randomly generated items appropriate to the level of the Player, and the chest will keep its rolled content across saves. Combined with nested tables you can build the entire loot economy of your game from a few reusable assets: one "Gems" table, one "Potions" table, one "Low Level Weapons" table, and every dungeon chest just references them with different weights.

In the Demo's starting cave you will find a crate on a corner as an example on how everything is setup.

[[File:Loottable 6.png|959x959px]]

File:Loottable 6.png

2026-07-17T23:41:41Z

Silvematt:

loottable_6

File:Loottable 5.png

2026-07-17T23:39:17Z

Silvematt:

loottable_5

File:Loottable 4.png

2026-07-17T23:37:40Z

Silvematt:

loottable_4

File:Loottable 3.png

2026-07-17T23:36:59Z

Silvematt:

loottable_3

File:Loottable 2.png

2026-07-17T23:35:32Z

Silvematt:

loottable_2

File:Loottable 1.png

2026-07-17T23:32:54Z

Silvematt:

loottable_1

Main Page

2026-07-17T23:12:00Z

Silvematt:

Welcome to the RPG Creation Kit Documentation.

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

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

'''Newest Tutorials'''
* [[Crafting & Enchanting]]
*[[Loot Tables]]
*[[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]]

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