Tutorial sitrep idea
Posted: Thu Mar 13, 2014 11:39 pm
Reading through multiple threads from newer players recently it's very apparent that the steep learning curve of the game is a problem, and one that we might want to think about solving over time as the game develops.
One idea occured to meāhave a series of Pedia articles about different game concepts aimed at newer players, and have them linked from the sitrep panel at appropirate moments.
For example, if a player builds a premade ship design, especially a Troop Ship, it could trigger a sitrep on completion that links to a tutorial page that summarises stuff (and links to the current pedia article) about Fleet Upkeep, and why the troop ship might need replacing in the ship design window because it's fragile, you need to build lots, etc.
Because it's sitrep driven, experienced players can simply turn them off, but new players can take advantage of it and learn stuff as it happens. Most of the sitreps themselves should be easily coded into existing effects because it would be stuff like completed a premade ship, or completed researching a key tech.
Plus, most of the work could be done by those of us that find the backend code baffling (but we'd need help on occasions), and it could be an ongoing project that gets added to as and when we see questions, etc.
Good idea? Doable?
One idea occured to meāhave a series of Pedia articles about different game concepts aimed at newer players, and have them linked from the sitrep panel at appropirate moments.
For example, if a player builds a premade ship design, especially a Troop Ship, it could trigger a sitrep on completion that links to a tutorial page that summarises stuff (and links to the current pedia article) about Fleet Upkeep, and why the troop ship might need replacing in the ship design window because it's fragile, you need to build lots, etc.
Because it's sitrep driven, experienced players can simply turn them off, but new players can take advantage of it and learn stuff as it happens. Most of the sitreps themselves should be easily coded into existing effects because it would be stuff like completed a premade ship, or completed researching a key tech.
Plus, most of the work could be done by those of us that find the backend code baffling (but we'd need help on occasions), and it could be an ongoing project that gets added to as and when we see questions, etc.
Good idea? Doable?