-
Notifications
You must be signed in to change notification settings - Fork 42
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
mines are not reloaded correctly #2
Comments
That means the level is no longer loaded, there should be a better error though. |
I need help ASAP people cant destroy my mine blocks dont know y please help I just doent let them |
On mcpe |
@WazzyWaffles I have a busy life to keep up with. I will get to this when I have time. I understand that it is important to you and will strive to get it done. |
I have a server to run I just need help please :( and how long will it take
|
@WazzyWaffles I tested your issue on a clean installation of the latest dev build and could not reproduce. |
Wat does that mean
|
And how do u set reset time on minereset
|
that happens after you restart the server... set up a mine, reset it, will work, ok... |
@iVertx Thanks. |
ok, I found the fix by myself the fix that i found for this issue is deleting the original ./level.dat from the world that yor mine are located (probally PC Imported), and restarting the server, pocketmine will regenerate this file with the correct name by itself if your world are properly documented on pocketmine.yml, and the plugin will load fine. |
[CODE] |
it worked at first but after I restart the server it gives me this message 14:39:39 [NOTICE] InvalidArgumentException: "Argument 4 passed to minereset\Mine::__construct() must be an instance of pocketmine\level\Level, null given, called in phar://D:/san andreas/PocketMine-MP/plugins/MineReset_v2.0.3.phar/src/minereset/MineReset.php on line 177 and defined" (E_RECOVERABLE_ERROR) in "/MineReset_v2.0.3.phar/src/minereset/Mine" at line 13
and after that it stopped working I redownloaded it but it did not help
The text was updated successfully, but these errors were encountered: