You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2019. It is now read-only.
The SMS app works like an old school text based RPG. Where it recognizes a series of commands and performs prescribed actions based on the commands.
For example the command "stop bus " returns the next 3 times (in hours and minutes) that the bus will arrive at the stop.
What other commands should there be and how should they be formatted?
"stop " has already been suggested to do return the next 3 buses arriving and at what time.
I've also thought of "stop at at " should return the stop IDs for the south bound and north bound stops. For example: "stop at NW 79 st at 7 ave"
NOTE: the spaces in the commands are important. It's how the app separates the words for translation and to figure out the pattern of the commands. So in the example above "79st" is not the same as "79 st".
The text was updated successfully, but these errors were encountered:
The SMS app works like an old school text based RPG. Where it recognizes a series of commands and performs prescribed actions based on the commands.
For example the command "stop bus " returns the next 3 times (in hours and minutes) that the bus will arrive at the stop.
What other commands should there be and how should they be formatted?
"stop " has already been suggested to do return the next 3 buses arriving and at what time.
I've also thought of "stop at at " should return the stop IDs for the south bound and north bound stops. For example: "stop at NW 79 st at 7 ave"
NOTE: the spaces in the commands are important. It's how the app separates the words for translation and to figure out the pattern of the commands. So in the example above "79st" is not the same as "79 st".
The text was updated successfully, but these errors were encountered: