[SPIGOT-460] Generators still linked to Classloader Created: 22/Jan/15  Updated: 25/Jan/15  Resolved: 25/Jan/15

Status: Closed
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: MattBDev Assignee: Thinkofname
Resolution: Won't Fix Votes: 0
Labels: Craftbukkit, bug, chunkgen, world


 Description   

On /reload the worlds have their their generator still linked to the old classloader. This can cause issues with some generator plugins.



 Comments   
Comment by Thinkofname [ 25/Jan/15 ]

A warning was added

Comment by MattBDev [ 22/Jan/15 ]

You would think a server owner would know better but they don't. Some of them have no clue what they are doing. I have seen some sever owners with issues that you would just laugh at because they are so ridiculous. It is just astonishing.

Comment by md_5 [ 22/Jan/15 ]

First result for "bukkit reload" on Google:

http://bukkit.org/threads/petition-to-remove-the-reload-command.43212/

I can't see any reason why a server owner would assume that it is safe.

Comment by MattBDev [ 22/Jan/15 ]

Many servers think that the reload command is a safe way to update plugins or configurations instead of a hard restart. I think it should be mentioned while executing the command that it's use is not recommended.

Comment by md_5 [ 22/Jan/15 ]

Because some people like to use it for development or quick testing.

It wasn't us that wrote the command, Bukkit added it over 3 years ago. No one has recommended it be used for at least 2 years.

Comment by MattBDev [ 22/Jan/15 ]

Why have reload at all then?

Comment by md_5 [ 22/Jan/15 ]

Yeah....... there isn't a way to solve this, which is why reload is broken.

For example, what if you reloaded and deleted the plugin providing the generator. Your world is f****d.

Generated at Sat Apr 05 06:16:29 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.