Have the server check a folder instead of a file for challenges. Each file represents a single challenge (with a name). When the user types /challenges list show a list of challenge names (not file names). The user can load invidual challenges with /challenges load <name>. If another challenge was loaded previously, this challenge will be unloaded first.
The server now stores the information about the last played/currently being played challenge when the server stops. That way users can just do /resume after the server stopped/restarted during an active challenge without having to specify which challenge to play again. This implicitly forces the server to always load the current challenge (if one exists) on server start.
Have the server check a folder instead of a file for challenges. Each file represents a single challenge (with a name). When the user types
/challenges listshow a list of challenge names (not file names). The user can load invidual challenges with/challenges load <name>. If another challenge was loaded previously, this challenge will be unloaded first.The server now stores the information about the last played/currently being played challenge when the server stops. That way users can just do
/resumeafter the server stopped/restarted during an active challenge without having to specify which challenge to play again. This implicitly forces the server to always load the current challenge (if one exists) on server start.