Belbo 462 Posted August 22, 2017 Supposedly since 1.71 you should be able to create a mod with enableDebugConsole: https://community.bistudio.com/wiki/Mission_Editor:_Debug_Console_(Arma_3)#Mod_support Tried it, didn't work. Is this actually implemented or is there something else to think about than just putting the statement blandly in the config.cpp? Whitelisting multiple users via description.ext seems not to be implemented as well. Share this post Link to post Share on other sites
rebel12340 46 Posted August 24, 2017 This was supposedly added when Malden came out. Have you created a ticket on the feedback tracker about it? You could also try asking on the development branch sub-forum. Share this post Link to post Share on other sites
pierremgi 4850 Posted September 1, 2017 Probably something wrong with the order precedence. If you worked with debug console allowed in 3den then tried to use global/mod param, this could give the precedence to 3den, so stay as is. Share this post Link to post Share on other sites
Belbo 462 Posted September 1, 2017 I don't know... I haven't set anything with the 3den params and removed almost all from the mission.sqm. I'm working only with description.ext and possibly a config.cpp. Setting enableDebugConsole to 0 in description.ext and then not be able to overwrite it with enableDebugConsole=2 in a config.cpp doesn't really make any sense - that's what this is for after all. enableDebugConsole[] = {"###UID###"}; in the description.ext didn't work either. Share this post Link to post Share on other sites
DÄZ 56 Posted December 18, 2017 hi, i am also interested ... if anyone find the solution, thanks Share this post Link to post Share on other sites
Tim.M 0 Posted September 28, 2021 Any update on this? Share this post Link to post Share on other sites
pierremgi 4850 Posted October 3, 2021 What for? You can use it in description.ext for your own scenarii. From a mod, stay aware of battleEye. Share this post Link to post Share on other sites
Tim.M 0 Posted October 20, 2021 I was refering to Belbo's last post. According to the wiki you can overwrite enableDebugConsole using a mod if it has allready been defined in description.ext. I was able to define it with a mod provided it wasnt allready in description.ext but i couldnt overwrite or remove it if it was. Quote To whitelist (multiple) users with a mod, if enableDebugConsole has already been defined, use the delete keyword: delete enableDebugConsole; enableDebugConsole[] = {"81273982178973213"}; https://community.bistudio.com/wiki/Arma_3:_Debug_Console#Mod_support Share this post Link to post Share on other sites
pierremgi 4850 Posted October 20, 2021 Don't forget the lin es about batteEye. If I'm right, no matter a server is yours. If battleEye detects a potential cheat, you can be banned. (to be confirmed) Share this post Link to post Share on other sites