Home

---

Before using the plugin and creating content, it is helpful to understand the key concepts of Open Logic. Understanding these concepts will get you ready to use the plugin!

---

A foundation for your systems

Open Logic provides you a blank canvas—a foundation for building your own systems from the ground up. It is designed to be flexible, allowing you to create exactly what you need without being limited to a default node style or graph editor style— you can create your own styles. You have the freedom to create and customize your own nodes and your own graph editor style. Whether you are developing Quest Editors, Dialogue Editors, Gameplay Ability Editors or any other system, you have full control. The tools are here and it's up to you to shape them into the systems that suit your needs.

---

Tasks and Nodes

A task is a UObject blueprint class that defines the behavior and properties of a node. It acts as a template, telling how the node should work and appear in runtime and in the graph editor.

Tasks are latent by default, meaning if you don't explicitly tell the task to execute an output pin, it will cause the graph to block at that task. The API is straightforward and gives you full control over the nodes in a graph.

A task can be either a function or an event. When used as an event, a task can serve as an entry point in the graph. For example, an On Start task would be an event. You can also control whether an event can be implemented only once in a graph or multiple times.

---

Blueprint vs Open Logic

Open Logic is not meant to replace Blueprint; it's designed to work alongside it. Blueprints are excellent for visual scripting within Unreal Engine, making it easy to quickly create gameplay mechanics and logic. Open Logic, however, offers more flexibility when you need to build custom systems from scratch. Open Logic is better for situations where you need more control and customization.

While the logic for Open Logic Tasks is developed using Blueprints, the actual execution of an Open Logic graph doesn't rely on the Blueprint Virtual Machine (VM). Instead, it uses a custom system to run the graph, which can result in better performance in various scenarios because it doesn't have the overhead associated with the Blueprint VM.