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

Commands are terribly clunky, and break if not entered properly #10

Open
StevenRS11 opened this issue Jun 12, 2013 · 2 comments
Open

Commands are terribly clunky, and break if not entered properly #10

StevenRS11 opened this issue Jun 12, 2013 · 2 comments

Comments

@StevenRS11
Copy link
Owner

No description provided.

@SenseiKiwi
Copy link
Contributor

I can handle this with ease. The main issue is that before we get around to coding up commands, we should be sure of what commands we want and how they will work. For instance, players have proposed that the properties of a schematic be defined by signs inside the schematic, rather than by its file name. I'm not sure I agree with this, but regardless, we should be clear on how we want to proceed.

@SenseiKiwi
Copy link
Contributor

Done. Commands have been reviewed and polished.

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

2 participants