The link redirects to https://https//discourse.behaviortree.dev/ instead of https//discourse.behaviortree.dev/.

Hi, as a newbie I could not figure out what code to add inside the C++ code of tutorial_01_first_tree (version 3.8) to communicate with Groot1 to make it show states. Sad to have to ask to chatGPT how to do it (sorry if this information exist and I have not found maybe this is not enough hightlighted):

#include <behaviortree_cpp_v3/loggers/bt_groot_logger.h>

BT::StdCoutLogger logger_cout(tree);
BT::MinitraceLogger logger_minitrace(tree, "minitrace.json");
BT::FileLogger logger_file(tree, "bt_trace.fbl");
BT::GrootLogger logger_groot(tree);

while (tree.tickRoot() == BT::NodeStatus::RUNNING) {
        // Attente active
    }

But in my case the header does not exist. I guess this is bt_zmq_publisher.h but what I have to do ?

Hello,

For this section, "An Inverter followed by the node called isDoorOpen is...", this seems to be inconsistent with the node shown in the given figure which has the node labelled "isDoorClosed".

Do correct me if I understand it wrongly.

Thank you very much.

Hello. Opening this page in firefox results in the following error:

I can reproduce this with Firefox 107.0.1 on Linux, and firefox 107.1.0 on Android.

UPDATE: it seems related to uBlock Origin extension. if I disable it, the page loads correctly.

Under https://github.com/BehaviorTree/btcpp_website/blob/master/docs/nodes-library/SequenceNode.md#sequencewithmemory
you mention

On the other hand, isBatteryOK must be checked at every tick, for this reason its parent must be a ReactiveSequence.

but neither isBatteryOK not ReactiveSequence is part of the diagram.

05. Using SubTrees

In section "The CPP code", the function BT::NodeStatus isDoorClosed(); is marked as // SUCCESS if _door_open == true, but it should be the opposite.

06. Port Remapping

In the given XML schema, for Script nodes, the port script is used instead of the port code

I think the picture in https://www.behaviortree.dev/docs/learn-the-basics/BT_basics#fetch-me-a-beer-revisited section maybe have a error state.

This ForceFailure node should not be green (SUCCESS), it should be red (FAILURE). At the same time, if the ForceFailure node is green, then the Fallback node should also be green. Additionally, the subsequent CloseFridge will be executed again, meaning that the fridge will be closed twice. I don't think this is the expected behavior.