thaewyn / operation-jungle-knight Goto Github PK

Investigate tracking player stats from a run, ideally using an Observer architecture.

What stats do we track?
Where do we save them?

Allow players to voluntarily jump back to the 'select encounter' page, inform players that damage taken will not be reverted.

Once issue #3 is done, seed the database with some basic reference information for applicable tables. Dummy data is totally acceptable, as long as there are valid values in place so that they can be tested.

Right now we have the 'logout and then log back in' workaround. We should allow the user to start a new run from the front end without jank.

Build a style guide for the look and feel of the game.

• Colors, fonts, basic presentation details.
• Any other look-and-feel information that would be useful in creating the master CSS file

Will need wireframes for every current page (other pages will get their own tasks for wireframing as they are added).

• Home page
• Main Menu
• New Run
• Player Details
• Select Encounter
• Encounter
• Rewards
• Run Over
• Run History

Status effects are mostly done, going to focus this one on handling enemy attacks.

Display options for starting a new run. This page should only be accessible to players who want to start a new run

• allow input of alphanumeric 'Seed' string
• allow generation of randomized alphanumeric 'Seed' string
• Placeholders for other potential options to be selected (available "classes"?)
• When all valid options are selected, they should be submitted to the server
• on response from the server, a 'Begin Run' button should be displayed, taking the user to the Encounter Select page

Once the Style Guide is complete ( #6 ), implement the details into the /public/assets/styles/main.css

• variables for reusable colors
• font selection
• standard box model adjustments for organization
• any other generic/reusable styles as per the style guide.

In addition to the listed 'debuffs', the status effect handler should also handle enemies that can modify player stats:
'decon' = 'decrease connection', etc.

Should also handle decreasing Defense, as well as Obfuscation.

• Make sure player attacks can also apply statuses to enemies
• Check all server routes for things like res.status(500) that don't actually work the way we want.
• Investigate and confirm how Defense decays in combat.
• update database schema so that guest users work (set userId to DEFAULT NULL instead of NOT NULL)
• Create theme selector
• #19
• Create a handler for 'relics'
• Create a 'combat turn log'

If an enemy attack negatively affects Defense, Connection, Obfuscation, etc. make sure that is properly recorded in the enemy skill data model, and properly handled by the gamecontroller

Homepage will need:

• Game name (or placeholder)
• Login form (pointed at /api/login)
• Form updates after submit
• form updates on response
• Option to 'continue as guest'

Do we allow duplicate skills?
Does picking duplicates 'power up' a skill?
Do we prevent duplicate skills?

Need to finish database table initial structure for:

• hardware_ref
• software_ref
• encounter_ref
• enemy_ref
• enemy_attack_ref
• enemy_attack_list

There may be others, but those at least are stubbed out in /db/schema.sql

Suggestions for new database table/columns, to collect interesting data from player runs, such as:

• death data
  • current act/encounter at time of death
  • enemy the player was killed by
• victory data
  • run time
  • number of enemies slain

This thread should be used for suggestions for data that will not be important to the performance of the game, but rather just for the player's interest (and ours, of course). This would be used to just see general trends in game play to help with balancing, and making neat infographs.

Investigate if we need a whole new 'create account' page, or if this can be handled as an attachment to the homepage.

In the event a new page is needed:

• new html file in pages
• new route in view_routes
• new link to page on index.html

Finish the basic structure for the Main Menu page. Includes:

• ajax query to get current run information (or at least see if any is available). buttons should be disabled until information is retrieved.
• if there is a run in progress, buttons for 'continue run' and 'abandon run'
• if no run is in progress (or user is guest) button for 'start new run'
• placeholder links for things like "unlock list" and "run history"

File located in /controllers/login_controller.js will need to be updated to handle both login and logout, as well as account creation

• login method (compare input password with hashed password via bcrypt or similar)
• logout method
• create account method (create new account only if credentials are valid and username not in use, only store hashed passwords, never plaintext)