I'm stuck at the 'umod new launcher' step in the installation guide
It also placed the files all over system32, is there a way to move the current installation into another folder?
"The handle is invalid" when installing uMod on server OSBug
Did you run the power shell window as admin? Normally they will start your whatever you run from thst location.
Also, which Windows version are you running?
I did run PS as admin. I'm using Win10 LTSC 2019 (17763.2090)
Merged post
I can't even uninstall the Rust server now and I don't feel like going through system32 and delete all of it manually.
Yeah, that wasn't the place it should have been installed to. You wouldn't run it as admin to install the server itself generally, else at least you'd want to set the location to where you actually want to install it.
There are some known issues with the Windows Server OS versions as well, which one of your initial issues would be likely from.
The one-liner did not work for me, even after manually installing .NET 5.0, so I went through every step in the Windows manual installation guide and got the error when creating a new launcher.
I'll go ahead and delete every known file and folder from system32 related to RustDedicated, is there anything else I should remove from there before installing it again in another directory?
Merged post
This is a complete mess now. I removed every known file and folder related to RustDedicated and umod and now I can't install or uninstall umod or anything else.
I give up.
I guess the current method for Oxide to download, unzip and be done with it is too easy for uMod.
Others have been there.. being really good at one thing and then suddenly becoming jacks of all trades.
Shall we all 'f' for McAfee ? At the start a really good AV and nowadays it's nothing more than bloatware.
Why uMod trying to be a package manager ?
You aren't required to install your server with uMod Agent, but it's there as an option. It does what it does because it needs to be that way given the more complex structure that it has as well as additional components to it. The Agent also handles updating each of the components. Eventually, we'd want to move away from distributing random bundles of copyrighted DLLs too, which is what happens now with Oxide.kasvotonI guess the current method for Oxide to download, unzip and be done with it is too easy for uMod.
Others have been there.. being really good at one thing and then suddenly becoming jacks of all trades.
Shall we all 'f' for McAfee ? At the start a really good AV and nowadays it's nothing more than bloatware.
Why uMod trying to be a package manager ?
Also, the current method to install uMod is for development and testing, and is subject to change.
You can read about the various changes here: https://umod.org/guides/foreword/release-notes
And the functionality of uMod Agent here: https://umod.org/guides/getting-started/agent
I understand your frustration, but it's primarily for testing right now and issues like this will come up until we get them worked out.runescape
This is a complete mess now. I removed every known file and folder related to RustDedicated and umod and now I can't install or uninstall umod or anything else.
I give up.
> The show command will list all available packages.
Yup.. it's a package manager.
I can understand the problematic related with the .dll distribution, patching and such.
I can also understand "patch in place" then unzipping a file it's not enough and a process must be triggered and so on.. but all of this [I guess] is solvable with a simple script.
Because now it's not only your core product that needs to be maintened, it's all this "ecosystem" being built.
Specially when you are crossing the line and including into your package manager the installation and lifecycle of the game files.
If your time is short today, it will be even shorter in the future having more stuff to take care of.
But in the end of the day if I can keep my steamcmd process and replace the wget oxide with umod update then I'm a happy customer.