Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/20/15 in all areas

  1. This release might be my biggest or second biggest release here, and this will affect every single scripter and botter here. Not only did I write code to make this update come to life, but @Maxi contributed essential components to make this happen. As usual, thank @Zach for continuing to work modestly behind the scenes. As the title implies, everything you do has changed. When first coming here, I was often frustrated with interactions. Why is my script attempting to walk on the minimap for an object right next to me? Why is my camera rotating to pick an NPC out from a mile away? The entire interaction event system has been re-written. Not only does the code look a lot cleaner, it's faster and handles a lot more situations than the previous interaction events. Unfortunately while working on this re-write, I ran into API that was just flat-out not working or only worked in limited circumstances. Although this set me back two days from my initial projected release date, everything that was broken was patched and improved. Memory/CPU Usage: Depending on the script, you may see a dramatic drop in computer resource usage (up to 50% for RAM and 25% for CPU). Changelog: -Re-wrote entire InteractionEvent --Added cameraDistanceThreshold(int) ---Default camera threshold set to 8 --Added setMaximumAttempts(int) --Drastically improved visibility checks/handlers --Design is linear allowing for events to be executed much more quickly with higher precision. --Added inventory misclick handling --Default walking distance threshold is 24 -Added setSafetyOverride(boolean) --Safety override ignores distance thresholds when visibility checks fail -Re-wrote the entire Menu API --getMenuIndex(Entity,String[], String[]) is now deprecated --New method is getMenuIndex(String[], String[]) -Updated Magic.deselectSpell() -Updated Magic.cast() to check if the same spell is already selected -Updated Inventory.deselectItem() -Patched WalkingEvent -Updated LocalWalker.walkPath() -Removed loading gif saving ~600kb -Removed unused code saving ~50kb @Maxi's updates: -Patched DynamicCircularPathFinder @Zach's updates: -Patched Auto-updater -Fixed various connection issues (thanks ikos9 for your patience) -Updated SDN infrastructure There are a ton of updates with this release. I'm not sure if scripts will break or perform drastically different. If you have any questions or concerns, please post below. API Docs have been updated
    4 points
  2. Fair enough. Im not disagreeing with you necessarily I am just saying it is a safe assumption if you are familiar with the api here. Where I work I write alot of code documentation, and I will always specify something like you stated, "otherwise returns null". For the scope of OSBot, its pretty safe to assume that it will be null though. ^_^
    2 points
  3. There's a problem with walking event which only seems to be apparent now because interaction event was re-written properly. Maxi is working on it at the moment.
    1 point
  4. I was botting flax, got banned 20 seconds later.
    1 point
  5. I'm going to US in April :c Sux for me :'c
    1 point
  6. but you can switch off ironman mode and drop trade to your main so its not even the slightest bit pointless
    1 point
  7. bank#open looks for the closest bank booth. doesnt support npc bankers not sure about chest. Also it doesnt matter if it in sight i believe it will walk to entity and also rotate camera to the bank. Bank class extend item container. if bank isnt open then you simply get a null ps. the bank itself is a item container just like a shop and also inventory.
    1 point
  8. DOTW would be interesting to see, maybe every two weeks to ensure a few entries either way I always love looking at cool shit ^^
    1 point
  9. the font in the layout is too hard to read, but nice work man edit ~ looks nicer now :P
    1 point
  10. u basically run around saying " imma botter", then ppl think u jokin etc and then u turn yo script on etc
    1 point
  11. Unobfuscated Results Obfuscated Results That's completely fine, but continue to get detection results such as the ones above from Malware-Bytes.
    1 point
×
×
  • Create New...