ryfry / hr Goto Github PK

Write an abstract class named "Entity" which constuctable objects like cities and mines will extend. Must contain variables and behaviors common to ALL entities; may need adjusting if future types of entities are added.

Keep this file fairly simple and general; don't try to force too much into it at this time.

All files must be commented to increase readability: all methods must have at least one line of header describing their purpose and parameters; variables and constants should have UNIFORM and INFORMATIVE naming conventions.

Determine variables and behaviors shared by all constructable entities like cities and mines.

All files must be commented to increase readability: all methods must have at least one line of header describing their purpose and parameters; variables and constants should have UNIFORM and INFORMATIVE naming conventions.

All files must be commented to increase readability: all methods must have at least one line of header describing their purpose and parameters; variables and constants should have UNIFORM and INFORMATIVE naming conventions.

All files must be commented to increase readability: all methods must have at least one line of header describing their purpose and parameters; variables and constants should have UNIFORM and INFORMATIVE naming conventions.

All files must be commented to increase readability: all methods must have at least one line of header describing their purpose and parameters; variables and constants should have UNIFORM and INFORMATIVE naming conventions.

There are many ways to make the code look fancy. Implement the following after everything is working and you have some free time.

1. Change the "Global Constants" comment at the top of GC to be made of multi-line letters.

All files must be commented to increase readability: all methods must have at least one line of header describing their purpose and parameters; variables and constants should have UNIFORM and INFORMATIVE naming conventions.

The HR file should not contain any hard coded numbers; all should be alterable from the GC file.

Practice typing in the different commands. Determine the optimal, most user-friendly syntax for typing each in (by using shorthand words, for example) and change the Command.java file appropriately.

The syntax of the commands should be geared for fast-paced gameplay, and should minimize the chances for players to hastily mistype commands.

All files must be commented to increase readability: all methods must have at least one line of header describing their purpose and parameters; variables and constants should have UNIFORM and INFORMATIVE naming conventions.

All files must be commented to increase readability: all methods must have at least one line of header describing their purpose and parameters; variables and constants should have UNIFORM and INFORMATIVE naming conventions.

Expand GlobalConstants.java to be the primary control code for the game's internal gameplay-equations such Rates of Growth, Rates of Decay, Resource Costs for building new entities, etc.
This way they may easily be adjusted for game-testing, as well as future EASY/HARD Mode capabilities.

Group constants in GlobalConstants.java according to the functions they adjust, for ease of manipulation.

Rewrite existing constructable objects like cities and mines to extend the Entity class when it is build. This should remove the need for a few methods and variables if done properly.

Overload Entity-inheriting classes' constructors so that different instances may have different internal algorithms; two cities, for example, may have different rates of growth and decay.

Standard constructors (no parameters) should be taken to mean default standards.

ALL NON-DEFAULT RATES SHOULD BE STORED IN GLOBALCONSTANTS.JAVA, AND PASSED TO NEW INSTANCES AT THE TIME OF THEIR INITIALIZATION.

Change the standing lists of string names for Cities and Mines. Bear in mind that these names need to both sound spacey and be somewhat easy to type.