Alright, to start off, I’m going to begin with a little griping. I need a little bit of venting frustration when I continue to hear often the same complaints about ‘profiles’ and the inability to make custom profiles. I have–without reservation–absolute confidence that there is no ways in which the custom profile system of old is more usable than the current system.
Here is what happened in the Python with profiles:
- user enters in the custom profile info; the custom profile info was saved to
profiles.config - user assigned a server to the particular profile
- user starts a server
- profile was copied from the profile directory to the live server directory
Here is what happens in the nodejs system with profiles:
- user downloads a profile already listed
- user assigned a server to the particular profile
- user starts a server
- profile was copied from the profile directory to the live server directory
Here is what happens when you instead of starting the server, just use the ‘copy profile button’:
- user downloads a profile already listed
- user assigned a server to the particular profile
- ‘copy profile’ pushed, copies from the profile directory to the live server directory
- user starts a server
I hope it is abundantly clear now that custom profiles offer no difference to how servers work in MineOS. At All. The new system simply affords an easier way that doesn’t involve copy/pasting URLs, arbitrarily naming server jarfiles and understanding what “unmanaged” servers are.
I’m not sure why you’re skipping utilities that are designed to reduce user error. The purpose of the ‘copy profile’ button is to a) allow you to stay still within the webui to make a file copy and b) ensure that permissions of the copy are 100% correct, by ensuring the correct user owns the files.
If you copy it manually (read as: doing more work than you need to), you also run the risk of permissions being incorrect. Profiles get downloaded as root:root, but when in the server directory must be mc:mc (or whichever user you’re using). The webui always makes sure it’s assigned to the user creds you used for the login, but in SSH, it could be the right user, or you might have been using sudo or been doing it as root. I don’t know–when doing things manually, assumptions about how things are getting put into place that I’ve made and coded into MineOS can’t be relied upon anymore.
So it is is not “because you cannot create a custom profile” that you should select FTBInfinity, you should be selecting FTBInfinity because “it is the more reliable, dependable way to install FTBInfinity”.
The errors you get are pretty much the only thing that would be useful in order to diagnose your problem. If you take a look, you’ll see there are LOTs of people who have problems with stock FTBInfinity who aren’t using MineOS–so they understandably are not seeing “custom profiles” as being the problem at hand. If the problem is being reported in Java, then the answer is likely to be found in Java, not “custom profiles” and skipping the “copy profile” button.
Please know, I am not trying to single you out, but I am–for my own sanity–needing to point out that how you frame your issue and request for help has a significant effect on my attitude toward this free project I maintain.