You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Autoconfig is only capable of loading for one server at a time, this means that we need to have different configs for each server. This creates problems with keeping configs updated.
For Example we have a Vulcan Config and a Stray Config, most likely only the Vulcan config will receive any updates.
We should be able to list servers that the config bypasses with which will significantly improve autoconfig. Eg, for the polar config you could have Pika, Hycraft, Jartex etc.
Additional context
NA
The text was updated successfully, but these errors were encountered:
LiquidBounce Branch
Nextgen
Describe your feature request.
Currently Autoconfig is only capable of loading for one server at a time, this means that we need to have different configs for each server. This creates problems with keeping configs updated.
For Example we have a Vulcan Config and a Stray Config, most likely only the Vulcan config will receive any updates.
We should be able to list servers that the config bypasses with which will significantly improve autoconfig. Eg, for the polar config you could have Pika, Hycraft, Jartex etc.
Additional context
NA
The text was updated successfully, but these errors were encountered: