velvet-make System Requirements Document

Introduction

This document outlines the system requirements for the project "velvet-make," a ROBLOX game titled "Bit:Zero." The game is inspired by BitLife and Re;Zero, focusing on life simulation with fantasy elements. The game will feature a variety of mechanics including family systems, reroll systems, relationship dynamics, crime involvement, generational gameplay, and more, all within a UI-centric design.

System Overview

Product Interpretation and Delivery Boundary

• Domain Descriptor: Life simulation with fantasy elements.

  • Source Evidence: User request for a game combining life simulation mechanics with fantasy elements like magic and spirit contracts.
  • Confidence: 0.9

• What is Being Built: A standalone ROBLOX game with custom UI elements, focusing on life simulation and fantasy elements.

• Excluded Conventional Assumptions:

  • Conventional e-commerce features
  • Standard multiplayer mechanics

• First-Party Custom Pages:

  • Bit:Zero Game UI: A UI-based game experience.
  • Authentication: A combined authentication surface for account sign-up, login, and session entry.

• Access: Application-owned identity is required for persistent player identity.

• Behavior Contracts:

  • Family and Reroll Mechanics: Player initiates family creation or reroll action.
  • Magic and Authority Mechanics: Player engages in magic or authority-related action.
  • Relationship and Crime Mechanics: Player initiates relationship or crime action.
  • Playable Baby After Death: Player character dies, leading to a new playable baby character.
  • Authority Spawn Chance: Player character is created with a chance to spawn with authority.
  • Witch Visit Events: Random event where a witch visits the player.
  • World Updates: Scheduled or triggered world update events.
  • Training and Relics/Items Search: Player selects train or search action.
  • Isekai Character Start: First character creation after wipe.
  • Spirit Contracts and Abilities: Player initiates contract or interacts with spirit.
  • Character Customization on First Wipe: Player customizes character appearance.
  • Jobs and Asset Acquisition: Player selects job or asset acquisition action.
  • Bless or Attack by Witches: Witch visit event occurs.
  • Witch Can Kill Someone Close: Witch attack event targets someone close.
  • Have a Baby: Player initiates have baby action.
  • Train: Player selects train action.
  • Look for Relics and Items: Player selects search for relics/items action.
  • Gain Jobs That Make Sense: Player selects job acquisition action.
  • Buy Houses and Assets Like BitLife: Player selects asset purchase action.

Functional Requirements as Story Points

• As a Player, I should be able to create a family and use a reroll system to change family attributes.
• As a Player, I should be able to engage in magic activities and have a chance to gain authority.
• As a Player, I should be able to form relationships and commit crimes, affecting my status and history.
• As a Player, I should be able to continue playing as a baby character after my character dies.
• As a Player, I should have a chance to spawn with authority when creating a new character.
• As a Player, I should experience random witch visits that can bless or attack me.
• As a System, I should update the world state based on scheduled or triggered events.
• As a Player, I should be able to train and search for relics or items to improve my stats or inventory.
• As a Player, I should start as an isekai character after the first wipe.
• As a Player, I should be able to form contracts with spirits and gain abilities based on relationship strength.
• As a Player, I should be able to customize my character's appearance after the first wipe.
• As a Player, I should be able to gain jobs and acquire assets like houses.
• As a Player, I should experience witch events that can bless or attack me or someone close.
• As a Player, I should be able to have a baby and continue the game as the baby after death.
• As a Player, I should be able to train to improve my stats.
• As a Player, I should be able to search for relics and items to add to my inventory.
• As a Player, I should be able to gain jobs that make sense within the game world.
• As a Player, I should be able to buy houses and assets similar to BitLife.

User Personas

• Player: The primary user interacting with the game, engaging in various life simulation and fantasy elements.

Core User Flows

1. Character Creation and Customization:

   • Player starts the game and creates a character.
   • Player customizes the character's appearance after the first wipe.

2. Family and Reroll Mechanics:

   • Player initiates family creation.
   • Player uses reroll options to change family attributes.

3. Magic and Authority Engagement:

   • Player engages in magic activities.
   • Player has a chance to gain authority.

4. Relationship and Crime Dynamics:

   • Player forms relationships and commits crimes.
   • Player's status and history are affected.

5. Generational Gameplay:

   • Player character dies.
   • Player continues as a baby character.

6. Witch Visit Events:

   • Random witch visit occurs.
   • Player experiences blessings or attacks.

7. World Updates:

   • System updates the world state based on events.

8. Training and Relics/Items Search:

   • Player selects training or search actions.
   • Player improves stats or finds items.

9. Jobs and Asset Acquisition:

   • Player selects job or asset acquisition actions.
   • Player gains jobs and acquires assets.

Visuals Colors and Theme

• Primary: #1E1E1E (Dark Gray)
• Primary Light: #2E2E2E (Lighter Dark Gray)
• Secondary: #FFD700 (Gold)
• Accent: #FF4500 (Orange Red)
• Highlight: #32CD32 (Lime Green)
• Background: #121212 (Very Dark Gray)
• Surface: #1E1E1E (Dark Gray)
• Text: #FFFFFF (White)
• Text Muted: #A9A9A9 (Dark Gray)
• Border: #333333 (Darker Gray)

Signature Design Concept

The game will feature a UI-centric design with a focus on life simulation and fantasy elements. The design will incorporate a clean and intuitive interface, allowing players to easily navigate through various game mechanics such as family creation, magic engagement, and relationship dynamics. The color palette will be dark-themed, reflecting the user's preference, with interactive elements highlighted using the accent color. The game will maintain a consistent visual hierarchy, ensuring clarity and accessibility for all players.

Interaction Model & Motion Direction

• Interaction Model: Animated
  • The game will feature moderate scroll-triggered reveals and hover transitions, providing a polished and engaging experience for players.
  • Internal pages will prioritize clarity and task completion, with minimal motion to maintain focus on gameplay mechanics.

Non-Functional Requirements

• Performance: The game must maintain smooth performance on ROBLOX, ensuring quick load times and responsive interactions.
• Accessibility: The game must be accessible to players with varying abilities, providing options for text size adjustments and color contrast settings.

Tech Stack

• Frontend: ROBLOX Lua scripting for game mechanics and UI.
• Backend: ROBLOX DataStore for persistent data management.

Assumptions and Constraints

• The game will be developed and hosted on the ROBLOX platform.
• Persistent player identity will be managed through ROBLOX's authentication system.
• The game will focus on single-player experiences with potential for future multiplayer expansions.

Glossary

• Isekai: A genre of fantasy where a character is transported to another world.
• Reroll: A mechanic allowing players to randomly change attributes or outcomes.
• Authority: A special status or power that can be gained by the player.
• Spirit Contracts: Agreements made with spirits to gain abilities or benefits.
• Wipe: A reset of game progress, allowing for new character creation.