Branching Campaigns?

Daily 11/04/03

Finished working on the next round of Map Editor revisions. Here's the latest screen:

How would you like to play this map? Got the Drengin war machine breathing down your throat. Hmmm...fun.

I've also been asked to think more about events and triggers. Here are my thoughts so far.

Events

Events consist of a trigger and effect.

Trigger

When a trigger is triggered, then the effect happens. My triggers so far:

  • "Occupy" a position on the map or a star/planet

  • "Destroy" a particular ship

  • "Colonize" a particular planet

Effect

Effects have immediate impact on the game. Here are my effects so far:

  • Instant Victory/Defeat with accompanying text.
  • Add/Remove resources. Resources are planets/ships/money/techs.
  • Text. Just random text like "I love you" or something just as silly.

With this kind of syntax, we can specify events in a text file. What do you think? Not enough, too much?

Now on to the Campaign Editor....

The Campaign Editor wasn't really a product we planned on making. It just grew out of what used to be just a simple map editor. Now it's a map editor, scenario editor, and campaign editor. I wish I had kept the map and scenario editors as one package. Ugh. I'm a big fan of data driven design so anything that helps us generate content is a good thing.

The simplest campaign editor would make just a list of linked missions:

Campaign:

  1. Scenario1 Map1
  2. Scenario2 Map2
  3. Scenario3 Map3
  4. etc...

A more complex campaign editor would allow branching:

Campaign:

  1. Scenario1 Map1 [Win goto 2][Lose goto 3]
  2. Scenario2 Map2 [Win goto 4][Lose goto 1]
  3. etc...

I think for now we'll stick with the first style. For a game like GalCiv, going through a scenario more than once doesn't make sense.

7,588 views 2 replies
Reply #1 Top
Do events occur only once ? Or do they occur each time the trigger is triggered ?

You could associate to each trigger a list of effects (instead of just one effect), and you could also add as an effect the addition of a new event (which would make chained events possible: the effect of trigger A is some text and adding the event B -> "foo". When trigger B is then triggered, "foo" is displayed).

And great looking screenshot, by the way.
Reply #2 Top
We're still thinking about events so all input is welcome.

That's in interesting idea. Multiple effects triggered either in parallel or serial each time the trigger is triggered. We'll have to add that. Thanks.