Really need help with a monster loop.

[Your Computer]

Monsters become disabled when either the player is out of its activation distance or when they reach the last patrol node while the player doesn't see the monster. If you edit the monster, you can increase the activation distance and you can override AutoRemoveAtPathEnd in the user defined variables of the entity so that the monster doesn't get disabled when it reaches the final patrol node.

You do not have to continually add patrol nodes to the monster. There's a reason why they're called patrol nodes: the monster will loop through them automatically.