Skip to content

Instantly share code, notes, and snippets.

@Fusselwurm
Last active September 21, 2021 19:30
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Fusselwurm/c07a7befb95a69634107443227fcea46 to your computer and use it in GitHub Desktop.
Save Fusselwurm/c07a7befb95a69634107443227fcea46 to your computer and use it in GitHub Desktop.
Slotting Bounty System (SBS)

Slotting Bounty System (SBS)

Motivation

Some roles tend to stay open for a long time, some roles are taken the instant the slotting goes online. We want some system that equals the playing field and

  • incentivizes players to cover all roles
  • prevents slot sniping
  • gives everyone a chance to play their preferred role

Solution: slots are auctioned

Use our current slotting tool, with these added features:

  • Every user is associated their own persistent numerical slotting score ("score")
  • Upon slotting, participants have to enter a numerical bounty ("bounty"), defaulting to 100
    • a bounty cannot be higher than 100 (default value)
      • this is so people cannot get rich on slots that no-one else wants
    • a bounty must be integer
      • this is so people dont get into tedious floating point battles
  • Participants can kick other participants off their respective slot and take it for themselves by entering a lower bounty than the one the previous occupant entered
    • Participants are allowed to enter a negative bounty as long as their score is higher than zero
    • When a participant kicks another from their slot, their score is reduced by:
      • longer than a week before the event: 0 point
      • 6…7 days before the event: 1 point
      • 5…6 days before the event: 2 points
      • 4…5 days before the event: 4 points
      • 3…4 days before the event: 8 points
      • 2…3 days before the event: 16 points
      • 1…2 days before the event: 32 points
      • 0…1 days before the event: impossible to kick other players off their slots
    • the prompt for the bounty contains a list of previously slotted players, the timestamp & their selected bounties
  • After an event, a moderator gets a "Confirm slottings" button which opens a pop-up that lists all the slots and the players
    • for every slot-player combo, there's
      • a button "did not show up"
      • if that button gets clicked, a dropdown is added with all other slotted players available for selection as stand-in
      • at the bottom, there is a "save" button
  • Once confirmed, every player's slot bounty gets added to their score but ONLY if they actually played the slot
    • If a player did not show up their score is reduced by 100 points
    • If a player slotted somewhere else to replace a no-show, 100 points get added to their score
  • There is no provision for players that were not slotted but showed-up spontaneously!
@nomisum
Copy link

nomisum commented Jul 15, 2021

we would need a way to handle players

  • not turning up
  • jumping in instead
    so, unlocking/assigning after the event, maybe limited to moderators.

@Fusselwurm
Copy link
Author

we would need a way to handle players

  • not turning up

  • jumping in instead

so, unlocking/assigning after the event, maybe limited to moderators.

Simple solution:

  • for people who did not use their slotted slot in-game, we do not pay out whatever bounty their slotting had
  • for no-shows, we set a penalty -100 points
  • for spontaneous stand-ins, we give them 100 points
    • if their original slotting had a bounty of 100, nothing changes for them – but thats ok, their original slot wasnt super important to them (or anyone else) anyway
    • if their original slotting had a low bounty – that is they loved their slot and wanted to have it – they effectively get a bonus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment