Skip to content

Milestones

List view

  • Make code run quicker (check your algorithmic complexities!) and more elegant where possible (as is "do the same amount, with less").

    No due date
    0/1 issues closed
  • The internal mechanics of the game, the equations which determine rates of change and costs, must be represented with variables in a primary control block. This way, if an adjustment is needed, only the hard-coded value of the variable must be changed in the control block, and the update thereby cascades through the code. Furthermore, any ways in which the game can be made more modular (i.e. anyway the code can be broken down into swappable, adaptable chunks) should be debated, outlined and if approved by the group, implemented.

    No due date
    0/3 issues closed
  • All code must be commented to ease readability and section off important sections of code wherein bugs may be found. A naming convention must also be adhered to, as well as uniform indention. All this is for clarity purposes. Future programmers will benefit from seeing this code, should the project expand in scope.

    No due date
    0/8 issues closed
  • Create a superclass for the game's constructable objects like cities and mines. Future tpyes will also inherit from this class so it should contain ONLY those features that would conceivably be shared by all types.

    No due date
    0/3 issues closed