[UI] Inconsistent Naming for "Set Collision" Nodes in Logic Node Search Menu (v0.44)

[Roiin]

UPBGE Version:
UPBGE 0.44.0 (based on Blender 4.4.3)

Description of the Bug:

In the Logic Node Editor, when adding a new node, the action nodes Set Collision Mask and Set Collision Group are incorrectly named as "Get Collision Mask" and "Get Collision Group" in the search menu.

This creates confusion as it makes it appear there are two "Get" nodes for each function. The placed node has the correct title, but the search/add menu is misleading.

(For context, this was discovered while creating a full set of documentation for all logic nodes, which I've shared with the community here: https://github.com/Roiin/Roiin.github.io/tree/main/Atomic-Logic-Node-Editor

Steps to Reproduce:

Open a new UPBGE 0.44 project.
Go to the Logic Node Editor workspace.
Press Shift + A to open the "Add Node" search menu.
Type "Get Collision Mask" into the search bar.
Observe: Two nodes named "Get Collision Mask" appear. One is the getter, the other is the setter.

Expected Behavior:

The search menu should accurately reflect the node's function, naming them "Set Collision Mask" and "Set Collision Group" to distinguish them from the getters.

Evidence:

[IzaZed]

This has been fixed in 5.0 releases, thank you for reporting!
Would there be any interest in having your documentation integrated into the upbge manual as well?

[Roiin]

This has been fixed in 5.0 releases, thank you for reporting! Would there be any interest in having your documentation integrated into the upbge manual as well?

Hello @IzaZed,

Thank you so much for the update! I'm thrilled to hear the naming inconsistency has been fixed in the 5.0 releases. It's a small change that will make a big difference for new users, and I'm glad my report was helpful.

Regarding your question about integrating my documentation: Yes, absolutely. I would be honored to contribute and help integrate it into the official UPBGE manual.

This documentation project actually grew out of a very practical need. As an educator and a creator, I am developing a systemic narrative game prototype, Khunires, entirely within UPBGE. My primary goal was to create a clear, comprehensive resource not just for myself, but for my students and other world-builders who could benefit from a deep dive into the Logic Node system.

My core philosophy for the documentation has been to focus on practical, real-world examples that teach not just what a single node does, but how to architect complete, functional systems with them. I believe this approach is key to empowering newcomers, helping them learn to debug their own work and, eventually, design their own novel solutions.

For instance, when explaining something like movement, I've been creating clean, titled graphs that solve a complete problem from start to finish. Here is an example of that style:

I am very excited about this possibility and ready to help in any way I can. Please let me know what the next steps would be. Is there a specific format (like Markdown) or a contribution guide I should follow? I'm happy to coordinate with whomever is leading the documentation effort.

Thank you again for this incredible opportunity!

Best regards,
Arash (Roiin)