Prefab parties attached to scenarios #492

New Issue

2024-11-24T01:24:23Z

NQNStudios commented

2024-11-24 01:24:23 +00:00

(Migrated from github.com)

This could be done by essentially bundling a saved game (either zipped as usual or unzipped) inside the scenario file. It should be a party that's not in a scenario. The game would ask the user if they want to use the provided party. ~CelticMinstrel

This could be done by essentially bundling a saved game (either zipped as usual or unzipped) inside the scenario file. It should be a party that's not in a scenario. The game would ask the user if they want to use the provided party. \~CelticMinstrel

NQNStudios commented

2024-11-24 19:31:28 +00:00

(Migrated from github.com)

There are some interesting considerations with this one.

Usually, you can't click "Start Scenario" without a party loaded, unless you're forcing the default party. But if I want to play a scenario with an embedded prefab, I wouldn't want to have a different party loaded first. There would be no point.
If I did have my own party loaded when I try to start a scenario with a prefab, it would ask me if I want to use the prefab. If I say yes, it should probably save the party I had loaded first, before unloading it.

There are some interesting considerations with this one. 1. Usually, you can't click "Start Scenario" without a party loaded, unless you're forcing the default party. But if I want to play a scenario with an embedded prefab, I wouldn't want to have a different party loaded first. There would be no point. 2. If I *did* have my own party loaded when I try to start a scenario with a prefab, it would ask me if I want to use the prefab. If I say yes, it should probably save the party I had loaded first, before unloading it.

CelticMinstrel commented

2024-11-24 19:47:30 +00:00

(Migrated from github.com)

Usually, you can't click "Start Scenario" without a party loaded, unless you're forcing the default party. But if I want to play a scenario with an embedded prefab, I wouldn't want to have a different party loaded first. There would be no point.

I have a feeling that this vaguely tends towards removing the Make New Party button entirely. If you wanted to make a new party, you'd unload your party and click start scenario, and after choosing the scenario you're taken to the party creation screen, with an option to use the prefab party (either scenario-provided or default, depending on the scenario). If you don't want to make a new party, you load one first before clicking start scenario. If you then choose one with a prefab, as you said, you'd be asked if you want to use the prefab instead. Otherwise it'd just go forward with the chosen party.

Changing the flow like this actually solves another issue, which is that there isn't really a way to create a party from scratch that's higher-level for a more advanced scenario. But if the scenario is chosen before creating a party, the party creation screen can easily be adjusted to match the level expectation of the scenario.

Of course, this means we end up having yet another unused button…

> Usually, you can't click "Start Scenario" without a party loaded, unless you're forcing the default party. But if I want to play a scenario with an embedded prefab, I wouldn't want to have a different party loaded first. There would be no point. I have a feeling that this vaguely tends towards removing the Make New Party button entirely. If you wanted to make a new party, you'd unload your party and click start scenario, and after choosing the scenario you're taken to the party creation screen, with an option to use the prefab party (either scenario-provided or default, depending on the scenario). If you _don't_ want to make a new party, you load one first before clicking start scenario. If you then choose one with a prefab, as you said, you'd be asked if you want to use the prefab instead. Otherwise it'd just go forward with the chosen party. Changing the flow like this actually solves another issue, which is that there isn't really a way to create a party from scratch that's higher-level for a more advanced scenario. But if the scenario is chosen _before_ creating a party, the party creation screen can easily be adjusted to match the level expectation of the scenario. Of course, this means we end up having yet another unused button…

NQNStudios commented

2024-11-24 20:19:50 +00:00

(Migrated from github.com)

Of course, this means we end up having yet another unused button…

We could show twice as much of the startanim.png at one time. I think that would actually be nice.

> Of course, this means we end up having yet another unused button… We could show twice as much of the startanim.png at one time. I think that would actually be nice.

NQNStudios commented

2024-11-24 20:25:10 +00:00

(Migrated from github.com)


Tutorial	Preferences
Start Scenario	Startanim
Load Game	Startanim

| | | | ------------- | ------------- | | Tutorial | Preferences | | Start Scenario | Startanim | | Load Game | Startanim |

CelticMinstrel commented

2024-11-24 20:45:42 +00:00

(Migrated from github.com)

It's… an option, I guess. Not sure if I like that idea.

It's… _an_ option, I guess. Not sure if I like that idea.

CelticMinstrel commented

2024-11-24 21:17:43 +00:00

(Migrated from github.com)

Oh, another thing we could do if the scenario is chosen first is allow the scenario to impose a few restrictions on the party creator.

Some examples:

Legacy BoE scenarios could require you make a build with fewer skill points (I think the skill points for a new party were increased at some point in OBoE) and forbid Vahnatai, Anama, or Pacifist characters.
Escape from the Pit could accept only human characters and forbid the Anama trait.
Initial starting spells could be varied by scenario.

These would ultimately be only "soft" restrictions, because you could get around them by creating the party in another way and then entering the scenario with that party. So I'm not even sure if it would be worth doing. But it could be something to consider.

Oh, another thing we could do if the scenario is chosen first is allow the scenario to impose a few restrictions on the party creator. Some examples: * Legacy BoE scenarios could require you make a build with fewer skill points (I think the skill points for a new party were increased at some point in OBoE) and forbid Vahnatai, Anama, or Pacifist characters. * Escape from the Pit could accept only human characters and forbid the Anama trait. * Initial starting spells could be varied by scenario. These would ultimately be only "soft" restrictions, because you could get around them by creating the party in another way and then entering the scenario with that party. So I'm not even sure if it would be worth doing. But it could be something to consider.

NQNStudios commented

2024-11-26 19:40:14 +00:00

(Migrated from github.com)

I think this is sufficiently complicated that it should wait for after stable 2.0.

In the meantime for the tutorial scenario we should simply use force_party--no need to get fancy.

I think this is sufficiently complicated that it should wait for after stable 2.0. In the meantime for the tutorial scenario we should simply use force_party--no need to get fancy.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: openboe/oboe#492