I do not see why you would need to do that in the 'world' class; but would work. Using 'new World()' first would not work because the case is wrong for your subclass of World and an error will ensue saying 'World' is abstract and cannot be instantiated. Even then, if you used 'new world()' to create a new world, it would not be able to find the 'playGame' method because you are assigning it to a field that holds a 'World' object instead of a 'world' object. And then, further, if you did use this: you would lose all the data input by the user because it is in a different 'world' object (as the data is not in the newly created one). Actually, the second line in the above two-liner would never execute, as creating a new 'world' object will restart the options process. This will continue until the non-fileDialog option is taken.