Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different ways to start a scenario with and without keeping difficulty settings #4383

Closed
DorpsGek opened this issue Jan 5, 2011 · 4 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Jan 5, 2011

George opened the ticket and wrote:

Split from #4362

R21646

Difficulty level should be not stored or be configurable in SE too (same as AI management)

Reported version: trunk
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/4383
@DorpsGek
Copy link
Member Author

frosch wrote:

Starting a scenario via "Play scenario" acts like "load game". It takes all none-client settings from the game.

Starting a scenario via "Start server" though starts it using StartScenario(), which takes the difficulty settings from the main menu.

This behaviour is also present in the 0.5 branch.

In the 0.4 branch OTOH, there are two ways to start a scenario. Either via "Play Scenario" which takes all settings from the game, or via "New Game" which also displays the list of scenarios, but uses the difficulty settings from main menu.

However, while the behaviour is inconsistent between multiplayer and singleplayer, I do not know what the right behaviour is. Some difficulty settings only affect map creation and make no sense for an already existing scenario.
The same holds for advanced settings. Most of them are not bound to a scenario/map, and could be taken from the main menu. But e.g. freeform_edges needs preserving.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4383#comment9498

@DorpsGek
Copy link
Member Author

George wrote:

IMHO, the scanario should start a new game, with all setting being taken from the menu, even if they do not make sense, except whose, that are mandatory, like freeform_edges, which should be overwritten by scenario (same for NEWGRFs, because they define objects on map and resetting them would break the scenario).

P.S. If the scenario allows to have AIs running on them, the AI used already should be taken from scenario.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4383#comment9506

@DorpsGek
Copy link
Member Author

frosch wrote:

The behaviour is now consistent again.
The old method of starting a scenario with some settings from main menu has been removed.

It needs complete rethinking what can be changed when starting a scenario, and what implications
- certain settings or
- NewGrfs, or even
- present company properties
have on new resp. loaded games and scenarios.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4383#comment9523

@DorpsGek
Copy link
Member Author

andythenorth closed the ticket.

Reason for closing: Won't implement

Flyspray clean up: more than 5 years old, and not obvious what should be done with this next, so closing. If this offends, discuss with andythenorth in irc. Thanks.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4383

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant