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

Open
opened 2013-06-12 06:01:14 +00:00 by StevenRS11 · 2 comments
StevenRS11 commented 2013-06-12 06:01:14 +00:00 (Migrated from github.com)
No description provided.
SenseiKiwi commented 2013-06-13 01:39:34 +00:00 (Migrated from github.com)

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.

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 commented 2014-07-08 08:46:00 +00:00 (Migrated from github.com)

Done. Commands have been reviewed and polished.

Done. Commands have been reviewed and polished.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: apex/DimDoors#10
No description provided.