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

FeatureFlags are now moved to GameConfig - Reflect this inside Builder/Runner #56

Closed
JaXt0r opened this issue Jun 24, 2024 · 1 comment

Comments

@JaXt0r
Copy link
Contributor

JaXt0r commented Jun 24, 2024

Hint: Needs to be done after #39

With @lmichaelis new architecture, we alter the way, how we handle FeatureFlags. They're now a ScriptableObject which is added to Bootstrap component. We need to alter it's behaviour

  • from: Call FeatureFlagTools.cs and reset all flags to production value.
  • to: Set a specific GameConfig asset (e.g. Assets/Gothic-UnZENity-Core/Resources/GameConfigurations/Production.asset) into the proper Bootstrap component in the scene.
@JaXt0r
Copy link
Contributor Author

JaXt0r commented Aug 27, 2024

Right now we set Production as the default GameConfiguration within main branch. I don't see why we would need to overwrite this via pipeline as of today. Can be closed for now.

@JaXt0r JaXt0r closed this as completed Aug 27, 2024
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