-
Notifications
You must be signed in to change notification settings - Fork 132
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
Scoreboard / Trainer Dashboard #27
Comments
@J12934 I see the last activity on this issue was in 2020. Any progress update? Any way I can help contribute to the project around completing this issue? |
Hey @artis3n thanks for showing you interest in this feature 👍 I made a few attempts on implementing this last year, but never found a way to display this "naturally" in the MultiJuicer UI in a way which seemed fitting and then always ran out of time... Contributions are always very much appreciated, there is a rather old branch which has the basic scoring implemented with mostly the UI missing: https://github.com/iteratec/multi-juicer/tree/main This would be a good starting point. Also a even older branch in similar state of incompletness: https://github.com/iteratec/multi-juicer/tree/score-board |
Just to clarify - that first "old branch" link is |
@artis3n yes... |
Worked on this a bit today. My plan for this moving forward is:
|
MultiJuicer v5.0.0 is out now with the new score-board functionality 🎉 |
To give a overview on which team already solved particular challenges, MultiJuicer(JuicyCTF 😉) should provide a scoreboard.
The scoreboard is meant for less competitive events and should be focused on providing a helpful overview for the trainer(s) and a fun overview for the players.
This scoreboard should be able to display the following things:
XSS
) and how many users have solved them.It might also be nice to add an option to use a more competitive mode. Competition can be fun even during training. For that a ranking could be added with the following pages:
The text was updated successfully, but these errors were encountered: