External/card-drop

Fork 0

AS a developer, I want there to be the concept of effects created in the codebase #378

New issue

Open

opened 2024-10-11 19:01:03 +01:00 by Vylpes · 1 comment

Vylpes commented

2024-10-11 19:01:03 +01:00

Owner

Epic: #377
Story Points: 5

SO THAT users are able to have different status effects given to them in the future

Acceptance Criteria

GIVEN I am a developer
WHEN I want to add an effect
THEN there should be the ability within the codebase to add one

GIVEN I am a developer
WHEN I check what statuses are created
THEN there should be the "unobtained chance up" effect

Subtasks

Plan implementation
Implement
Plan tests
Add tests

Notes

No notes

Epic: #377 Story Points: 5 --- SO THAT users are able to have different status effects given to them in the future ## Acceptance Criteria GIVEN I am a developer WHEN I want to add an effect THEN there should be the ability within the codebase to add one GIVEN I am a developer WHEN I check what statuses are created THEN there should be the "unobtained chance up" effect ## Subtasks - [x] Plan implementation - [x] Implement - [x] Plan tests - [x] Add tests ## Notes *No notes*

Vylpes added the

labels 2024-10-11 19:01:08 +01:00

Vylpes added this to the 0.9.0 milestone 2024-10-11 19:01:13 +01:00

Vylpes referenced this issue

2024-10-11 19:03:22 +01:00

AS a user, I want to be able to list all the effects I have in my inventory #379

Vylpes referenced this issue

2024-10-11 19:05:19 +01:00

AS a user, I want to be able to use an effect I have in my inventory #380

Vylpes referenced this issue

2024-10-11 19:06:56 +01:00

AS a user, I want to be able to buy more effects #381

Vylpes referenced this issue

2024-10-11 19:07:08 +01:00

Consumables #377

Vylpes added this to the 0.9 Sprint 6 project 2024-10-11 19:08:17 +01:00

Vylpes changed title from ~~Create concept of effects in the database~~ to AS a developer, I want there to be the concept of effects created in the codebase

2024-10-13 15:27:04 +01:00

Vylpes removed the

needs criteria

label 2024-10-13 15:28:30 +01:00

Vylpes removed the

needs estimate

label 2024-10-17 18:45:18 +01:00

Vylpes self-assigned this 2024-10-17 18:45:24 +01:00

Vylpes started working 2024-10-19 11:34:17 +01:00

Vylpes stopped working 2024-10-19 11:59:20 +01:00

25 minutes 3 seconds

Vylpes modified the project from 0.9 Sprint 6 to 0.9 Sprint 7

2024-10-20 17:12:58 +01:00

Vylpes started working 2024-10-25 16:58:31 +01:00

Vylpes commented

2024-10-25 17:18:33 +01:00

Author

Owner

Effect is attached to a user and has an expiry date
Implementation will be put into the code
- This ticket is just to let the effects be stored
- How the effect will affect the user will be checked in other tickets
Unused effects can be stored as an additional column of the entity

UserEffects entity

Name	Type	Nullable	Default	Notes
Id	UUID	No		Primary Key
Name	string	No
UserId	string	No		Discord User ID
Unused	int	No	0
WhenExpires	Date	Yes	null	null or in the past means inactive

Subtasks

Create UserEffect entity
Create EffectHelper class
- AddEffect(userid: string, name: string, quantity: number = 1)
- UseEffect(userid: string, name: string): bool
- HasEffect(userid: string): bool

- Effect is attached to a user and has an expiry date - Implementation will be put into the code - This ticket is just to let the effects be stored - How the effect will affect the user will be checked in other tickets - Unused effects can be stored as an additional column of the entity ## UserEffects entity | Name | Type | Nullable | Default | Notes | | --- | --- | --- | --- | --- | | Id | UUID | No | | Primary Key | | Name | string | No | | | | UserId | string | No | | Discord User ID | | Unused | int | No | 0 | | | WhenExpires | Date | Yes | *null* | *null* or in the past means inactive | ## Subtasks - [x] Create UserEffect entity - [x] Create EffectHelper class - [x] AddEffect(userid: string, name: string, quantity: number = 1) - [x] UseEffect(userid: string, name: string): bool - [x] HasEffect(userid: string): bool

Vylpes stopped working 2024-10-25 17:23:08 +01:00

24 minutes 37 seconds

Vylpes started working 2024-10-26 17:48:17 +01:00

Vylpes stopped working 2024-10-26 18:23:19 +01:00

35 minutes 2 seconds

Vylpes started working 2024-10-26 21:22:26 +01:00

Vylpes stopped working 2024-10-26 21:48:47 +01:00

26 minutes 21 seconds

Vylpes started working 2024-10-29 11:40:34 +00:00

Vylpes stopped working 2024-10-29 12:01:55 +00:00

21 minutes 21 seconds

Vylpes started working 2024-10-30 10:05:45 +00:00