Ease of server making

[xuuyz]

Role

I make servers

Suggestion

Ability to quickly and easily make servers

Benefit

I make servers for my friends and its very inconvenient making a server.

This suggestion is unique

• I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.

You may use the editor below to elaborate further.

I have made some mockups. 2 ideas.
1: Servers are a separate tab
2: Launch an instance as a server

[HyperSoop]

It would feel good to have server instances. They could just be marked with an indicator near their icons, a whole new tab would be a bit too overkill.

When creating an instance, there could be a "Server" checkbox somewhere in a corner, maybe the bottom left corner, under the platform list? It would be ideal to also have a few additional server softwares listed there if that's checked, that is, paper, purpur, all that...

[Xetaxheb]

Servers would need to be separate instances entirely, using the server pack files authors provide. There are clientside mods that will crash servers if they are in /mods/ and prism has no reasonable way to identify these. Adding support to download server packs would be nice, however (cf) server packs are not modpacks, they are redistributions of all jar and other necessary files and configs.

Other concerns:

• Cf reviews the zips manually so the batch files shouldn't be any more of a security risk than usual modding, right?
• Jar redistribution sits in a grey area curseforge kind of ignores the implications of for now afaik? I'm not sure it's worth getting into it with cf if attention is drawn to these because of it.
• Prism isn't really a server management program and even if the fabric/forge server installers were run there's not that much utility to be gotten out of doing this through prism instead of the easy jars server packs provide.
• Running a client install as a server can have a host of problems especially if it's concurrently.

[HyperSoop]

CF server packs are screwed and why'd we care that much

We're making a power user launcher here so if people are stupid it's their business, if you're going into server creation you should know how to deal with servers anyway. Servers aren't much different from clients, especially when it comes to mod loaders.

[P3rf3ctXZer0]

I think its the pack builders responsibility to test if a mod is server client or both. Is very unrealistic to automate this. This launcher should install the necessary base launcher files and libraries but a popup should still show Eula for legal protection of Prism. You should have a global black and whitelist for known client and server mods but it should be entirely optional. It should be easy for a person to set a mod as blacklist even as wildcard when doing pack creation and it would be nice if the not functionality could be on a per pack per version and maybe even per mod basis. This would allow faster trouble shooting. Example I know canary breaks Minecolonies so I could add this category to notes canary*.jar [This mod is incompatible with Minecolonies on a fundamental level.] Users should be allowed to commit this knowledge so we can pool our information together. Also the launch button should run whatever start apparatus the user sets examples .bat .exe .hamster you get the idea. It should need to be configured on a per pack per user basis.

[robinofskii]

I want to try here before opening a new issue, since I think it relates to "Ease of server making". How about we show in the table of mods in a profile, if they're server-, client-side or both? It would fit behind the version number column and would help eliminate a lot of hassle, looking for the mods I need to delete.
I found that the internal mod menu that minecraft has when launching it with fabric, has client labels attached to mods. But this was not correct all the time. The logs also aren't much help. And, because of the resetting pagination after showing mod details, it's quite a hassle to check every mod for that clientside / serverside indication on the detail page.

[snkiz]

I'm doing this. As a 'power user' I am taking on the responsibility of vetting that mods I'm downloading are compatible with servers.

• First I created an instance in Prism with the same fabric version as in my server instance. (I used simply optimized as I had it on the server.)
• Then I Used Flatseal to give prism rw access to the server instances folder.
• Then I deleted the mod and config folders in the prism instance and replaced them with symlinks to the server equivalents.
• I restarted prism, and updated the mods. Prism regenerated the index file. Everything worked.

I was pleasantly surprised to find prism recognized that these folders are now symlinks, though I miss the mod icons. This gives me the added bonus of being able to run a local client on prism for testing configurations. Since prism con only see those two folders nothing else is affected and prism still has it's own directory.
A really simple solution would be to add a button that could automate this on prism's end. Flatseal would still have to be done manually since prism doesn't know where a users server install is by default. A tooltip can solve that.

[P3rf3ctXZer0]

I'm doing this. As a 'power user' I am taking on the responsibility of vetting that mods I'm downloading are compatible with servers.

• First I created an instance in Prism with the same fabric version as in my server instance. (I used simply optimized as I had it on the server.)
• Then I Used Flatseal to give prism rw access to the server instances folder.
• Then I deleted the mod and config folders in the prism instance and replaced them with symlinks to the server equivalents.
• I restarted prism, and updated the mods. Prism regenerated the index file. Everything worked.

I was pleasantly surprised to find prism recognized that these folders are now symlinks, though I miss the mod icons. This gives me the added bonus of being able to run a local client on prism for testing configurations. Since prism con only see those two folders nothing else is affected and prism still has it's own directory. A really simple solution would be to add a button that could automate this on prism's end. Flatseal would still have to be done manually since prism doesn't know where a users server install is by default. A tooltip can solve that.

I have just doing a work around with ATLauncher Prism Launcher Combo at this point on a vm.