And I have still another feature request ... isn't it Xmas, time of gifts&presents?
It is very simple (but possibly hard to create): I am looking for a diagnose tool:
Sometimes I am getting "output not found" messages or other unexpected #outputs from the Verbot, and hell - I cannot find the rule where it comes from!
So my request is a small developer window or a console appendix after the regular output that tells me the name of the KB and the name of the rule that fired the #output, and always appears after activating a kind of 'debug mode' of the Verbot player.
It is rather a similar, but simplier feature compared with the right list field of the KB tester.