mablay / bitcoin-clicker Goto Github PK

Which option would yield more fun?

Currently, certain game stats are updated every day (game interval).

A higher refresh rate of said stats would yield a more convenient user experience.

Example: BTC Savings, Network hashrate and BTC price vary within a day and not just at the end of each day.

Since internally a reduction of state changes is desired, any user interaction requires a state update to avoid data inconsistencies. Example: view just used displayed that a product can be bought, while the game state still holds an insufficient balance. A purchase would fail unless a state change occurs right before the action. This would also requires some checks like "isAffordable" use state extrapolation to reflect the displayed game state.

At the beginning of the game, the screen is cluttered with unnecessary controls confusing the user.
Hide control elements / info text until it becomes relevant.

This could be realised by mapping show-requirements into the tech tree or a similar structure.

Example: "Rent a flat" should not be shown before space 10 / 10 is reached and new space needs to be acquired.

charge bills monthly instead of daily.

The PWA was created using the vue cli version 3.0.3 with PWA option selected.

Deploying to gitlab pages required vue.config.js:baseUrl to change from "/" to "//".

While develop and production deployments render as expected in Google Chrome Mobile and Desktop, installing the PWA on Android 8, yields only a blank screen while the console indicates no errors.

Expected behaviour: Application renders similar to the non-PWA version.

GPUs hashrate should be added to the users hashrate after the GPU has been deployed.

Activities and events should be underlined with audible effects.

Ambient music would contribute to the game mood.

Mute all sounds option in settings

• Mining rigs can be bought but not deployed.

In History component,
use metric prefix to nominate BTC trade volume.

Change

sold 0.0001 BTC for $0.10 USD

to

sold 100 µBTC for $0.10 USD

Show achievements to reward players and track progress.

If the players balance turns negative by paying monthly bills:

1. Indicate imminent doom with due date (e.g: today + two weeks)
2. Game over if balance is still negative on due date.

By 2018, GPUs don't seem to yield more than 800 GHps.

Adjust tech tree accordingly.

The user should be able to leave the game (close the browser tab) and pick up later were he/she left at any later point without worrying about lost game status.

onbeforeunload + localStorage seems a good fit.

window.onbeforeunload = () => {
   window.localStorage.setItem('gameState', THE_GAME_STATE)
   return null
}

The user should be able to research automation technologies for repetitive tasks like deployment.

A maintenance worker could deploy x devices in y time automatically while causing z costs.

https://schema.org/Game

https://megatags.co/

https://css-tricks.com/essential-meta-tags-social-media/

Red for dropping price
Green for raising price

Navigating from game screen to settings screen causes clockwork to halt.
Ongoing button progress is not properly resumed on game screen re-entry.
=> progress stuck, does not finish, cannot be canceled, dead end.
persisting progress on navigation via vuex might be a solution.