Code Design - Character's sheet

[Kurt-Dekker]

If the game doesn’t exist yet then you are thinking way too far ahead.

For any given attribute, somehow that value has to make it into the correct spot in your game before it can be useful.

Numbers by themselves are utterly meaningless.

Make the game enough that you CAN have splash damage, then expose the splash damage parameter as some kind of attribute.

Until then all the stuff people type here is going to just be meaningless noise.

In Unity, ScriptableObjects are generally used for this sort of configuration stuff. Here’s some more reading:

ScriptableObject usage in RPGs:

ScriptableObjects for an RPG with multiple units in your team

The most important concept about ScriptableObjects (SOs) is that they are custom-shaped blobs of data that you can edit inside the Unity inspector. The serialized values inside a SO map directly to that created asset on disk, the instance of the SO. When your game runs, it needs some data. One way to get that data is to hard-code it in the code. That is bad because when you change it, you need to change code. That’s why we have things like a SO to configure existing unchanging shipped code. W…

Creating lookup tables that can be assigned in the inspector.

This looks like a job tailor made for ScriptableObjects! ScriptableObjects are basically structured blobs of predefined data to help you create content for your game. For instance if I had a ScriptableObject called Weapon, it might have these properties: name detailed name description damage toughness weight what it looks like in the inventory what model it uses in game what animations the player uses to swing it I would create many of these Weapons, each one a file on disk (also called an…

Usage as a shared common data container:

Better Data with Scriptable Objects in Unity! (Tutorial)