Alek

From Alek's woodcutter (pieced together): GraphicUtilities.getModelBoundingBox(bot, o.getGridX(), o.getGridY(), o.getZ(), o.getModel()); g.drawRect(rectangle.x, rectangle.y, rectangle.width, rectangle.height);

Should be online as of last night.

Work smarter not harder. I'd rather have a scripter that writes logic correctly the first time around than an "active" scripter that pushes 10 commits a day because the logic is consistently flawed.

How about we remove the emojis that we dont use?

Alright now what's the scripting question?

So what's the scripting question?

Was my answer not good enough for you @dmm_slayer?

This is not a scripting question.

That was the same issue you were having before?

Sorry for the delay, services should be restored. If you have any issues please post below. Additionally skill worlds and deadman worlds were removed from the login rotation. You will also find the new GrandExchange API in this update.

Would you mind taking a screenshot?

You will not be able to modify any settings set by the botter, they have the higher privileges. Edit: Example: breaks, human input, f2p/p2p world, etc.

Looks like you are missing a break after Pizza2 case. See if it that helps.

You can have getters in your GUI class, then check it in your Main class. Main: if(GUI.clickedStart()) { var1 = GUI.getVar1(); var2= GUI.getVar2(); GUI.dispose(); }

Well that's pretty embarrassing, they look similar. Well, thankfully it's a dev build. Good catch. Edit: Going to hurt Czar.

Yes, just testing the waters on the buyItem method first.

GrandExchange API: 1. The biggest change was adding a new method: buyItem(int itemId, String searchTerm, int price, int quantity) It handles literally everything for you including: -Scrolling through items with similar search terms -Going back if you are in sell screen -Resetting search if a term is already entered/not visible 2. buyItem(Box)/sellItem(Box) have had their logic slightly changed, some more automatic stuff in there too. Containers Continuity: Thanks to @Czar for his suggestion. The method isEmptyExcept() is now found in all containers including Bank, Trade, Store, etc. In addition I removed two duplicate Store contains() methods which were similar to the methods found in the super class. Other: -RS2Widget toString() overide with custom return, "root, second, third" -Removed worlds from F2P login list New scripts: -QverkkyAgility by @qverkk -Juggles AIO Shop Buyer by @Juggles -Glorious TzHaar by @Shudsy -HIronMiner by @venetox -Khal Wintertodt by @Khaleesi

Well I think you guys are kind of missing a big question. Does the GUI for OSBot look correct and the GUI from scripts look incorrect?

I'm guessing you're not on Windows?

What does cmd/bash/terminal/whatever say?

Your original post was well written, so a mature discussion deserves a proper response. I'll try to highlight specifics so you can get some direct answers. This has two parts, getting a script approved and getting a git account set up. First, I have never made a git account for anyone here since I joined 3 years ago. Second, there are a lot of reasons why a script may take a while to be approved. Now the phrase "a while" is pretty subjective, most people who I see that are unsatisfied have waited well under a week. One week turnarounds are pretty standard after the script is completely finished. If a scripter claims that a script is complete and I find numerous problems with the code, the scripter is then directed to fix the issues prior to release. This is the main cause for scripts being delayed, so please ensure your scripts are actually ready before they get reviewed. This is not quite how the process works. There are two different tracks, one for free and one for premium. Premium scripts require a plan review prior to developing the script whereas free scripts require no such plan, and you can release after it's finished. Many free scripts are made by newer scripters/programmers and are often bug-prone. I spend A LOT of my time coaching people on proper techniques. Once again, delays are caused from the issues highlighted above. The SDN is not guaranteed. Only properly written scripts will have the opportunity to be distributed to thousands of botters. It is a direct reflection of our services. This community has also been plagued by people who have distributed malicious code and people who have attempted to distribute malicious code through the SDN. Unlike other communities who risk their user base by not performing reviews, we spend a lot of time sitting down and reading other people's code rather than writing our own.

Thanks for that site @@Imateamcape, but it didn't have translations for the words that I needed. Also needs to be in cyrillic @@melomel.

You have a high DPI display and Swing is not DPI aware (or it is I forget which). It can't really be fixed from our end, still something I'm investigating.

.

granted