-
Notifications
You must be signed in to change notification settings - Fork 24
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
Attack/Defence: CTF Problems #53 #76
base: master
Are you sure you want to change the base?
Conversation
@@ -39,7 +39,8 @@ class Problem(BaseProblem): | |||
ma = fields.IntField(default=500) | |||
visible = fields.BooleanField(default=True) | |||
tags = fields.SmallIntField(default=1) # by default misc, 16 tag limit | |||
|
|||
difficulty_level = fields.SmallIntField(default=1) | |||
problem_type = fields.TextField(default="jeopardy") #Can use enum too |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use SmallIntField
|
||
class AttackDefProblem(Model): | ||
id = fields.IntField(pk=True) | ||
team: fields.ForeignKeyRelation[Team] = fields.ForeignKeyField( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
attack_def_team: fields.ForeignKeyRelation[AttackDefTeam] = fields.ForeignKeyField(
"models.AttackDefTeam", related_name="assigned_attack_def_problem"
)
Do different endpoints for the different modes. One route should always only do one thing so move to a separate router for round 2. The round 2 router should be called FFA and the round 1 router should be jeopardy. These should be the prefixes for the two modes |
feat: Add AttackDefProblem model and update CTF routes
(Note: Currently importing the team model directly since the dedicated AttackDefTeam model is pending)
The original requirements mention modifying all existing CTF routes to reject attack/def submissions and creating new routes for attack/def CTFs that incorporate powerup logic. Could you please clarify whether:
Additional guidance on how the powerup logic should affect the route behavior would be appreciated.
Closes #53