Skip to content

Request for More Robust Documentation (Data Passing & Node Variants) #364

@Zodsmar

Description

@Zodsmar

I am trying to figure out exactly what’s possible with this plugin, but the current documentation is missing some technical depth regarding data flow. I've looked through the Demo Project as well, but since it's all C++, it’s hard to translate some of those concepts to a Blueprint-heavy workflow.

Please consider expanding the documentation to cover:

  • Property Exposure: Is it possible to expose variables in Flow Node Blueprints so data can be passed in/edited directly from the Flow Asset? I'd like to see how to make node-specific data editable for designers in the graph.
  • Architectural Differences: I’m looking for a clear comparison between Flow Nodes, Flow Node Add-on blueprints, and the regular versions. Also, what is the intended use for Flow Asset Params?
  • Data Flow: Best practices for passing data from a Flow Asset into specific nodes.

Even updating the Demo Project to include Blueprint examples alongside the C++ ones would be awesome and would really help the onboarding process. Thanks!

Edit: My main concern is in 5.3, the pin type was functionally grouped with the Pin struct, so when I make an Input or Output, I used to be able to specify the pin type (which now seems to be always an EXEC pin). It seems to have been deprecated, so how is this achieved now?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions