Writing this down for future reference, most of this is not something that is important in the short term.
Currently I specifically only support 1.21.1 because that is what I am playing on. The simple/naive approach would be to only support future version I play on and effectively don't bring new features to older versions. Which I think is an option as it keeps things simple, but it is a bit annoying for people who might want to use it on a different version that I play on.
Supporting multiple versions in one code base does at least mean a few things:
translations.mjs needs to be version specific- For messages send to the front end the version needs to be part of the payload. probably good to already start doing this just to avoid issues down the line.
- I have no clue how fabric handles multiple versions?
Probably good to look at other mods how they handle this.
Writing this down for future reference, most of this is not something that is important in the short term.
Currently I specifically only support 1.21.1 because that is what I am playing on. The simple/naive approach would be to only support future version I play on and effectively don't bring new features to older versions. Which I think is an option as it keeps things simple, but it is a bit annoying for people who might want to use it on a different version that I play on.
Supporting multiple versions in one code base does at least mean a few things:
translations.mjsneeds to be version specificProbably good to look at other mods how they handle this.