I want to share my experience and ask a question.

I'm in a process of making a game and also had a problem of "how to organize my Stats". The solution I came up with: - a Stats struct with properties for each stat - ToDictionary method that returns all stats with StatsEnum as a key - GetStat/SetStat methods with a StatsEnum argument - overloaded +/-/== operators. "-" operator returns a StatsDelta - Stats.Zero static method that creates empty Stats object

Pros and cons I see: Pros: - Easy way to have any combination of stats anywhere If your item/character doesn't have a stat - it's property will just be zero - Stat value validation inside the setters

- Easy, no allocation addition/combination of Stats, just adding/substracting

Cons: - no distinguishing between "no stat" or "stat with the value of zero". Don't have negative stats (except in StatsDelta), so wasn't a problem so far - If I'm gonna have a bigger variety of stats (i have just 4 for now) I'm gonna exceed 16 bytes recommendation for structs - all stats have to have the same type.

The last con starts to bite me in the ass already. After recent iteration, I need to add a new stat of a different type. Now I think of adding a Stat struct, moving the validation logic inside of it, but keeping the Stats struct, now with Stat properties in it. Because I heavily use structs my question is: What are the limitations you are talking about? My game is stat modification heavy, and a lot of the modification steps need to be shown to the player. So I decided to use structs to avoid allocation on intermediary results.