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

Idea about Mod compatibility with Fabric Seasons #97

Open
sternschnaube opened this issue Dec 27, 2023 · 4 comments
Open

Idea about Mod compatibility with Fabric Seasons #97

sternschnaube opened this issue Dec 27, 2023 · 4 comments

Comments

@sternschnaube
Copy link

sternschnaube commented Dec 27, 2023

https://modrinth.com/mod/fabric-seasons

Using this mod and putting the cooldown down leads to alltime map refreshes.
My idea would be, add another 4 map types to the normal version.

If the mod with a season is detected, it switches to the season map from it. With this, you avoid countless map refreshes 😄

I like to hear your opinion about this. Keep up the great work with XaeroPlus 🥳

@rfresh2
Copy link
Owner

rfresh2 commented Dec 30, 2023

I understand the problem but the solution isn't simple. There aren't a concept of "map types" in xaero's. You can manually switch between multiple maps per server but only one is active at a time (i.e. data is actually written and read).

There might be a way to store and render the block colors dynamically based on the season but it would be a bit tricky to do.

@sternschnaube
Copy link
Author

Do you think that multiple map switching could be the way? That only one is active is absolutely fine - but automatical switching would be great. Option to switch it to manual.

Your second point sounds interesting - it would also reduce (a lot) storage, since you have only one map.

@rfresh2
Copy link
Owner

rfresh2 commented Dec 30, 2023

Do you think that multiple map switching could be the way

Nope. It wouldn't be a very good user experience if the map is constantly missing chunks whenever seasons change.

@sternschnaube
Copy link
Author

sternschnaube commented Dec 30, 2023

You have to run and unlock the areas multiple times - but that's something the user should decide in the end. It would be at least a better behaviour than multiple refreshes from the main map.

A way to convert / save the data dynamically would be the best.

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

2 participants