-
Notifications
You must be signed in to change notification settings - Fork 4
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
Player String Processing #36
Comments
would you describe the issue more clear? @robinje |
What I put together for the first part was just to send all of the user input to lower case, which isn't great for players expressing themselves with the say command. My general thought is that the lower case should be applied at the testing for verbs. If say is the first verb everything after that should be left as is and sent back through the system in the provided case. |
I was curious that if i could participate to this repository but I had problems running it on my local. If you provide the steps to get the software up and running in the README.md file, I may contribute. Cause it sounds fun. |
@efeertugrul I have added the deployment instructions to the README with PR #52. I also created Issue #51 for a non-AWS deployment. |
Currently string input is simply lowered for processing. This approach should be refined to allow the players to send messages in any desired case.
The text was updated successfully, but these errors were encountered: