EnderEyeGames

Positive: Easy advertisement to players within Minehut, no need to deal with server lists and stuff Negative: Useless web GUI for managing your server, very poor price-to-performance compared to hosting on a PC or buying non-MH hosting, limited freedom to configure the server. As for the very poor performance, I used a simple benchmark of selecting a given area and regenerating chunks with //regen -b (random number), overwriting the chunks, and then using the performance info at the end to calculate the speed. Compared to a localhost server, the free MH server was more than 10 times slower than the localhost server to generate 64 chunks with FAWE, and simply could not generate 1024 chunks due to memory limitations whereas the localhost server handled it quite well. Also, there's basically no transparency as to what specs the server plans have other than RAM.

Yes, I recognize that the purpose of this is to prevent people from advertising servers that are not free OP as being free OP to troll them. However, actual free op servers are also blocked as an unintentional side effect, not to mention that people will always find new ways to troll servers. It is especially strange that the word "freeop" being in a server name in /ad causes it to be blocked, since a server that is named "freeop" most likely does actually give free OP. I did change the server name to FreeRoot1, a reference to the root user on a *nix system, since this clearly isn't going to be fixed anytime soon.

This is simply false, even in the "stuck offline" state you can access the Plugins folder, install plugins, and create skripts. Skript reloads all scripts on boot, so even if you can't execute commands, it will work.

IMO, "Force Hibernate" should mean "SIGKILL (Immediately terminate the process with no warning or time to save anything) the Java process, whatever data loss that might cause, then immediately hibernate". However, it doesn't, so it really doesn't belong in Danger Zone at all. If you can't enter a console command before the server crashes, add a Skript to execute the solution (e.g. execute console command "minecraft:kill @e[type=!player]") "on server start". Force hibernating, then just waiting a while usually allows it to hibernate. Then, start it up and your Skript will fix the problem.

Try and give yourself -sv.* and see if that solves the problem. It could very well be that you can't PvP while in SuperVanish. Additionally, I recommend cutting down on the number of plugins by implementing them in Skript; the more plugins you install and don't configure, the more inexplicable problems you will have and the harder it will be for us to troubleshoot it.

1. This doesn't actually do what they want. They need something that makes the spawnpoint one thing for the first join and a different thing for subsequent deaths. 2. "if player has permission example.permission" in a command event should be avoided, instead use the built in permission mechanic: command /troll <player>: permission: sktroll.troll permission message: &4[&6Troll&4]&c You have no permission. trigger: # do trolling stuff

PaperSpigot servers often break commandblock-based maps even when command blocks are enabled. You will have the best chance of success if you go into paper.yml and set everything to vanilla-like behavior as opposed to "optimized" or "exploit preventing" behavior. For example, you should set piston duplication and headless pistons to true. You could break your server if you mess it up, but this wouldn't be too big of a deal if you make a backup first so you can restore quickly.

In fact, resetting the world will also do absolutely nothing to the rest of your server's configuration. It only deletes the world folders, which will cause them to get regenerated on the next restart.

This is a built in feature of the Essentials plugin. If you're not willing to recreate things in Skript, Essentials is recommended for any server. You will also need a permissions plugin (PermissionsEX is ideal) to grant the relevant permissions for any Essentials command you want players to be able to use. This also requires the Vault plugin as a dependency. To create a warp, use /setwarp (warpname).

This is false, the /spawnpoint [player] [coordinates] command does exactly this.

A pressure plate on a command block is a really bad way to accomplish this. Are you sure command blocks are enabled? Even if they aren't and enabling them "fixes" it, it would be far better to use a Skript that uses the first join event.

If you use EssentialsSpawn it may override /setworldspawn. In that case, it is /setspawn. If you don't know what that is, you likely don't need to worry about it as you haven't installed it. There is a gamerule called spawnRadius that will disperse players in a small radius near the world spawn. This isn't ideal for servers, it is advisable to do /gamerule spawnRadius 0 so the spawn point is predictable.

Someone else with a similar problem solved their issue by force hibernating their server, then starting it up and doing minecraft:kill @e[type=item] in the console as soon as possible.

You need to press the Force Hibernate button to force stop the server. This will allow you to start from hibernation again. Edit: oof i posted this before i refreshed the page

That message generally means the server is not hibernated, but it is either offline or crashed. If it shows as "offline" and you can edit your server, you may want to create a Skript which kills all entities on server startup.