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.

Sign up for GitHub

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

Jump to bottom

Controller, Checker: Check behavior regarding GameControl timing #36

Open
F30 opened this issue Jun 15, 2018 · 0 comments
Open

Controller, Checker: Check behavior regarding GameControl timing #36

F30 opened this issue Jun 15, 2018 · 0 comments
Assignees
@rudis @F30
Labels
improvement Not a critical bug, but also not a visible feature

Comments

@F30
Copy link
Member

F30 commented Jun 15, 2018

I'm not sure if data from the "GameControl", especially regarding timing, is currently processed by all components in an optimal way. Questions include:

  • What happens when the Controller does start delayed, such as at FAUST CTF 2018?
  • What happens when there is a conflict between the current tick in the database and the current one according to start time and tick duration?
  • Can we prevent all services from being "Recovering" at the start of a CTF, which iirc is what happened at FAUST CTF 2018?
  • Is the configurable tick duration actually used?
  • Are extensions of a CTF's duration supported?
@F30 F30 added the improvement Not a critical bug, but also not a visible feature label Jun 15, 2018
@F30 F30 assigned rudis and F30 Feb 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rudis rudis

@F30 F30

Labels
improvement Not a critical bug, but also not a visible feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rudis @F30