Why 1.21.9？

[Pectics]

Nova replaced the support version with 1.21.9 just after the 1.21.9 update, is that too aggressive?

The main problem for me is that I am still using the last Release version that supported 1.21.8, but there is a problem in use, and at the same time I can't submit a new issue for feedback because I am not using the latest version!

[NichtStudioCode]

What stops you from checking whether the problem still exists in Nova 0.21 and then opening an issue for that version?

[ByteZ1337]

could you name the actual plugin that causes this?

Also, I think it's unwise to put all the dependencies in a .jar, I've never seen a plugin up to 46MB😢

This is primarily done for futureproofing to ensure Nova will still run fine even if our repo goes down.

[NichtStudioCode]

This may also very well be fixed with the removal of PatchedClassLoader in 0.21, which is the reason why we want people to test it on latest.

[Pectics]

could you name the actual plugin that causes this?

TrMenu, a GUI menu plugin based on TabooLib. The latest usable version is currently maintained by the community.

However, both repositories are fairly localized, so I’m not sure how much this can help Nova resolve the issue.

This is primarily done for futureproofing to ensure Nova will still run fine even if our repo goes down.

While this approach does have the advantage of ensuring Nova continues to function even if the main repo goes down, given that Nova is still in its 0.x development stage, it might make sense to offer two release variants instead — a full version with all dependencies included, and a lite version that fetches them online.

[NichtStudioCode]

a full version with all dependencies included, and a lite version that fetches them online.

I don't really see any downsides to the current approach. This seems unnecessary

[Pectics]

okay let's focus on the LinkageError issue mentioned above