[Request]: Add more tips and explanations to make the game more accessible for non-programmers

[grubeninspekteur]

Request?

Especially in later levels the player is confronted with terms and concepts that may be difficult to grasp if they don't have a programming or computer science background. For example, the manual entry "Turing complete" mentions functions and recursion. It is never explained that "XOR" stands for "exclusive or" or "NAND" for "not and". The first assembly challenges involving the robot could benefit from an intermediate level teaching the concept of looping using conditional jumping, and also explain the label functionality in OVERTURE. An example task would be to use the input value to determine how often to output 5. Furthermore, later levels like multiplication, unsigned less or sorting dishes could use one or two optional hints.

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[MR-Spagetty]

I am encountering this with both symphony counter and comparison flags and there doesnt appear to be anything obviously related in the debug log (full output below)

Godot Engine v3.4.2.stable.custom_build - https://godotengine.org
OpenGL ES 3.0 Renderer: AMD Radeon RX 7900 XTX
OpenGL ES Batching: ON
 
Turing Complete 2.0.16 Alpha on Windows
ERROR: Condition "_first != nullptr" is true.
   at: SelfList<class GDScriptFunction>::List::~List (.\core/self_list.h:108) - Condition "_first != nullptr" is true.
ERROR: Condition "_first != nullptr" is true.
   at: SelfList<class GDScript>::List::~List (.\core/self_list.h:108) - Condition "_first != nullptr" is true.
ERROR: Condition "_first != nullptr" is true.
   at: SelfList<class DynamicFont>::List::~List (.\core/self_list.h:108) - Condition "_first != nullptr" is true.
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
   at: ObjectDB::cleanup (core\object.cpp:2064) - ObjectDB instances leaked at exit (run with --verbose for details).
ERROR: Resources still in use at exit (run with --verbose for details).
   at: ResourceCache::clear (core\resource.cpp:417) - Resources still in use at exit (run with --verbose for details).
ERROR: There are still MemoryPool allocs in use at exit!
   at: MemoryPool::cleanup (core\pool_vector.cpp:63) - Condition "allocs_used > 0" is true.

the workaround of copy pasting from a space/level such as sandbox does work though

[Gelthir]

A better, more permanent, workaround is: Pasting the following line into levels.txt (which is found in your save folder, check the location in Options):

symphony_register_1,true,10000,10000,0,Default

(This marks the deleted level symphony_register_1 as done that used to unlock this feature.)

[MR-Spagetty]

just checked the component factory and it seems to also not have the bit width tool (atleast for me)

[MR-Spagetty]

A better, more permanent, workaround is: Pasting the following line into levels.txt (which is found in your save folder, check the location in Options):

symphony_register_1,true,10000,10000,0,Default

(This marks the deleted level symphony_register_1 as done that used to unlock this feature.)

thx, does the instruction decoder level maybe not depend on that one? as i was able to use the bit width tool just fine in that level but not the symphony counter or comparison flags

[Gelthir]

I'd be surprised if that level were special cased. The static indexers used in the decoder level might not rely the the level unlock. But I'm speculating.