It seems that at the current state it is necessary to protect sending stats/ending game from multiple execution,
as that can happen if you e.g. fail a mission more than once in the same tick (e.g. destroying two essential crates at the same time)
Otherwise you can get a blank / stuck frontend (e.g. when using deagle to shoot the two last crates at the same time)!
the best approach might be to never call the function that sends stats and ends game from any event handler directly, but instead have a flag 'isFailed' that is set to true when any of the possible fails happen and to check that flag every tick to send stats and end game if true
{-# LANGUAGE OverloadedStrings #-}
module HWProtoChecker where
import Data.Maybe
import Control.Monad.Reader
--------------------------------------
import CoreTypes
import Actions
import HandlerUtils
handleCmd_checker :: CmdHandler
handleCmd_checker ["READY"] = return [ModifyClient $ \c -> c{isReady = True}, CheckRecord]
handleCmd_checker ["CHECKED", "FAIL", msg] = do
isChecking <- liftM (isJust . checkInfo) thisClient
if not isChecking then
return []
else
return [CheckFailed msg, ModifyClient $ \c -> c{checkInfo = Nothing}]
handleCmd_checker ("CHECKED" : "OK" : info) = do
isChecking <- liftM (isJust . checkInfo) thisClient
if not isChecking then
return []
else
return [CheckSuccess info, ModifyClient $ \c -> c{checkInfo = Nothing}]
handleCmd_checker _ = return [ProtocolError "Unknown command"]