Economy clicker game

[Moniarchy]

Description

This project would have you reverse engineer a game that is text based.

1. http://orteil.dashnet.org/cookieclicker/

The above is an example.

Context

This is important because creating this game would allow you to focus mainly on an interactive language and how it interacts with the elements on the page, which change over time. You would learn how the functionality of certain parts of the code depend on each other.

Specifications

• [ ] As a user, I can save the game.
• [ ] As a user, I can "buy" items that increase the counter rate.
• [ ] As a user, I can see the amount of "currency" I have.
• [ ] As a user, I can reload my game data.
• [ ] The game increases currency depending on an algorithm that calculates the rate.

  Stretch Goals

  Required

• [ ] The artifact produced is properly licensed, preferably with the MIT license.

---

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

[shereefb]

Consider giving reviewers more information to figure out what quality looks like. Is it about test coverage? Is it about not using frameworks? Is it about the UI look and feel?

For example, you can create a quality rubric like this: UI/UX: 100pts Test Coverage: 100pts Good file organization: 50pts Good variable and function names: 50pts Code is object oriented: 75pts No bootstrap or other UI framework: 100pts

[Moniarchy]

@bluemihai @deadlyicon @jrob8577 Is this ready to move out of draft?

[Moniarchy]

@pllearns @Jusdev89

[Moniarchy]

@Anasauce

[pllearns]

I think that it should be implied that either this goal needs to be written in HTML/CSS alone(as in the title) or having the team members determine the language they would like to create this in (as in the second spec). You could also continue the user story expression for the specs, and give the team total autonomy as to how they want to create the app.

[jrob8577]

This feels like a meta-goal to me - it describes a goal description instead of a goal itself. For me, this goal would be perfect if it described the game, rather than requirements around building an arbitrary game.

[phoniks]

I moved this out of draft! I think the basics are there, and we can flesh out the details as a group.