Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
designproject20182019quarter1mud
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Design Project - 20182019 - Quarter 1 - MUD
  • designproject20182019quarter1mud
  • Issues
  • #96

Closed
Open
Opened Oct 25, 2018 by Kevin Booijink@s1598244Owner
  • Report abuse
  • New issue
Report abuse New issue

[Optional] Changes to quest system

Instead of having a 'minimalstorylevel' indicating whether a quest is accessible or not, we could have a list requiredQuests showing what quests need to be completed before a player can start this one. This will allow for multiple storylines at the same time, sidequests, etc. Obviously, all player-quest relationships will have to be put in the database as soon as a new character is made, or as soon as a new quest is released. Easy for mudCharacter, for Quests: Check for all quests & mudCharacter combinations once the bot is deployed. If a combination is not present, create it and set the completed boolean to false. Probably too big of an overhaul to start on this late in the project.

Edited Oct 25, 2018 by Kevin Booijink
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: designproject20182019quarter1mud/designproject20182019quarter1mud#96