I can say with certain confidence, support for allocating passive will not be added anytime in the foreseeable future.
Our API doesn't call client functions to perform actions or send packets. That means the bot must click and drag around the entire passive graph, in order to try and allocate points. Looking past the obvious issues of trying to make the bot use that insane GUI like a human would, you'd have to give the bot the specific passive ids so it knows which nodes to allocate.
At the rate in which the passive tree changes, coupled with the tediousness of how their GUIs are setup (i.e., there's literally 1000 nodes to go though and find gui controls for to start), it's simply not worth the time to try and come up with something that most likely won't even fully work the way we'd like.
It would be quite a challenge, but there's a ton of other things that would be better to take care of first before doing this, so it's not even a consideration right now.
