Create a common design template for console output

[anthonyLuttrell]

Since most or all methods will involve the same console output style, we will need a common design template for this to maintain code consistency and so that each person/team doesn't have to re-create this from scratch. This template should meet the following criteria:

• [ ] Each printed character should have a few millisecond delay as it is printed to simulate a typing effect

  

• [ ] The game should keep an eye out for a key press (space or enter) to skip the above effect

• [ ] The ellipsis (...) should remain at the end of every sentence if it is not the last sentence in a sequence. This lets the player know there is more dialogue coming

• [ ] Every time the player presses the enter key when prompted ("Type 1 to fall back"), but not when skipping the typing effect, they should get audible feedback. This should work for now

• [ ] Need a way to clear the screen after a scene is over

[anthonyLuttrell]

Questions:

1. What is the best way to store/distribute this template once completed? Create a new branch from the main repo, or just add it to the Wiki?

2. From a design standpoint, what is the better option for after the user presses a key to skip the typing effect: a) It instantly completes the line and instantly begins the typing effect on the next line b) It instantly completes the line, but waits for another keypress before beginning the typing effect on the next line

[blackk100]

Answering 2, it should be consistent with how the text would be displayed if the typing effect isn't skipped. If the display of the next line is started without waiting for some sort of input from the user, it should preferably remain the same if the user skips the typing effect.

[EhWhoAmI]

One way we could do it is by writing our custom printstream classes. System.setOut may work.

[nylanderdev]

Are VT100 codes acceptable or do we need to support CMD?