You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2025. It is now read-only.
Basically, as it seems to me, the world type option in the /mv create command is extraneous. It would be a lot simpler (for the average user) if the type were automagically detected based on whether the world name ends with "nether" or "the_end". The type option would just override this behavior.
The text was updated successfully, but these errors were encountered:
All too often people are wondering why their worlds aren't pairing up (like what mv-np offers) when they only have core... Having to telling them to get another plugin for what obviously seems like should be the default just seems odd. Also, there are options in mv-core that don't even do anything without mv-np (scale, for one) so that's also odd.
See: Multiverse/Multiverse-Core#1348
Basically, as it seems to me, the world type option in the /mv create command is extraneous. It would be a lot simpler (for the average user) if the type were automagically detected based on whether the world name ends with "nether" or "the_end". The type option would just override this behavior.
The text was updated successfully, but these errors were encountered: