Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Vehicle Data Structure #16

Open
Shinedown204 opened this issue Jun 9, 2024 · 0 comments
Open

New Vehicle Data Structure #16

Shinedown204 opened this issue Jun 9, 2024 · 0 comments
Assignees
Labels
feat: breaking-changes This might break other parts of the code. priority: high After critical issues are fixed, these should be dealt with before any further issues. semver: major This will cause a major bump in the version X.0.0 status: discussion-needed This should be discussed first before proceeding. type: feature New feature, concept idea or suggestion.

Comments

@Shinedown204
Copy link

Data Structure

  • Name of Vehicle: The vehicle's name.
  • Image of Vehicle: Image ID or a Roblox model camera view as suggested by Newton.
  • Price: The vehicle's purchase price.
  • Sell Price: The resale value, distinct from the purchase price.
  • Vehicle Type: Category of the vehicle (e.g., Sedan, Luxury).
  • Default Rim Decal: Decal applied to all rim parts by default.
  • Default Paint Color: Default color of the vehicle in RGB format.
  • Vehicle Rarity: Derived from the number of owners; requires tracking the number of users owning each vehicle.
  • Date Added: Date the vehicle was added to the game, used to mark new vehicles in the dealership. The system automatically updates this, displaying new vehicles for a set duration (e.g., 1 month).
  • Speedometer List: List of available speedometers for the vehicle, allowing users to select from the options.
  • Daily Reward Restricted: Indicates if the vehicle is restricted to being unlocked only through the daily reward system.
@Shinedown204 Shinedown204 converted this from a draft issue Jun 9, 2024
@Shinedown204 Shinedown204 added type: feature New feature, concept idea or suggestion. priority: high After critical issues are fixed, these should be dealt with before any further issues. status: discussion-needed This should be discussed first before proceeding. labels Jun 9, 2024
@Shinedown204 Shinedown204 moved this from Backlog to Ready for Dev in Tang County V4 Jun 9, 2024
@Shinedown204 Shinedown204 moved this from Ready for Dev to In Review in Tang County V4 Jun 9, 2024
@Shinedown204 Shinedown204 moved this from In Review to Backlog in Tang County V4 Jun 9, 2024
@Shinedown204 Shinedown204 moved this from Backlog to Ready for Dev in Tang County V4 Jun 9, 2024
@Shinedown204 Shinedown204 moved this from Ready for Dev to Backlog in Tang County V4 Jun 9, 2024
@Shinedown204 Shinedown204 self-assigned this Jun 9, 2024
@iceeburr iceeburr self-assigned this Jun 9, 2024
@iceeburr iceeburr added semver: major This will cause a major bump in the version X.0.0 feat: breaking-changes This might break other parts of the code. labels Jun 9, 2024
@iceeburr iceeburr added this to the Tang County V4 milestone Jun 9, 2024
@Shinedown204 Shinedown204 moved this from Backlog to Ready for Dev in Tang County V4 Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat: breaking-changes This might break other parts of the code. priority: high After critical issues are fixed, these should be dealt with before any further issues. semver: major This will cause a major bump in the version X.0.0 status: discussion-needed This should be discussed first before proceeding. type: feature New feature, concept idea or suggestion.
Projects
Status: Ready for Dev
Development

No branches or pull requests

3 participants