Thanks for checking out this project. I'll give a brief overview how to get started playing.

In the project you'll find 2 scenes, 1. PersistantScene and 2. WorldScene.

If you want to start the game, press play while in the PersistantScene as this scene acts as the starting point to get certain systems up n running.

A lot of the games systems are not directly visible to the eye and hidden below, like the modding system, inventory, trading, economy, squad management and so on. A skilled coder or an organized team could really shine here.

We're using AI Tree for our AI logic. It's a behavior tree framework.

Currently our Factions and Armies are using that logic.

We want to use Unit testing to write better and clean code.

This project is working with a Component Based Architecture. Therefore you'll see a lot of components, some generic and some non generic ones. Components allow us to easily share functionality across different GameObjects and encourages modularity.

Our quest system is flexible and completly modable. We're storing all quests inside the Quests.json. We're using C# reflection to create QuestObjectiveSO at runtime based on a given type and properties.

To create a new quest objective type you simply create a new script with the naming scheme Quest[YOUR_OBJECTIVE_TYPE]TypeSO.cs. The class needs to inherite from QuestObjectiveSO.cs.

Additionally most ObjectiveTypes needs extra variables to determine the IsCompleted(). We add all required variables for calculation in QuestObjective.cs ( Examples: VisitedTarget or CurrencyRemaining)

To use this new quest objective simply use [YOUR_OBJECTIVE_TYPE] in the Quests.json.

Example:

public class QuestAquireCurrencyTypeSO : QuestObjectiveSO
{
    public int Amount;

    private QuestObjective data;

    public override void Initialize(QuestObjective questObjective)
    {
        data = questObjective;

        data.CurrencyRemaining = Amount;
        data.Self.GetComponent<CurrencyStorage>().OnCurrencyChanged += HandleCurrenyChange;
    }

    public override void UpdateObjective(QuestObjective questObjective)
    {
        // not needed
    }

    public override bool IsComplete(QuestObjective questObjective)
    {
        return data.CurrencyRemaining == 0;
    }

    private void HandleCurrenyChange(int changedAmount)
    {
        if (changedAmount > 0)
        {
            int remaining = Mathf.Max(0, data.CurrencyRemaining - changedAmount);
            data.CurrencyRemaining = remaining;
        }
    }
}

This is how it would look like to use this newly added quest objective type

{
    "Text": "Earn some cash along the way",
    "Type": "AquireCurrency",
    "Properties": {
        "Amount": 5000
    }
}

To create a new dialogue requirement you simply create a new script with the naming scheme Dialogue[YOUR_REQUIREMENT_NAME]RequirementSO.cs. The class needs to inherite from DialogueRequirementSO.cs.

To use this new dialogue requirement simply use [YOUR_REQUIREMENT_NAME] in the DialogueChoices.json.

Example:

public class DialogueCurrencyRequirementSO : DialogueRequirementSO
{
    public int RequiredCurrency;

    public override bool CheckRequirements(Transform self, Transform other)
    {
        Transform selectedTransform = Self ? self : other;

        CurrencyStorage currencyStorage = selectedTransform.GetComponent<CurrencyStorage>();
        return currencyStorage.HasEnoughCurrency(RequiredCurrency);
    }
}

This is how it would look like to use this newly added dialogue requirement

{
    "Type": "Currency",
    "Properties": {
        "Self": true,
        "RequiredCurrency": 6969
    }
}

Dialogue works extremely similar to the quests in terms of creating & managing them.

Sadly I did not have the time to build a tool that helps creating those JSON files as the game did not reach that stage of production yet.