A nightmare of /reload ..

Hello, I'm an intern op of a Korean skyblock server, probably will be fired in next few days.​

I work in this server for a year now, with op internship started 2 weeks ago.​

Now I'm going to lose all of that because of /reload.​

​

As our server requires economy we use Vault, iConomy 6, AuthMe. Few days ago iConomy got sick and weren't working well. I typed /reload with stupid attempt to fix it, iConomy data and some of AuthMe were blown. Evaporation, nearly.​

​

With chaos I rebooted the server. This time, AuthMe's data evaporated. I wasn't even an op anymore. NOOOOO!​

​

What happened next? Angry users throwing eggs at me, angry CEO's call, half-forced night-shift for investigation.​

​

Quote from his call:​

HEY, YOU WANNA DIE?

Ooooh, I'm gonna be slaughtered.


Main part,

This isn't just me facing this problem. Here's a thread posted 3 years ago.​

https://forums.bukkit.org/threads/petition-to-remove-the-reload-command.43212/​

Another:​

http://www.minecraftforum.net/forum...ion/1926757-server-errors-after-server-reload​

​

Long story short, /reload need to see a doctor or something.​

​

 

JinLee1224
There is nothing wrong with /reload in general. It's only that most plugins don't handle a reload pretty well.

However, I'd question a few things:
1. For what do you need AuthMe? This plugin has close to 0 legal use cases.
2. /reload can do a lot of things, but that 2 popular plugins use all their data is highly unlikely
3. What kind of company (because of CEO) does host a server without making any backups? If there is someone responsible for your crash it's most likely the guy who made the backup strategy.
4. "HEY, YOU WANNA DIE?" can be enough to send a SWAT team...

 

Good response. I would never trust /reload unless you knew exactly how each plugin worked. I explicitly disable it along with /stop so admins don't accidentally issue them (i.e. restrict to console only).

Although you made a mistake using it, and it would stand reason to delay or cancel op privilege until the situation blew over, the owner's response seems ludicrous. Best you can do is say the truth: "Sorry, I didn't know /reload would do that."

Kudos for Syd's response on backups. That should be a top priority for running a server. Question shouldn't be if to make backups but just whether to do full or incremental, and how often.

 

OK,
1. Actually, I don't know. It's just there. I'm not in the plugins team.
2. Umm, I guess you're right, but it's not just plugins get broken on /reload. Read the thread
3. Bad MySQL Server.
4. Haha, he was that mad when he heard the news.

 

I'm not too sure what sort of an operation your "CEO" is running. You mind sending me a link to any of his official stuff? Because something just smells of illegality. "Intern OPs"? WTF? Threats to kill you? I just don't have a good feeling about this. At all.

 

Well, I'm not sure where to find that sort of link, but it is a real company (we even have a small IDC!)

There's only one time our CEO offended law, DDoS-ing another server. He never explained about this.

Since people seems to take you-wanna-die seriously I'm pretty sure he had nothing in his mind.. or was he? Heheh. Joking. From a year of time me being with him, what I know is that he's not a person to do that. Still curious about DDoS though.

* EDITED - Found misspellings.

 

DDOSing servers, death threats, and offline mode servers... OK then.

 

Necrodoom JinLee1224 Yes, I must say this seems awfully odd.
But regardless, the reload command isn't likely to be removed. If you want it removed, just use the commands.yml file. I understand the reload is notoriously bad, and I never use it, but it is there for a reason, and some people do use it. How would those people feel about getting rid of it?

Also, what exactly is an intern OP? Generally the only time you hear of an internship is when you are working for a company to gain skills during college.

 

ZanderMan9 Even if it was removed, it would take about 6 seconds to make a plugin to add it back.

 

The reload command can work with some plugins and also could be useful for quick testing with few/simple plugins on.
For me the possibiltiy of plugins not taking reload into account in a sufficient way, cross-plugin dependencies with CB not knowing, class-loader questions make me not use it for live/production servers.

 

1. This is a game, meant to have fun on.
2. /reload works perfectly.
3. All good server owners know that restarting is better than reloading.
4. If the owner is that unmature because of a silly mistake, I wouldn't worry. Server won't get popular.

OP Internship..? Refer to #1. Obviously I can tell you and that "CEO of a Minecraft Server", take this game too seriously.

 

Lol this is why I don't have ops. It's all based on permissions.

 

Problem starts when somebody reloads the server and then go complain to some random plugin developer just because server crashed and there was a mention og plugin name somewhere in the log.
I think the commands reload should be blocked by default and allowed only by adding a propery flag.

 

/reload = memory leak of doom