Skip to content
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

Could not queue reset for A #120

Open
z0mbieslayer opened this issue Mar 31, 2019 · 14 comments
Open

Could not queue reset for A #120

z0mbieslayer opened this issue Mar 31, 2019 · 14 comments

Comments

@z0mbieslayer
Copy link

So i have looked at all of the other issues for this problem and they all suggest that the world isnt loaded. However I am having the same problem as them except my level IS loaded. In fact, it my main world. Any help would be greatly appreciated!

@falkirks
Copy link
Owner

falkirks commented Mar 31, 2019

This can be caused by three things

  • The world isn't loaded.
  • The mine is already resetting.
  • There is a problem with how the mine was setup (ie: the ratio data is bad).

I am leaning toward it being the last one. Could you tell me the full command you used to set the mine? It would start with mine set.

@z0mbieslayer
Copy link
Author

This can be caused by three things

  • The world isn't loaded.
  • The mine is already resetting.
  • There is a problem with how the mine was setup (ie: the ratio data is bad).

I am leaning toward it being the last one. Could you tell me the full command you used to set the mine? It would start with mine set.

Thanks for responding! I used the command mine set 1 75 16 25

@falkirks
Copy link
Owner

falkirks commented Apr 1, 2019

That should be mine set A 1 75 16 25 if the name of your mine is "A". Have you tried that?

@z0mbieslayer
Copy link
Author

I might have, let me try again

@z0mbieslayer
Copy link
Author

That should be mine set A 1 75 16 25 if the name of your mine is "A". Have you tried that?

Did that command, still doesn't work. Ive used this plugin before and it worked fine in the past, don't know why it's acting up now

@falkirks
Copy link
Owner

falkirks commented Apr 2, 2019

Hmm weird. Could the world have changed name since the mine was setup?

@z0mbieslayer
Copy link
Author

I don’t think I did. I immediately tried to reset the mine after I set it. I can send you the server files if you’d like.

@Rubylium
Copy link

i got the exact same problem.

@Rubylium
Copy link

After doing some test i found out that the error only come on an downloaded world, for exemple i downloaded an pre build prison mine world made on the PC version of MC, on it i got the error.
On an generated world by MultiWorld plugin the error is not there and the plugin work great

@Rubylium
Copy link

Aaaaaand i just got it fixed using the MultiWorl command "Fix name" :)

( /mw fix [Name of your world] )

@Chuckeymomo
Copy link

I found the same issue but Multiworlds “fix name” does not work for the PocketMine version of Minecraft. Is there any way I could fix it without that command?

@Chuckeymomo
Copy link

Never mind I fixed it by copy and pasting the mines to a multiworld-generated world

@Chuckeymomo
Copy link

And that fixed the issue.
Thanks so much for this great plugin falkirks
😃

@ExileWeb
Copy link

ExileWeb commented Oct 8, 2020

See PR #129. After looking at the source and modifying my config the fix uses the Level getFolderName which means PC-imported worlds that are loaded can be reset.

Don’t think it should affect PM worlds as they have the same name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants