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

Config/Parameters/Settings Overhaul #514

Closed
5 tasks done
Wyqer opened this issue Oct 17, 2018 · 0 comments
Closed
5 tasks done

Config/Parameters/Settings Overhaul #514

Wyqer opened this issue Oct 17, 2018 · 0 comments
Assignees
Milestone

Comments

@Wyqer
Copy link
Member

Wyqer commented Oct 17, 2018

Short Summary

As developer I want to provide a sensible and easy settings/parameter system for not critical adjustments for the mission, so that players have an easy and intuitive way to individualize their game experience with the mission.

Description

We'll delete all current paramters in the v0.97 version. Reason is, that it's currently a copy from the old framework parameters and therefore nearly all aren't even used yet. We'll add parameters during the development to have a cleaner set of settings.
Due to the modular structure we'll also evaluate different approaches and test them before choosing one of the following possibilities to implement these settings:

  • Use the mission parameters with an own save/load functionality like it's implemented in the old framework. So every module could add own settings via includes
  • Use CBA Settings completely. This way modules could add settings via preInit functions to the mission. Only downside would be that you have to start the mission once to set the settings you want. You could even need to restart/wipe once after you've chosen your settings, if they contain settings which affects the basic mission initialization
  • Use only the KPLIB Config File for all available settings. This way the settings need to be set by editing the file, which makes them persistent without any further work. Downside would be that players need to edit the missionfile to have the settings they like and edits could result in mistakes

We'll discuss and test the above possibilities internally but we would also appreciate opinions from everyone else on this topic. Many thanks in advance for your feedback on this.

Sub-Tasks

  • Remove all unused parameters
  • Evaluate which implementation to use for the future settings/parameters
  • Implement all currently needed/used settings
  • Start a wiki article for parameters explanations Directly in the settings files
  • Adjust the wiki article for module adding accordingly Will be done until moved to gh-pages
@Wyqer Wyqer added the backlog label Oct 17, 2018
@Wyqer Wyqer added this to the Sprint 8 milestone Oct 17, 2018
@Wyqer Wyqer self-assigned this Nov 6, 2018
@Wyqer Wyqer added in progress and removed backlog labels Nov 8, 2018
@Wyqer Wyqer mentioned this issue Nov 11, 2018
13 tasks
@Wyqer Wyqer closed this as completed Nov 12, 2018
@Wyqer Wyqer mentioned this issue Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant