Scanner problem.

[keo]

Hello, I am working on a terminal based game and have a problem with the scanner.

The below code is part of the "players turn". The first time the method is called for the game, it prints once and works perfectly. Then during the second calling & onwards, it prints the "Message..." and "type a command:..." lines twice before it offers me to input a string into the terminal.

if(!notComputerTurn) {
            System.out.println("Message...");
            System.out.println("type a command: play, move, exit");
            String keyWord = scan.nextLine();
        
      if(keyWord.contains("play")) {
              int number scan.nextInt();
          ...
        }
        ...
}

I have been trying to fix this for hours... Im working in netbeans but have also taken it to bluej and used that debugged to trace, it simply skips over it the first time (after the second time its called).

Whats wrong?
Thank you.

[Junky]

Do you call nextInt or nextDouble anywhere in the code you omitted?

[keo]

Oops, I wrote my code wrong, but yes, there is a nextInt is that the problem? Thanks for helping.

Wrong:

      if(keyWord.contains("play")) {
                        String keyWord = scan.nextLine();
                          ...
               }

Correct:

              if(keyWord.contains("play")) {
                      int number scan.nextInt();
                      ...
                }
...

[Junky]

Yes nextInt is notorious for causing headaches. If user enter 9[enter] the nextInt method reads the 9 but not the enter. The next time you call nextLine it reads the empty String between the 9 and enter and carries on as if user had entered something. Solution: after the call to nextInt make a call to nextLine and throw it away.

[keo]

Thank you so much Junky! :):):):):)

I have spent so many hours just trying to fix this bug, and I would have never of fixed it without asking :rolleyes:.

[DarrylBurke]

I would have never of fixed it without asking

Learn to search the net intelligently. Google gives a truckload of useful results when searching "nextint nextline problem"

db

[keo]

Learn to search the net intelligently. Google gives a truckload of useful results when searching "nextint nextline problem"

db

But I had no idea that nextInt() was causing the problem.