olink/projectfluctlight

projectfluctlight's Issues

Project name issues

Project Fluctlight consistently sounds like "Fucklight" or "Fleshlight" when attempting to explain to friends what it is.

Suggestion: rename to different name.

Implement views for user registration, and user login

Requirements:

• Rendering is complete(#1)
• Implemented user registration logic(#5)

Reason:
Users need to be able to log in, which requires a user interface.

Implement a database of some sort.

Requirements:
None

Reason:
Need a backend storage for everything.

Implement the stuff for rendering webpages

Requirements:
None.

Reason:
Need a view for our model.

Tasks:

• sinatra
• ...

Save skills to the database, linking to a users account.

Implement Skills and Proficiency System

Create a skill system that tracks proficiencies. It should be expandable and easy to add new skills to.

Requirements:

• Database (#4) to keep track of each player's skills.

Reasons:
We should have the ability to track skills and their levels. This is important in order to have player classes and player crafting.

Notes:
Preferably, the system should include these things:

• It should be easy to expand.
• It should allow for skill prerequisites.
• It should allow for skill progression.

Rest api

Long term task/discussion.

I think shipping a desktop/mobile app of this project down the road would be nice. While making a mobile version of the web page is a safe solution, implementing a desktop app requires an api for us. I think the safe bet is to create one around a rest api.

Implement User registration

Requirements:

• We can save data to a database(#4)

Reason:
First step in having a running server

What should our first game feature be?

Discuss:

• Crafting?
• Adventuring?
• Town management?
• Other?

Implement queued database operations per user/subsystem

Requirements:

• Database is implemented (#4)

Reason:
Since this game is web based, all requests will be async. We need to be able to ensure proper behavior, should a player open 10 tabs and click the buttons all at once. This demands that each response is blocked on a queue of database operations for that user, such that we do not get some weird bugs where they can buy things for free. It is per user for most operations, but things such as towns and stuff will need to be queued for that specific object.