It would be nice to have a “Pseudo” node that allows us to add execution pins in and out of it that can have a text spot to explain what that node will do for Blueprint Planning and placeholder nodes while the function/event is still being worked on or yet to be created. It will let the current code still execute as it will just pass through and be an editor only node so to speak. A lot like Pseudo hand coding it can give BP developers a way to plan out the code in a what that helps organize thoughts and doesn’t spam the console or print to screen.
Something along the lines of this mock up would be amazing!
Yeah but its just a work around vs an actual solution. I can see how making a function with a text input can sortta serve as that but a dedicated pseudo node could be a quick and easy way to get it out without creating a functions or macro.
Comments are too clunky imo. They take up a lot of space and have sections that are just empty taking up even more space. And in order to have executing lines go through them you have to add reroute nodes. It just feels like a work around vs and actual solution.
To be fair you’re talking about pseudocode which isn’t a thing that should last very long. I would even go so far as to say it’s not something that should get checked in. It’s a planning step for work that isn’t complete until all the pseudo becomes real code.
A secondary benefit of comments as pseudocode would be that you put the real logic into the comment space and just leave the comment. Since you wrote it first, it will describe intent not actions and you’ll have good comments in the graph for later.
it’s a solution if you let it be. it feels you’re hyperfocusing on the solution you want rather than the issue you want to fix. you can make a function on cpp and mark it as blueprintcallable, with autocreateref for a text. and be done. creating a node, and creating a function. is not a lot of difference. a macro would be far more efficient since it could be compiled out. but i think comments are even better.
to be honest never in my career did i needed such a thing. mixing stub code with production code sounds like a bad idea to me. even in cpp when i need to do something similar i use comments.
i’m thinking you might also get a better outcome just by designing your things in a google doc and sharing with the team. it will be faster to improve.
anyway, if you want it, you can create a node yourself. i think it’s called k2 nodes, you can see some examples in the code. when you compare the work involved with a simple macro, you might think that a macro is good enough.
That’s not the point though. A comment can’t be plugged into so if I need to put some placeholder in between existing code I have to move everything out to make room then have the pin go through it, and if I move anything I have to then go back and rearrange everything.
I get that not everyone wants it or doesn’t find a need for it but there are tons of nodes people don’t feel like they need but exist.
I’m basically asking for a node to leave a comment in that has execution pins for organization, not a comment box that just floats not attached to anything.… I feel like people are thinking I’m asking for something else. I just want a cleaner way to leave a comment. It has nothing to do with actual code. Pseudo code is just comments.
I don’t know C++ very well so easily making one isn’t something I can easily do. Again, I feel like people are misunderstanding. It’s not even a problem, I’ve said other suggestions work I just think they are clunky and I want a cleaner way, which is why it’s a suggestion. It’s just a QOL thing for me, production doesn’t hinge on it.
So if you have a long wire you plan to add a function to later, stick 2 rereoute nodes on it about a function width apart, and wrap them with a comment. Or as others have said, just make an empty placeholder function. Name it something like Do X Logic Here, then wire up the actual logic inside it later. IMO, teh placeholder function idea is cleaner than a pseudonode, since execution pins wouldm’t even need to be rewired. At worst one might need to nudge things around to make room for inputs, but that would be true of a dummy pseudonode as well.
