Krulvis

How do you decide if a scripter is 'trustworthy' ? I think it's best to stick with the admin team and just hope that they won't be as busy as they are now in a week or so. I know that they are developing great programs and giving us enormous client updates weekly so I imagine they are very busy on a good cause. Once the client is more as it pleases them they will have more time for other stuff.

I've seen this discussion before :P But I think no matter what, priotity should lay at the hands of the Admins checking the script. It is important to keep safety on a high pitch to make sure nothing bad happens to people's accounts. A untested-sdn could be a good idea if people get well explained that the scripts have not been verrified by admins. This will still remain the protection of the script source and a fast way to let other people of the community test your scripts. It's just really important that people get noticed whenever they run an 'unverrified-SDN' script that it still is unverrified and that the script CAN contain password-stealing code. I heard maxi saying that they protected this client against code like this, but you never know what people can do... I do not know if it is 100% impossible

haha, you guys are making it too easy

Naut jungle

You don't have to actually delete the chat as it is now, it could be a second feature. You also do not need a mic to use teamspeak, you can type there if you prefer

I like the idea but you do need to make sure to give certain people rights and have rooms for different toppics. - Help - General - Scripting - w/e

when people release premium script they will do what they can to update whenever necessary but it's not like scripters gain anything from releasing free scripts. It's just a nice gesture. Consider it a gift that you do not NEED to learn java yourself because there are people who take time to write a script that they give to the community for free.

I bet a yew wcer

I dont think this is necessary. Scripters will test their own scripts until they believe it works. When they feel like it works they will release it (or not). After they release it there could still be some buggs in it but they will find out soon enough. It isn't necessary to make a whole different section for "untested scripts" because there indirectly already is one. As soon as it is decided that a script works perfect it will be added to the sdn. Before it is in located in sdn you could say (if you prefer to use that term) that a script is in testing mode or "beta" as you called it

Thanks for the heads up. I'm so glad I got convinced to stay in this community when I joined... Thanks Xerion

Why do I get this error? It seems like isEmptyExcept() doesn't even exist...

Script writers love it when you help them find errors in their script. But the usual Doesn't really help well... There is a way to get the full error so you can see exactly where the problem in the script is. As you can see on the screenshot above I can see exactly what and where in the script causes the error. This is way more useful and it would be great if more people used this. How does it work: Open a notepad and type the following text: "C:\Program Files\Java\jdk1.7.0_07\bin\java.exe" -jar osbot_1.4.5.jar -dev Change the directory to your JDK version and change the 'osbot_1.4.5.jar' to the osbot.jar file you downloaded from OSBot's website. Make sure there aren't any spaces in the name because that won't allow it to work. After you found the corrent directory and changed the name of the osbot.jar file to yours SAVE THE FILE AS... run.bat and make sure to select all files(*): After you named it, save it or place it in the same folder as your osbot.jar file

m/s OR mps but not mp/s

Xp p/hour ? you should really fix that.

THANKS GUYS

Thanks for the update, I've stared confused at my screen for a moment when this also occured to me

There doesn't have to be a reward tbh, The point is to show your creations and winning itself is a reward high enough imo

Or you could make an array of the items you do not want to deposit (all the different hatchets) and make something like this: int slot = client.getInventory().getFirstNonEmptySlot(items);selectInventoryOption(slot, "Store All");

that just blew my mind

All broken hooks will be repaired, and the onLoop() function will be fixed. So much possibilities now

Thanks for the clarification captain obvious

There's some sick stuff going on there

Donating because you want to see improvement, and are thankful for the progress so far.