@ -28,11 +28,13 @@ More examples can be found at the following links:
What is important to note here is the importance of the command-method names. The names you use are the exact same commands your end-user will enter at run-time. The console's input is, also, case-sensitive. This means you can have two command-methods called `Test` and `test` and have them do different things.
![screenshot of command-method and console commands](attachments/code-and-console-sync-screen-shot.png)
![screenshot of command-method and console commands](attachments/method-mapping.gif)
Another feature of C.W.C. is it parses and coerces input arguments. This means your command-methods can include arguments and C.W.C. takes care of the error-handling and messaging for you.
![screenshot of error-handling](attachments/error-handling-screenshot.png)
![screenshot of error-handling 1](attachments/invalid-command-input.png)
![screenshot of error-handling 2](attachments/invalid-arguments-input.png)
To be clear, there are limits to the amount of types you can use with your command-methods. For a full, list of all the coercion types, please refer to the Coercion Types List in the main Console.Waterworks wiki. The link for it is as follows: