-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document differences to vanilla and how to get closer to vanilla again #325
Comments
this could also be handled via way to install paper via a preset (which would be a new paper feature that needs to be discussed) |
What do you mean with "preset"? You mean that you can define plugins, config etc. which will automatically apply on first server start? |
yes, altho we are not sure that is a good idea (we wouldnt recommend plugins, just config) and a good doc page will get us a to help 80% of people anyways |
see also #21 (basically the same thing, but dead for 2 years). I might be too cynical but I do not believe a page like this can be conclusive and should have a warning on the top saying that if you are after complete vanilla behaviour, you should use fabric or vanilla. Without that I see it causing additional frustration for people who want a completely vanilla experience. It could still be very useful for people who don't need that, though. |
Yeah, to get the closest Vanilla experience, it should just be a recommendation to use Fabric. In case people wish to use plugins or enjoy the optimization from Paper, the idea of having a preset feature would be kind of nice. I can say that the demand for a Vanilla-like Paper server is there, as one of my blog posts has one of the most hits via Google search, so having something official would indeed be nice. For example, Spigot has very low player tracking range (48 blocks) and is one of the most common question asked in Paper-help. Maybe a feature "preset" could've include a higher default value for server owner seeking Vanilla-like experinece (?) If anyone is interested in the blogpost mentioned, and want to take ideas from it for this PR, here it is. |
Oh yeah, closing in favor of the linked issue |
Kind of a one stop shop kinda deal with an intro on why stuff is different (history of cb/spigot, why do we fix exploits, tradeoffs for performance), some example of what is different and a list of all config options with copy-paste examples (with links to the config page) we suggest tweaking to get closer to vanilla again
The text was updated successfully, but these errors were encountered: