Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gather requirements for project #2

Open
MylesFTOP opened this issue May 26, 2020 · 3 comments
Open

Gather requirements for project #2

MylesFTOP opened this issue May 26, 2020 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@MylesFTOP
Copy link
Owner

Following planning and discussions with friends on what the toolkit needs to do, this should list requirements and priorities.

@MylesFTOP MylesFTOP added the documentation Improvements or additions to documentation label May 26, 2020
@MylesFTOP MylesFTOP self-assigned this May 26, 2020
@MylesFTOP
Copy link
Owner Author

Requirements

  1. Takes character ability stats and other character attributes
  2. Players need to be able to store, upload, and edit multiple characters
  3. Character sheets need to be publicly visible (either to everyone, or to a select group of users - e.g. friends list)
  4. Stats need to track automatically based on player input and calculation rules from the rulebook (e.g. class and race abilities, modifiers with and without level, icon relationship roles, spell usages)
  5. Uses dice rolls to generate stats for characters and return results on actions (e.g. attacks)
  6. Can group multiple players under a campaign (with one player designated as a GM)
  7. Items, spells, etc need to be assigned attributes (e.g. bonuses to ability stats

Questions

  1. How many characters can a user create?
  2. What sort of frontend should this have?
  3. Where will the data be stored?
  4. Will a GM be able to change anything (either in the characters or overriding the rules)?
  5. Will users have a friends list function?
  6. Will this have user accounts? How will they be created and authenticated?

@MylesFTOP MylesFTOP pinned this issue May 26, 2020
@MylesFTOP
Copy link
Owner Author

Design

Structure: Class Library, initially with Windows Form application for proof-of-concept, later ported to website
Data: SQL
Users: Initially one per application, later multiple users on website

Key concepts

  • E-mail
  • Web hosting
  • SQL
  • Custom Events
  • Error Handling
  • Interfaces
  • Random number generation

@MylesFTOP
Copy link
Owner Author

MylesFTOP commented May 26, 2020

Class structure

Character

  • Character name (string)
  • Character ID (int)
  • Player (User)
  • Character race (CharacterRace)
  • Character class (CharacterClass)
  • Ability stats (List<AbilityStat>)
  • Attributes (List<Attribute>)
  • Icon relationships (List<IconRelationship>)
  • Backgrounds (List <Background>)
  • Feats (List<Feat>)
  • Talents (List<Talent>)
  • Skills (List<Skill>)
  • Spells (List<Spell>)
  • Items (List<Item>)

User

  • Username (string)
  • User ID (int)
  • E-mail address (string)

Campaign

  • Campaign name (string)
  • Campaign ID (int)
  • Players (List<User>)
  • GM (User)

@MylesFTOP MylesFTOP added this to the Character sheet milestone Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant