Hallo,
Just for the record, I appreciate all that has been done to fix the plugin closing problem. It's way better than it was when this first started.
However, often the problem occurs that the plugin will close when there isn't an admin around. Our practice has typically been to bug the hell out of any admin who is available, and although this usually works, I don't think it's sustainable.
I know votes are not typically allowed by non-admins but I think an exception should be made here. I'm not sure which command it would be best to use this on, but I think a callvote to restart the plugin/server/whatever could fix this problem.
That said, I understand that votes are a completely different animal, so feel free to tell me that my idea is stupid (legitimately, I know nothing about how to go about doing this, so feel free).
Thanks,
PiB
Just for the record, I appreciate all that has been done to fix the plugin closing problem. It's way better than it was when this first started.
However, often the problem occurs that the plugin will close when there isn't an admin around. Our practice has typically been to bug the hell out of any admin who is available, and although this usually works, I don't think it's sustainable.
I know votes are not typically allowed by non-admins but I think an exception should be made here. I'm not sure which command it would be best to use this on, but I think a callvote to restart the plugin/server/whatever could fix this problem.
That said, I understand that votes are a completely different animal, so feel free to tell me that my idea is stupid (legitimately, I know nothing about how to go about doing this, so feel free).
Thanks,
PiB