adamhillier / mobile-network-game Goto Github PK

Currently, the price of a tower (of any type) is taken from the contents of #towerPrice and updates to the price update the contents of #towerPrice. This is problematic if we want to show the same price in multiple places and is not good code organisation. We also don't have a system to give different towers different prices because of this.

It would be better if the price of a tower were stored as a variable, or an array used to store the prices of each type of tower. These values would still have to update relevant parts of the page when they are changed (say, all elements with classes tower1price, tower2price, or perhaps towerPrice1, towerPrice2).

This HTML vs. JS issue also applies to the balance and the month, although fixing these is less of a priority since we don't currently display them in more than one place. However, these may need fixing when stuff from the sidebar is moved into help/game start/game over screens.

To be done in the last step (after implementing other features/tasks).

• more initial balance (but constraint on number of towers you can place?)
• cost function
• population increase

different types of towers can have different range(radius), capacity, price.

• Appropriately scale roadmap node coordinates for the OSM query boundary box parameters
• Filter out roadmap connected components with sufficiently low node count
• Colour or otherwise enhance background roadmap svg

• with more even road density

• game "pauses" when window.onblur (by setting sprite speed and call probability to 0)
• but time elapsed doesn't pause
• player can get longer time recorded than their actual survival time

this issue has been mentioned by someone else earlier in Slack. I'm opening it here on Github so we don't forget about it.