This is a wonderful module, and it has helped me overcome a big problem. I love it.

However, it seems to me that the sequence of actions is wrong. (I know nothing about coding, so I'm just commenting from a users perspective).

First, it would make more sense (to me) that "check a node limit" should be a condition rather than the triggering event. When I created my first rule with this module, I was expecting to write something like:

- Trigger: User has created a node of type: xx
- Condition: Check to see if node limit has been reached
- Do: Something

That's not a problem, but it seems odd to me.

Second, The actions, which result from reaching the node limit, don't actually trigger when the user reaches the limit. Instead, they happen when he tries to create 1 node over the limit.

For example, I set a node limit of 2 for my trial members. As soon as they save the second node, they should be reassigned to a "trial lapsed" role.

But with this module, nothing happens after they save the 2nd node. Their role is only changed when they try to create a 3rd node.

Again, I can work around that, but it is a problem for me. It means that a user whose trial membership has expired might actually stay in that role forever, as long as he doesn't try to create a 3rd node.

As I said, I love this module. But please consider my comments. As good as the module is, it would be much better if it performed the way I am describing.

Thank you so much for your work.