Make your own fork of MCServerUpdater

[HSGamer]

Importance: 1/10

Problem:
Since you added MCServerUpdater code directly into your project, you would waste some time to check my upstream changes everytimes I occasionally made an update. And since I don't actively maintain it and you want total control of the code quality, you may want to control the code into your quality.

Solution:
Make your own fork of MCServerUpdater and make changes into your fork. Make it standalone so that other developers can contribute. Publish your fork to jitpack or something.

EDIT: I can't just change the ownership to you since it's my personal project and it has my core library, so making a fork is the only way.

[Osiris-Team]

@HSGamer no worries, a fork or ownership shouldn't be needed since I won't do any changes to it. I added your MCServerUpdater directly to autoplug source code, including its dependencies, so that I can easily review changes to it and to its dependencies by simply copying and pasting the new code, then reviewing the commit diff.
I don't think there is a better way of doing this, if I want to make sure I can review all the code (including your core dependencies).

[Osiris-Team]

If changes/new features are required I would do it in the traditional way, by creating a fork and then a PR on your repo, to avoid duplicate versions of MCServerUpdater👍

[HSGamer]

You may need to get rid of the core library since I have removed most of the needed core code in HSCore 4.6.0
I am going to do that anyways since I'm planning to move the library to my organization ProjectUnified for better formal maintaining

[Osiris-Team]

Nice. I think MCServerUpdater depended on some core libraries with the version 4.5.7, I included those and reviewed those.
Great job btw keeping those things so modular and minimal, I was expecting a ton more files to review haha.