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

[Feature]: Per-Arena configurations #548

Open
hoiw opened this issue Aug 21, 2024 · 1 comment
Open

[Feature]: Per-Arena configurations #548

hoiw opened this issue Aug 21, 2024 · 1 comment
Labels
0.3.x Targeted for a 0.3.x version feature request New feature or request

Comments

@hoiw
Copy link

hoiw commented Aug 21, 2024

Feature description

Making each arenas able to use different configurations, like resource type, game-effects on start and etc.
I think all the arenas always keeping the same configurations all the time make the game a bit boring , as the mechanics in config.yml would always be applied to all the arenas.
Divided configurations in different arenas makes the arena creators to have more space to make each arena more playable, mechanics more diverse in each arena as the map can still use the global configurations if they want ,which can prevent it from being boring, and no need to make all the arenas follow the same configurations all the time.

Is your feature request related to a problem?

No

@hoiw hoiw added feature request New feature or request needs triage Needs to be confirmed labels Aug 21, 2024
@Misat11 Misat11 added 0.3.x Targeted for a 0.3.x version and removed needs triage Needs to be confirmed labels Aug 21, 2024
@Misat11
Copy link
Member

Misat11 commented Aug 21, 2024

This is something we are looking at in the development versions of upcoming version 0.3.0 by introducing variants and configuration containers. Currently, we have no ETA on this version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.3.x Targeted for a 0.3.x version feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants