With tons of features, but I really don't love the interface and I'm not to thrilled about full RPG Engine thing, I would prefer to take care of UI etc stuff myself, and have classes that I can use and setup myself without having to rely on ORK Interface. Setting up things takes a lot of time and it's subpar compared to Unity Inspector.
ORK is full of things that make me think "that's now how
I would have done it.". That's always the trade off when you use a framework created by someone else versus rolling your own. It takes some time to get used to the editor and how everything is set up in it.
You don't have to do everything through ORK, as it has an API that you can call from your own code, plus you can call functions on components through the event system. That does require some coding, but still a lot less that implementing everything that ORK does on your own.
There are a few posts on the ORK forum about only using parts of it. However, it is more flexible than it might appear at first. My approach is to use ORK's features as long as possible; if I reach a point where I would need to make major compromises to my design, then I would look at other solutions. So far, I can tell that the camera and player input will get replaced (but even the author suggests that you might want to do so), and Pixel Crushers' Dialogue System will replace ORK's native dialogue functionality.
As for other tools that you might want to look at, there is the classic combo of Playmaker and Behavior Designer, aling with Pixel Crushers' Dialogue System For Unity, Opsive's Third Person Controller, and Inventory Pro. I believe that all of these tools now integrate well with each other.
However, there is still the issue of a combat system, and there isn't currently anything on the Asset Store that gives you a decent turn based tactical combat system. Turn Based Toolkit is closest, but it is designed with smaller, contained battle maps in mind -- like FF Tactics or Fire Emblem. Adapting it to an RPG with large area maps (Fallout, ToEE, etc) would be a lot of work. MapNav2 would handle pathfinding on a grid, but you'd need to write all of the turn-based code yourself.
Each of the tools that I mentioned above are better at their specific tasks than are the equivalent ORK systems. But you're already talking $300+ worth of tools here and you haven't touched on RPG systems, combat, art, etc.
