Background Voice/Narrator

[Unyahs]

Is there something in cogito at allows for a background sound/voice (a narrator) to be heard when an action is done ie. picking up items, placing items, finishing quests ? and the voice can only be heard once as pickup up the item again and again would make the voice redundant. I'd like to fit in some story within the gameplay.

Another question if I may, does cogito also support common level format like having level 1, 2, 3, so on and then having a victory screen at the end of each level as well as saving progress like stars/ponts?

Thank you in advance for those who will respond! 😊

[ac-arcana]

I don't think anything is built in to just play an audio file like that. There are sound bytes for picking up items. I would make a custom component and use signals for when the item is picked up, used, or whatever you want. You could also leverage the save system to prevent replays.

[ac-arcana]

You definitely can have multiple levels, just using transition points between them. Ie you jump down into a new space which triggers the transition to the next area. Just make it so you can't physically go back to the previous area by not linking it. Ie one way doors, drop downs, so it makes sense to the player.

COGITO supports saving, but afaik there isn't anything for a score screen at the end of levels.
Potentially this could be done as a separate scene where you read the saved data and give some kind of report.

[Phazorknight]

@ac-arcana already gave accurate answers, I'll just add my two cents a bit:

Is there something in cogito at allows for a background sound/voice (a narrator) to be heard when an action is done ie. picking up items, placing items, finishing quests ? and the voice can only be heard once as pickup up the item again and again would make the voice redundant. I'd like to fit in some story within the gameplay.

There's currently nothing built in but a few objects fire signals when you interact with them and save their state (if it's a one-time interaction). So you could create a simple object that plays an AudioStream (for narration etc I'd probably just use the quick audio plugin) and this will only happen the single time the player can interact with said object.

For quests, it's currently not built in, but the cogito_quest.gd has some functions that would be suitable for this:
start() gets called when a quest is started, complete() when a quest is successfully completed, failed() when you... well, you get the idea.
In these function bodies you could easily play an Audiostream in there that you add via export
This would let you add voice or narrator reaction to each individual quest. If you use the quick audio plugin, you don't need to worry about AudioPlayer nodes etc.

does cogito also support common level format like having level 1, 2, 3, so on and then having a victory screen at the end of each level as well as saving progress like stars/ponts?

There's no Victory screen built in.
In terms saving progress in terms of stars/points: If you want to use the built in systems, I'd probably use a Cogito Currency for it (or even a Cogito Attribute. This would stay saved with the player and kept from level to level.
The level states themselves would story any collected/picked up objects (like a star pickup)

[Phazorknight]

cogito_quest.gd is the custom resource that quests are based on, it defines the data and behavior that all quest resources have in common.

I've just updated the resource script with some fields for audio streams in this commit: c406d82

So in each quest you create, under Quest Audio, you can now add references to audio files that will play on a quest status change.
Contrary to the regular quest notification sound, this one is specific to each quest, so you can slot in voice over and the likes.

I've updated Quest A in the _Legacy Demo Scene` to include some voice lines if you want to hear this in action.

[Unyahs]

goodday, how do you fire a signal when all the quest counter are achieved? I tried to add signals in the quest_updater since i need multiple tasks to be done under one quest. so far it only fire a signal when the specific action is achieved not when the entire quest is done. I would want for the quest_complete to only fire after all the counters are done. Any solutions to this? The quest start works great but the quest complete for the changecounter doesnt. Anyway, thank you so much for the responses!

[Phazorknight]

@Unyahs
Currently, the Quest Counter properties of quest aren't properly implemented. Specifically, the current counter value of a quest is not saved and gets lost/reset if a player loads a game with an active quest that relies on the quest counter value, so I'd advice against using this.

In terms of signals and quests: Could you explain more what kind of behavior you're trying to create? Maybe talk me through an example?
The quest_updater is more used to receive signals to update quests, not to send signals.

[Unyahs]

so far I've mostly been using quest_updater since i need my quests to have multiple tasks to complete. I was trying to make something happen after a quest with counters is completed.

In example, one of my quest requires 3 items to placed on their own socket. After 3 of those items are placed, the quest should be completed and something should happen like a victory screen (or another quest).

what i currently have is one only of those items trigger the signal. so if i place the that one item, victory screen pops up even without finishing the entire quest (placing the other two). Meahwhile, placing the other two first, then placing that one item works normally (will finish the quest while victory screen pops up)

[Phazorknight]

In example, one of my quest requires 3 items to placed on their own socket. After 3 of those items are placed, the quest should be completed and something should happen like a victory screen (or another quest).

So in this scenario, I'd not use the quest system at all to send signals for this.
Here's how I would approach this:

• Three individual sockets, each has a signal that emits when the object is placed. I'd use the CogitoSwitch and it's signal _switched(is_on: bool)
• I'd create an empty node with a basic script that has a function to check the status of all switches. here's the pseudocode:
  I have not tested this!

switch_status_checker.gd

export var switches : Array[CogitoSwitch]
signal all_switches_on

func check_all_switches():
var switch_count: int = 0
 for switch in switches:
   if switch.is_on:
     switch_count+=1
     if switch_count >= switches.length()
       all_switches_on.emit()

• I'd hook up the switched signal from the switches to the switch status checker.
• Then I'd hook whatever is needed to happen to the all_switches_on signal of the switch status checker. So for example, when this signal is emitted, a door could open, or a quest could be changed to complete, etc.

Hope this helps!