Aka, use the in game command console and type:
in BG2/BGT:
CLUAConsole:GetGlobal("C#LCNOOB_Quest","GLOBAL")
in EE-games v1.3 and beyond:
C:GetGlobal("C#LCNOOB_Quest","GLOBAL")
...
Sorry, I cannot use the CLUAConsole since I have no baldur.ini and I don't know how to modify Baldur.lua in order to activate the console so I got the variable in my previous reply from EEKeeper.
(I have added the line "SetPrivateProfileString('Program Options','Debug Mode','1')" (without quotes) to the end of my baldur.lua file but ctrl+space does nothing, not even in a new started game) (Correction: it does what the space normally does i.e. pause/unpause)
You open .lua in the same way as .ini, with your text editor (I'd advice you to use Notepad++ as a default text reader instead of Windows' one)
Find the bunch of lines starting with "Program Options", and add one line:
SetPrivateProfileString('Program Options','Debug Mode','1')
(similar to original Baldur.ini in Baldur's Gate II: Shadows of Amn)
But be careful to check it after every change of baldur.lua (when you run the game for the first time, or when you set/change the game/visual/sound/subtitles settings), because the game reloads Baldur.lua file, even if you have saved the changes before. And it forces you to repeat the action (adding the line) again. I'm not sure why is this happening. So do it again if need, and check it out, just in case.
Like in the original BG2, you use Ctrl+Space
In BGEE you use C: instead of CLUAConsole:
for example:
C:ExploreArea()
instead of
CLUAConsole:ExploreArea()
Sorry for an offtop, I hope I'll get away with this...