Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Geike Geike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • f00f
  • GeikeGeike
  • Issues
  • #24
Closed
Open
Created Apr 15, 2019 by Luc Everse@wuklOwner

Custom probability classes

Guilds should be able to add and change probability classes. "zelden", "soms", and "vaak" may not be enough for guilds who have a cultish obsession with a certain song or want a one-in-a-million chance of starting a 10-hour song.

Rebuilding the p total of the entire library is acceptable in this case, so the current architecture does not need significant changes.

Assignee
Assign to
Time tracking