Mission debriefing - Githubissues

nczempin / Turres-Monacorum

scifi tower defense made with löve2d and lua

http://nczempin.github.io/Turres-Monacorum/

Other

52 stars 10 forks source link

Mission debriefing #107

Open nczempin opened 10 years ago

nczempin commented 10 years ago

Especially for tutorials, we should have some text for an "after action report" when you clear a wave and/or a level (a map with several waves).

Supersonic112 commented 10 years ago

I think "wave repelled" or something along those lines would be sufficient after the end of a wave. The level end message could be a bit more detailed, though.

nczempin commented 10 years ago

Yes, but for the tutorial I want to introduce new gameplay elements after each wave, so I'll want to let it be as flexible and general as possible.

Supersonic112 commented 10 years ago

Ok. Then the mission.ini files could be expanded to contain a custom message (or a reference to a generic/default message) for each wave.

nczempin commented 10 years ago

To be as flexible as possible, we should have:

a mission briefing
a mission debriefing for success (meaning all waves were beaten)
a mission debriefing for failure (base destroyed)
a "before wave" message
an "after wave" message (this assumes success, because on failure we hit the mission debriefing). I'm not sure if we really need this one or if we can just combine before wave and after wave into one, with the mission [de]briefing providing the bookends.

nczempin commented 10 years ago

In here we'll just handle the mission-specific success and failure messages, whereas the "between waves" messages are dealt with in issue #63

nczempin commented 10 years ago

Please take a look at issue #18 for some "generic" success and failure messages.

We'll use those when we don't have any more specific ones, like we would in the tutorial.