Seasons #4694
Labels
No Label
#P1 CRITICAL
#P2: HIGH
#P3: elevated
#P4 priority: medium
#P6: low
#Review
annoying
API
bug
code quality
combat
commands
compatibility
configurability
contribution inside
controls
core feature
creative mode
delayed for engine release
documentation
duplicate
enhancement
environment
feature request
gameplay
graphics
ground content conflict
GUI/HUD
help wanted
incomplete feature
invalid / won't fix
items
looking for contributor
mapgen
meta
mineclone2+
Minecraft >= 1.13
Minecraft >= 1.17
missing feature
mobile
mobs
mod support
model needed
multiplayer
Needs adoption
needs discussion
needs engine change
needs more information
needs research
nodes
non-mob entities
performance
player
possible close
redstone
release notes
schematics
Skyblock
sounds
Testing / Retest
tools
translation
unconfirmed
mcl5
mcla
Media missing
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: VoxeLibre/VoxeLibre#4694
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Seasons would be incredibly cool, but of course a lot of work.
It would also add an interesting challenge to gameplay: you start in spring, quickly build your base, and collect some supplies so you get through the winter. In winter, you may have to rely on hunting and fishing, but otherwise may want to spend more time underground.
I agree; this is one of the many things that I really wish Minecraft had.
However, I don't think this needs to be a feature of VoxeLibre. I can see people disliking it or having a specific use case where they don't want it. That wouldn't matter if it was a sort of dynamic setting so that it could be turned on or off. That said, it should be possible to implement as an external mod.
Obviously one would make this configurable, just as with weather and timespeed.
But I doubt this can be done within a mod, as it needs to integrate into farming (plants grow slower in winter) for example, weather (snowstorms instead of rain, snowfall) but also into biomes.
There was a mod for MTG, "mymonths" https://github.com/minetest-mods/mymonths https://forum.luanti.org/viewtopic.php?f=9&t=13639&hilit=mymonths but no activity for 4 years now; plus this only works on its own trees.
Okay, that's fair.
Yeah, we probably shouldn't use this. It depends quite a bit on its own APIs, and like you said it hasn't been maintained in a while.
Farming can be made to have the current defaults, but check if the seasons mod is enabled and use those values and mechanics if it's the case.
While I love the idea, I remember the Minecraft developers/designers avoiding seasons because it poses multiple challenges and also affects exploration. For instance, if a player is guaranteed to get snow and ice in winter, it's no longer as enticing to search for a cold biome. Also, how would spawning be affected? We spawn certain mobs in cold biomes. Would we also adjust spawning based on seasons, and have foxes everywhere we get snow on the ground? Polar bears too? Strays?
What else would change during winter? Water freezing would make sense, and torches near water source blocks could prevent freezing, but should that be enough? Is the farmland supposed to stay hydrated just the same during winter, or should we reduce its range from 4 to 2 blocks around it?
Having seasons would be really cool but if we do it, it should be more than a gimmick. And if we do it seriously and add various bits of mechanics, I wonder how the complexity of the code base would increase. So it's probably worth trying this as a mod initially, to see what kind of mechanics we want, and what their addition means in practice. If things look good, we can bring it in officially. Maybe even have it as mandatory in hardcore mode - whenever we add difficulty levels (#177, #1106).
I can get behind that. I would recommend that we initially limit changes in the main game to those that allow the mod access it needs to implement seasons via APIs.
But to develop this API, one may need to largely work on this in a branch anyway.
I believe this will likely end up requiring too much integration (which is exactly why above mentioned mod brings along their own trees!) to be able to live as a separate mod. Just consider changing leaf colors in fall. You'd want to be able to hook into tree sapling growth, too, for example. And if these integrations are not tested well they will easily break across versions.
I doubt anybody will be happy to build and maintain this as an external mod. Just do a branch, develop it there, and then see how to integrate it step by step (and whether it is reasonable to make it a separate mod, or not).
But either way: whoever does work on this gets to decide how to approach this, not us beforehand, so this is a moot discussion.