p:\a3\functions_f\debug\fn_isdebugconsoleallowed.sqf has only these checks for SP but lacks the enableDebugConsole value check
```
// == SP MODE ==
if (!isMultiplayer) exitWith
{
allDisplays find findDisplay 313 in [0, 1] // 3DEN preview
||
{allDisplays find findDisplay 26 in [0, 1]} // 2DEN
||
{(configFile >> "enableDebugConsole") call {isArray _this || {isNumber _this && {getNumber _this >= 1}}}} // allowed by mod
};
```
The mission specific parameter (enableDebugConsole in desc.ext) not taken into account for SP. The check is done below but just for MP.
Wiki mentions also use for SP: https://community.bistudio.com/wiki/Arma_3:_Debug_Console#Configuration
T128695#1728561 claims it was done "by design". This doesnt make any sense.
As result you are forced to do testing via Eden, or need a config mod to enable the console globally.
---
Prior to a refactor the console was also available in SP:
```
_allowDebugConsole = if (isnil "_allowDebugConsole") then {false} else {_allowDebugConsole};
_enableDebugConsole = ["DebugConsole",getMissionConfigValue ["enableDebugConsole",0]] call bis_fnc_getParamValue;
if (
//--- Editor
(((alldisplays find (finddisplay 26) in [0,1]) || (alldisplays find (finddisplay 313) in [0,1])) && !ismultiplayer)
||
//--- In mission with enableDebugConsole entry set to 1 (only for host/admin)
{(_enableDebugConsole == 1 && (isserver || serverCommandAvailable "#shutdown"))}
||
//--- In mission with enableDebugConsole entry set to 2 (for everyone)
{(_enableDebugConsole == 2)}
||
//--- Allowed by script
{_allowDebugConsole}
//||
//--- Dev version
//cheatsEnabled
) then {
```
{F3502892}
{F3502893}