Using the console can have mixed results because of the way the renpy interpreter works and passes things to the python execution engine. The renpy interpreter either translates a renpy comand into python then passes it to the python engine or it just passes the python comand to the python engine. The catch here is if you pause the game because of how renpy predicatively executes code, what the python enigne has for a variable value and what the renpy interpreter has are two different things till renpy merges them. Which is why when you check the console for a variable and its not yet set, whats probably happend is when the game paused the interpreter and engine are not synced and therefore you get results that don’t match.
I learned this the hard way you can see an example i posted here: Can renpys screen object action SetVariable() change a variables that are not used in the screen the action it is called in.
The console is really a debugging tool. Your trying to use it to cheat but have no understanding of what you or it is actually doing, that’s why its disabled by default for all deployment builds.