Our game will have a lot of quests. Should we create one, or a few, large quest databases? Or should we have numerous small ones, say one for each major quest line or an area with a few quests in the area?
If we have more than one quest database, does that mean the quests in our game world cannot affect each other? Can we even have more than one database? How would that work with the journal?
thanks.
Quest database - many or one?
Re: Quest database - many or one?
Hi,
Either is fine. All of the databases assigned to the Quest Machine GameObject's Quest Databases list are treated as one big database at runtime.
Either is fine. All of the databases assigned to the Quest Machine GameObject's Quest Databases list are treated as one big database at runtime.
Re: Quest database - many or one?
Thanks. Can I export my databases into a standard format?
Re: Quest database - many or one?
Hi,
A standard format for quests doesn't exist.
You can export Quest Machine quests to JSON file format. You can also export all of the text in a quest to a Text Table asset, and then export the Text Table to a CSV spreadsheet, which is handy for localization.
A standard format for quests doesn't exist.
You can export Quest Machine quests to JSON file format. You can also export all of the text in a quest to a Text Table asset, and then export the Text Table to a CSV spreadsheet, which is handy for localization.