Skip to content
This repository has been archived by the owner on Jan 14, 2025. It is now read-only.

Optional world type in the /mv create command #6

Open
superjag opened this issue Dec 18, 2013 · 4 comments
Open

Optional world type in the /mv create command #6

superjag opened this issue Dec 18, 2013 · 4 comments

Comments

@superjag
Copy link

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.

@dumptruckman
Copy link
Member

This will be really great especially since MV-NetherPortals is planned to be merged into MV-Core.

@fernferret
Copy link
Member

Oh nice, wasn't aware that was in the plan. I feel like it really should've been in MV2, but I was kinda obsessed with "plugin all the things!"

@dumptruckman
Copy link
Member

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.

@elliot-huffman
Copy link

A feature list would be a good Idea to clear all of it up. I even had that issue at one point :-P

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

No branches or pull requests

4 participants