Hey — we have fixed the following bugs in the UBot Studio 3.3 – Beta Release Version x63. Thanks being involved in the private beta and look forward to your continued feedback. We are hoping this to be the final beta release before we roll-out the UBot Studio 3.3 Release Candidate 1 on the public update system. fixed: create compilation system (not yet implemented into system) fixed: edit will fail on the wrong type of parameter fixed: ctrl-v pastes over blank space command fixed: run sub parameter window has a blank space fixed: error when loading bots Please note that the old bug threads are now void and have been closed. If you find that a problem is still there, please report it again as a new thread. Download Instructions : Please download the new file from the same link as it was given to you initially. The URL for download is http://ubot.me/beta-3.3/ and the access credentials are the same as before. You are advised to delete the old beta version from your hard-disk and use the Beta Release Version x63 for testing.
Finally! UBot Studio 3.3 Beta is here!
After weeks of development, UBot 3.3 is finally ready. This version completely changes the workflow of UBot Studio in a way that makes it many times faster and more efficient. Here are some videos that provide a quick overview of the new version Video 1 Video 2 A few things I forgot to mention in the video: parameters now have labels the script window is animated smoothly if you are dragging something to the edge of the window, it will scroll automatically send keys chosen field now does capital letters correctly a ton of other little changes here and there If you signed up to receive this limited beta release, then Lord Brar will contact you shortly with instructions on how to download it.
3.15 – The New Update System
We appreciate everyone’s patience with the updates to UBot. We’ve now implemented a more intelligent system, and once you update to this latest version, all subsequent versions will use the new system. A few things to point out here: First of all, you will now have the choice of whether or not you want to update. There is a possibility of mandatory update, for instance if there are major security concerns, but 99% of the time, the updates will be entirely voluntary. When you see an update prompt, it will now give you a message about what is in the new update. This gives you the opportunity to look through exactly what features have changed, to let you make a more qualified decision. There are now 3 types of updates: STABLE, BETA, and MANDATORY. As I stated previously, the mandatory updates will be used sparingly, and only when there is a major security concern or a fundamental system change. A beta release will be made any time we add or change a feature. While we always test things before releasing them, there are many contexts in which UBot is used and sometimes bugs can slip through the cracks. Beta releases will give our power users a chance to try new features and find bugs while casual users can simply wait for the stable releases. A stable release is, as it sounds, a release that has been tested and (hopefully) has no bugs in any new or changed features. We hope that this change will take some of the edge off of the frequent releases, while still allowing us to provide an ever-evolving platform for growing the power of UBot. Let us know your opinion!
3.14 – timeouts on wait commands
this one was added purely at the requests of a number of users. from now on, when you use a wait finish or wait for command, you’ll have a timeout option, which will allow you to force the script to continue if the command hangs for too long. you will specify the timeout in seconds. enjoy!
3.124 – In Sub Window
The latest ubot update brings with it a wonderful new command: “in sub window”. You can find it under the flow menu. It is a container command, and what makes it special, is that any commands you put inside it will run inside a different window with a different webbrowser than your main ubot webbrowser. As I pointed out in my last blog post, this opens us up to the opportunity to create our own captcha service scripts. It also enables us to do many other things – pretty much anything you need to do but that you don’t want to leave the current page for. This update also contains some upgrades to the autosave system.
3.124 – In Sub Window
The latest ubot update brings with it a wonderful new command: “in sub window”. You can find it under the flow menu. It is a container command, and what makes it special, is that any commands you put inside it will run inside a different window with a different webbrowser than your main ubot webbrowser. As I pointed out in my last blog post, this opens us up to the opportunity to create our own captcha service scripts. It also enables us to do many other things – pretty much anything you need to do but that you don’t want to leave the current page for. This update also contains some upgrades to the autosave system.
The Captcha Problem and My Solution
Let me start out by noting that tonight’s update does not contain the solution I’m talking about in this post, but I am working on the solution right now and it will be available very soon. Tonight’s update contains a fix for the search page command There has been a lot of frustration lately about the utter failure that has become of decaptcher and the high prices of ITT. I’ve been thinking on how to provide a sensible solution in a way that would quick and painless and not clutter up the interface of ubot with a bunch of redundant commands. Looking through the various captcha services, I noticed something interesting. Many of them, if not most of them, have a form based system, in which you navigate to a web page, upload the image file and an api key or something of the sort, hit submit, and it sends you back a solution. This forces me to think of how easy it would be to actually make a captcha reader in ubot. all one would have to do is utilize the “save element image” command and simply make a script to fill out the form. The only problem is that in order to do this, you would have to actually leave the page that the captcha is on, which would lose the captcha, and thus lose the purpose of decoding it. It’s kind of a shame, because it would be pretty easy to use a number of new services if there were only a way to navigate to a different page without losing your place on the page you’re decoding. This leads to my proposal. What I’d like to do is have a command that can contain other commands (the way that a loop, for instance, does). When the script gets to this container command, it will load a new webbrowser in a new window. Any command that is put into the container will be executed in the new webbrowser. This means you can run an entire mini script completely separately without disturbing your main script. Besides any number of other uses that I’m certain people will come up with, one fantastic use for this will be, of course, uploading a captcha image to a captcha reading service. What I’m essentially doing is enabling ubotters to make their own captcha solving commands using any service they’d like (as long as they have a web based system, which many do). I think this will be the least cluttered, least limiting solution to our captcha solving woes, and at the same time, it will enable our script to do more things that I probably haven’t even thought of. I’ll be working on this and I should have an implementation within a couple days. Let me know your thoughts.
3.122 – some basic usability and bug fixes
the first iteration of autosave was a little quirky, and well, lets face it, downright annoying. I’ve played with it a little to make it a little less save happy and to not interfere when you’re using the autoplay and autoclose functions. it will also not come up if you open ubot by double clicking a .ubot file. I also wrapped the keyboard commands in a generic error handler to get rid of those nasty errors people were getting when pasting sometimes. Finally, I fixed a bug that was keeping itt from working correctly.
support.ubotstudio.com
UBot Studio has had a period of explosive growth in last few months and we have more than 400 customers right now — and we are growing fast, gaining more UBotters every single day. With all this growth, there comes a responsibility to keep increasing the feature-set of software while making sure we provide top-notch support to the existing users. I have to say that we are very lucky to have an active UBotting Community on the forum that actively helps each other out. To all the active members on the forum for participating in the discussions — you know who you are and we really really appreciate it. UBot Studio would not be where it is not without the strong community behind it. However, there are a lot of support requests that customers don’t prefer to discuss in public. Until now the way was just to quickly shoot me an email and I would try to answer the email directly. Recently the number of emails that I have been getting are just pure overwhelming. As much as I love to help all of you, there are a lot of emails that can be answered a lot quicker by someone else on our technical team. While we would still prefer the forums to be first place where you ask the questions — as that documents the answer for other users — but if you still need to get in touch with me or someone from the technical team, we have now setup a ticketing system on http://support.ubotstudio.com When you submit a question through support system, we will have better control over making sure that your issue is addressed. This will make support a much cleaner and more organized process, and will ultimately let us serve your support needs more efficiently and effectively. Also, you don’t really need to create a separate account to create a ticket. Just go ahead and submit a ticket — that will work! I, Seth, will personally have my nose in the ticket system frequently, so this will fully replace my previous request of having you guys email me for support issues. Helpdesk URL: http://support.ubotstudio.com
support.ubotstudio.com
UBot Studio has had a period of explosive growth in last few months and we have more than 400 customers right now — and we are growing fast, gaining more UBotters every single day. With all this growth, there comes a responsibility to keep increasing the feature-set of software while making sure we provide top-notch support to the existing users. I have to say that we are very lucky to have an active UBotting Community on the forum that actively helps each other out. To all the active members on the forum for participating in the discussions — you know who you are and we really really appreciate it. UBot Studio would not be where it is not without the strong community behind it. However, there are a lot of support requests that customers don’t prefer to discuss in public. Until now the way was just to quickly shoot me an email and I would try to answer the email directly. Recently the number of emails that I have been getting are just pure overwhelming. As much as I love to help all of you, there are a lot of emails that can be answered a lot quicker by someone else on our technical team. While we would still prefer the forums to be first place where you ask the questions — as that documents the answer for other users — but if you still need to get in touch with me or someone from the technical team, we have now setup a ticketing system on http://support.ubotstudio.com When you submit a question through support system, we will have better control over making sure that your issue is addressed. This will make support a much cleaner and more organized process, and will ultimately let us serve your support needs more efficiently and effectively. Also, you don’t really need to create a separate account to create a ticket. Just go ahead and submit a ticket — that will work! I, Seth, will personally have my nose in the ticket system frequently, so this will fully replace my previous request of having you guys email me for support issues. Helpdesk URL: http://support.ubotstudio.com

