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

1.19.2 support? #473

Closed
RemagOfficial opened this issue Nov 2, 2023 · 3 comments
Closed

1.19.2 support? #473

RemagOfficial opened this issue Nov 2, 2023 · 3 comments

Comments

@RemagOfficial
Copy link

is there any chance that there will be an update to 1.19.2 forge or is 1.19.X being skipped completely?

@TheOverpassArsonist
Copy link

TheOverpassArsonist commented Nov 3, 2023

A pull request already exists for 19.2 that appears to be mostly complete, #467 to be exact.

Not a developer on the project, haven't worked on any of the commits, and frankly don't even have any modding experience, but from my brief glimpses at the PR it looks, at least superficially, decently far along.

Also it's generally best to check around first for PRs, projects, branches, discussions, etc. for different versions before opening a new issue for version ports. If there aren't any and there isn't any information on ports in an FAQ, wiki, etc. then making an issue can be the right approach (if only to ask for some clarification on the porting process, what versions will/might be supported, etc.) but in general it clutters the repo unnecessarily. For small projects that's not necessarily an issue, but the larger a mod gets the more it can cause information fragmentation and general clutter. Admittedly a lot of mods don't have those,even though I really think they should, but it's good practice to check just in case. (A lot of the time mods just rely entirely on discord servers to communicate that sort of information which is very sub-optimal for countless reasons.)

@RemagOfficial
Copy link
Author

I have checked PRs and that one only has releases for fabric so I assumed that the forge code wasn't updated

@tyra314
Copy link
Member

tyra314 commented Dec 12, 2023

Not an issue.

@tyra314 tyra314 closed this as completed Dec 12, 2023
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

3 participants