There was security flaw in debug console that allowed to launch it without any permission with relatively short code. This has now been removed. Leaving this flaw would have been far worse for everyone running public servers than a little inconvenience for a few people that exploited this flaw for own benefit.

A custom admin panel would probably be better solution in the long run.

If BI ever decided to explore a method for "multiple admins having access to debug", a compromise for security could be done via some method similar to the following:

enableDebugConsole = 3; // available to all admins identified in server.cfg admins[]

This would essentially allow server owners to either allow only logged in admins to access debug and many admins use the #login command(eDC=1), or to allow access to the debug console for all whitelisted admins who may also login with the #login command(eDC=3).

A thought, at any rate.

Gnashes has a good idea please fix this or implement a workaround for us so we are able to have more than one admin with the access to the console. Please do not ignore this BI thank you.

In T124835#1605315, @Gnashes wrote:

If BI ever decided to explore a method for "multiple admins having access to debug", a compromise for security could be done via some method similar to the following:

enableDebugConsole = 4; // available to all admins identified in server.cfg admins[]

This would essentially allow server owners to either allow only logged in admins to access debug and many admins use the #login command(eDC=1), or to allow access to the debug console for all whitelisted admins who may also login with the #login command(eDC=4).

A thought, at any rate.

+1

I think the idea suggested by @Gnashes would be a very good solution to this issue. This would allow for more than 1 admin to access the debug console at a time, and I doubt it would pose any security issues as well.

I agree that Gnashes solution would be best. I do not want to publicly release all my admin's UIDs by including them in description.ext which is downloaded by anyone joining our server.

Unfortunately Gnashes solution will require quite significant engine changes and cannot be done with just scripting and config.

@BIS_fnc_KK changing the console already required significant change, didn't it? Given how a big share of arma community is based on clan-oriented servers, it needs to be a server config. Removal of admin console is not very far from way of thinking that "removal of multiplayer would fix the hacking problem" ;)

Unless... KK do you know if the change was made engine side, or function side? Can it be reverted with a mod?

Looks scriptside to me:

<redacted for security reasons>
@BIS_fnc_KK you messed up https://feedback.bistudio.com/T125063

can we also review the ability to create a debug console with ctrlcreate

ctrlcreate ['rscdebugconsole',-1]

only seen it used for malicious purposes

In T124835#1609385, @dedmen wrote:

Looks scriptside to me:

<redacted for security reasons>
@BIS_fnc_KK you messed up https://feedback.bistudio.com/T125063

Not really.

@demicanadian No one removed debug console, you probably misunderstood the whole ticket.

@MDCCLXXVI I can create non-functional console the way you suggested

I know that logged in admin sees debug console. But people with admin addon (signed by server's admin, with built in UID check to only allow specific people to use it) no longer do.

In T124835#1610058, @demicanadian wrote:

I know that logged in admin sees debug console. But people with admin addon (signed by server's admin, with built in UID check to only allow specific people to use it) no longer do.

This will still be possible, sort of. Will go in more details a bit later on.

In 1.72 enableDebugConsole param could be defined in root of a mod. If no mission param is defined, this one will be used. Default is 0

@BIS_fnc_KK If no mission param is defined Nope again. https://feedback.bistudio.com/T125778

Also if you have to use a signed PBO anyway. You can just overwrite the Console UI config and remove the isDebugConsoleAllowed check.
Or overwrite isDebugConsoleAllowed in CfgFunctions

This change caused an additional problem. I can no longer see debug console while in editor through editor menu options Tools\Debug Console. enableDebugConsole not existing in description.ext so its not over riding there... no mods loaded. screen shots -
http://i.imgur.com/1ySXEP5.jpg
http://i.imgur.com/1owrYOP.jpg
This behavior of only being able to see the Cancel button is what it looks like in mission on dedi if not loged as admin and initiated by admin tool mod since you removed access for non loged in admins. It has to be related

In T124835#1626942, @Jigsor wrote:

This change caused an additional problem. I can no longer see debug console while in editor through editor menu options Tools\Debug Console. enableDebugConsole not existing in description.ext so its not over riding there... no mods loaded. screen shots -
http://i.imgur.com/1ySXEP5.jpg
http://i.imgur.com/1owrYOP.jpg
This behavior of only being able to see the Cancel button is what it looks like in mission on dedi if not loged as admin and initiated by admin tool mod since you removed access for non loged in admins. It has to be related

I cannot repro this. Editor console is available in SP regardless of the description or editor attribute so there is no reason it would do that unless somehow something else is modified or horribly broken. BTW it looks like you are running some mod even though you say you are not, that icon next to PC in the bottom right corner of the editor should be greyed out if no unofficial mods are launched.

In T124835#1624052, @dedmen wrote:

Nope again

That is being looked at, thanks

OK, so debug console is working in sp editor but, why is the console ui incomplete in mp editor. It used to work in mp editor.
Why does mp editor indicate running mods when in the same instance without restart sp editor indicates no mods (icon grayed out).
http://i.imgur.com/4wEXTu5.jpg
http://i.imgur.com/9QTMWzI.jpg

BTW -filePatching is not enabled if that makes any difference.

Further to clarify which editor I am talking about. SP editor/main menu editor button. MP editor - from main menu click host server button on top then host server button in the middle of screen then select existing editable mission then 3D editor button or select <<New - 3D Editor>> from mission selection list.

I was able to reproduce this, thanks.

Recent changes in dev branch (1.73.142299) don't allow use addon version with this line in RPT:

ArmA3\adds\enable_debug_console\config.cpp.enableDebugConsole: Cannot update non array from array

It's because of useless enableDebugConsole = 0; in config. By default getNumber returns 0 even without it.

In T124835#1631156, @Dystopian wrote:

Recent changes in dev branch (1.73.142299) don't allow use addon version with this line in RPT:

ArmA3\adds\enable_debug_console\config.cpp.enableDebugConsole: Cannot update non array from array

It's because of useless enableDebugConsole = 0; in config. By default getNumber returns 0 even without it.

This seems to be indeed some recent change in exe. Thanks for reporting this

Also if I managed to set enableDebugConsole to array, I get

Warning Message: 'enableDebugConsole/' is not a value

on screen and in RPT on each console opening because of getNumber call on array value,

In T124835#1631450, @Dystopian wrote:

Also if I managed to set enableDebugConsole to array, I get

Warning Message: 'enableDebugConsole/' is not a value

on screen and in RPT on each console opening because of getNumber call on array value,

What do you mean by "managed". Are we still talking setting it in mod or in mission? Could you give repro?

mod one. I use 2 addons: one to delete value and one to set array. Repro: try to use getNumber on config with array value.

In T124835#1631455, @Dystopian wrote:

mod one. I use 2 addons: one to delete value and one to set array. Repro: try to use getNumber on config with array value.

Must have been another change that happened recenlty. Thanks for reporting this, I managed to repro.

Please check today's dev. All of the reported issues here should be fixed.