Page MenuHomePhabricator

[Roblox] Wiki Speedrun Backrooms
Closed, ResolvedPublic

Description

As a Roblox user, I want to speedrun Wikipedia on Roblox, so that I can enjoy Wikipedia and speedrunning in a new, fun, and exciting way.

Acceptance Criteria

  1. A player on Roblox must be able to join a lobby to queue up for a round of Wiki Speedrun. It must be possible to support multiple lobbies simultaneously.
    • Is it much easier to make this for one player? How many players should be in a lobby? What should the lobby look like? How will players know when a game will begin? Can players create custom/invite-only lobbies? How will inviting work?
  2. Players in a round of Wiki Speedrun should start their game from the same location. Players will be given their prompt.
    • How will the prompt be delivered? Is the prompt sticky?
  3. From the starting block, players are given 4 "rooms" as options to move into. Each room represents a Wikipedia link that branches from the starting article.
    • How will players know what link a room represents before moving into it? How will players know what link the room they are currently in represents?
  4. A room is created for all relevant players when a player first travels into it. Rooms should connect on the broader grid map and be traversable. Conflicting room creation (ex. two players enter a room from different entrances) should be resolved by prioritizing the first player to enter the room.
  5. Each room must display a basic blurb that tells the player what the current room's link means and represents. This blurb must be taken from Wikipedia.
    • How can we ensure that players know this blurb is from Wikipedia, especially since only older audiences might recognize the Wikipedia formatting?
  6. There must be X types of obstacle rooms. The starting block has no obstacle. Each other room has a randomly-selected obstacle. Rooms must still connect and be traversable.
    • How many types of obstacles should we use? What should the obstacles be?
  7. All links are always age-appropriate (kid-friendly).
  8. There must always be a pathway to success (each prompt must be winnable).
  9. Players should see a timer that represents how long the player has taken. The timer stops when a player successfully travels to the target room. If a player leaves before the traveling to the target room, the timer is cleared.
    • Where does the timer live? What does the timer look like? Is there a time limit? If so, what should it be?
  10. Players should see a room count that represents how many rooms the player has traveled to. This should not be unique (with the logic that on a normal speedrun, if a player clicked to Link A, then Link B, and then to Link A, then that would still count as 3).
  11. Players should be able to see a leaderboard.
    • How often does the leaderboard update? From where can players see it (while playing, before games, after games)? Is the leaderboard based on a shared prompt?
  12. When a player travels to the target room, their game ends, and they are given a congratulations after being moved to a post-game/score screen.
    • What kind of congratulations would be fun? Do players know what place they are on the leaderboard? Are players prompted to replay, or is there a different action we want them to take instead?
  13. (Open) What kinds of rewards should we offer players to incentivize return users and further playing?
    • Can you see which "place" you got? Could you start together but then "teleport" to different maps and then be "reunited" on the last screen so we don't have map conflict?

Related Objects

Event Timeline

etz moved this task from Backlog to In Development on the Future-Audiences board.
DLin-WMF reopened this task as Open.
DLin-WMF closed this task as Resolved.
DLin-WMF reopened this task as In Progress.
DLin-WMF changed the task status from In Progress to Open.
DLin-WMF moved this task from In Development to PROD: Deployed / Done on the Future-Audiences board.
DLin-WMF moved this task from PROD: Deployed / Done to In Development on the Future-Audiences board.
etz moved this task from In Development to PROD: Deployed / Done on the Future-Audiences board.