After two months of asking the 5 or so users who claimed this bug was a problem for help to reproduce it, in the tracker and via Skype, Dan finally gave a very clear explanation and I worked directly with him to reproduce it. It took about two hours of his time and we're glad he was able to assist. The issue was that to reproduce the bug, you cannot edit the define command itself, you must only edit the command inside the define. If you edit the define command directly, or switch to code view, the bug doesn't occur.
It is now on the roadmap to be fixed. Assisting us in reproducing an issue is a much more effective way of solving it than talking about it here.
Had to comment on this point - people were willing to give you the bots they were working on when this bug was found and as usual, anything that we wanted to send in had to be cut down to ensure your support / dev didn't have to read through the code. We are not the coders behind Ubot, if we took out chunks of code how do we know we were not taking something that caused the bug to occur out?
Not sure if its laziness that you can't check the code or its down to the SINGLE developer not having enough time to try and fix the bugs whilst introducing features that in turn introduce another pot of bugs into the mix.
As I have said several times before leaving the Skype group before you and your trigger happy finger could boot me from it, get the base code sorted, bug free and stable and then introduce all the frills. That would be a major step in the right direction.
If you all tested the software before rolling it out to paying customers, you may catch the bugs before people have to wait months to years for a fix (Talking the popup problem that I have submitted to your tracker, was marked down to routine and still waiting, the browser resolution that you all said was awesomiums problem and I ended up paying TJ for a working plugin that did it, do I need to go on)
There are bugs in the tracker from early 2014 (the one from 2013 is site specific so will let you have that one) so quick bug fixes are not happening, they are nearly a year old and thats just bugs that got put into the tracker. Not sure what happened to all the bugs that were in the forum before you closed the bug forum down.
Anyway, will leave you with that one before you and Seth declare me a heretic out to trash your company yet again - I have explained I am not but your professionalism is questionable, your software is decidedly not fit for purpose (latest is bug riddled for anyone who wants to try and use the full power of the software and V4 is unsupported) and you will not give a damn again before more marketing spin is pushed out the door.
You nearly had me when Seth pushed out 5.5, that was a huge step in the right direction and look what happened, devs started wanting to work with Ubot again, but after that it nosedived. Lets see if the new single dev Adam can get your failing show back on the road.