Leaderboard

Script Factory ChatGPT Support!

We're excited to announce that Script Factory now supports ChatGPT through AltChat! AltChat is an incredibly smart and affordable AI chatbot that can now engage in real conversations and even talk about Old School RuneScape in specific. With AltChat, you can reduce bans and increase account randomness at an incredibly low cost. Fund your entire farm for only a few bucks a month! We're thrilled to offer this innovative solution to our users and can't wait for you to try it out. Add it to any Script Factory script with just one click. Visit https://www.altchat.app/ to register! Here are some quick examples:

June 1, 2024

2 points

Perfect Fighter AIO

NEW! Added Gemstone Crab! 81 Hours at Cows Brutal Black Dragon support Sulphur Nagua support Blue Dragon 99 ranged 99 Ranged at Gemstone Crab 81 Range F2p Safespotting Hill Giants Hotkey List // F1 = set cannon tile // F2 = hide paint // F3 = Set afk tile // F4 = reset afk tile // F6 = Set safespot tile // F7 = activate tile selector // F8 = Reset tile selector // F9 and F10 used by the client, EDIT: will re-assign as they are no longer used by client // F11 = Set breaks tile // F12 = Reset breaks tile User Interface Banking Tab Demo (handles everything with banking) You can copy inventory (to avoid adding individual items...), you can insert item names which have Auto-Fill (for you lazy folk!) and you can choose whether to block an item and avoid depositing it in bank, ideal for runes and ammo. Looting Tab Demo (From looting to alchemy, noted/stackable items too) You can choose whether to alch an item after looting it simply by enabling a checkbox, with a visual representation. All items are saved upon exiting the bot, for your convenience! Tasking Demo (Not to be confused with sequence mode, this is an individual task for leveling) You can set stop conditions, for example to stop the bot after looting a visage, you can have a leveling streak by changing attack styles and training all combat stats, you can have windows alert bubbles when an event occurs and an expansive layout for misc. options! Prayer Flick Demo (Just example, I made it faster after recording this GIF) There are two settings: Safe mode and efficient mode, this is safe mode: Fight Bounds Demo Allows you to setup the fight bounds easily! Simplified NPC chooser Either choose nearby (local) NPCs or enter an NPC name to find the nearest fight location! Simple interface, just click! Level Task Switch Demo (Switching to attack combat style after getting 5 defence) You can choose how often to keep levels together! e.g. switch styles every 3 levels Cannon Demo (Cannon is still experimental, beta mode!) Choose to kill npcs with a cannon, recharges at a random revolution after around 20-24 hits to make sure the cannon never goes empty too! Results Caged Ogres: How does this bot know where to find NPCs? This bot will find far-away npcs by simply typing the NPC name. All NPCs in the game, including their spawn points have been documented, the bot knows where they are. You can type 'Hill giant' while your account is in Lumbridge, and the bot will find it's way to the edgeville dungeon Hill giants area! Here is a visual representation of the spawn system in action (this is just a visual tool, map mode is not added due to it requiring too much CPU) Fight Area Example (How the bot searches for the npc 'Wolf') Walking System The script has 2 main walking options which have distinctive effects on the script. The walking system is basically a map with points and connections linking each point. It tells the script where to go, and decides the routes to take when walking to fightzones. Walking system 1 This uses a custom walking API written by myself and is constantly being updated as new fightzones are added. Pros: - Updates are instant, no waiting times - More fightzones are supported Cons: - Sometimes if an object is altered, the changes are not instant - Restarting the script too many times requires loading this webwalker each time which adds unnecessary memory (there is no way to make it only load at client startup since I don't control the client) Walking system 2 This is the default OSBot webwalking API - it is relatively new and very stable since the developers have built it, but is currently lacking certain fightzones (e.g. stronghold) and other high level requirement zones. It is perfect for normal walking (no object interactions or stairs, entrances etc) and never fails. Pros: - Stable, works perfect for normal walking - All scripters are giving code to improve the client webwalker - More efficient when restarting the script since it is loaded upon client start Cons: - No stronghold support yet - Some new/rare fightzones not supported yet - If there is a game-breaking update or an unsupported fightzone, it may take some time to add/repair (less than 24 hours usually) So which system should I choose? Whichever one suits your chosen fightzone best! There really shouldn't be any problems - the sole purpose of these options are for backup and emergency purposes, if the script ever messes up there is always the next option to select. Note: If the script ever fails, there will be immediate updates to fix the walking systems! Script Queue/Bot Manager: Script ID is 758, and the parameters will be the profile name that you saved in the fighter setup! Bug Report templates: New feature request - What is the new feature - Basic description of what the script should do - Basic actions for the script: 'Use item on item' etc. For when the script gets stuck on a tile (or continuous loop): - Which exact tile does the script get stuck on? (exact tile, not 'near the draynor village') - Plugin or normal script? - Did you try all 3 walking options? Script has a logic bug (e.g. dies while safespotting) or (cannon mode doesn't pickup arrows) - What is the bug - How did you make the bug happen - (optional) recommendation for the bug, e.g. 'make the script walk back' or something - Tried client restart? - Normal script or a plugin? - Which exact setup options are enabled? Afk mode, cannon mode, etc etc.

2 hours ago

1 point

Czar Barrows

NEW! Added Grand Exchange auto-restocking! Perfect for goldfarms!! Features Coming Soon: - Deathwalk support - Salamander support - More ironman routes for barrows How to use Bot Manager or Script Queue: Script ID is 1181 Script Parameter is the saved profile name, e.g. hello123.txt

Sunday at 05:55 PM

1 point

Perfect Miner AIO

CURRENT RECORD: 201 HOURS RUNTIME NEW: Sandstone mining + hopper support Humidify/water circlet/bandit unnote Ardy cloak tele support Setup Screen Preview Results 84 HOURS ON NEW LEVEL 20 ACCOUNT Suicided account with mirror mode near rock crabs, 81 mining! I will probably go for 99 Even supports Ancient Essence Crystal mining! Preview: Mine 1 drop 1 item drop pre-hover feature:

October 11

1 point

Perfect Fletcher AIO

65 HOUR PROGGY!!

October 2

1 point

Preventing RS Botting Bans V3

Preventing RS Botting Bans V3 Written by Alek 1. Introduction This guide is Version 3 of my original guide released 4 years ago. I decided to focus more on commonly asked questions and general misconceptions about botting. Many of the topics are very technical and there are brilliant engineers who both bust bots and create them. The majority of botters who come here have little to no programming experience, or very little knowledge in subject areas such as reverse engineering. It’s very difficult to fully explain all key concepts, however hopefully this material will give you a base reference to draw your own conclusions. 2. How to not get banned The secret formula to botting is keeping a very, very, low profile. This game has been around for 15+ years, that is a TON of data to play with. Generally speaking: -Don’t bot more than 4 hours per day -Don’t bot more than 10 hours per week -Diversify your tasks -Don’t use a VPN/VPS/proxy -Don’t bot more than one account -Do quests -Don’t RWT/goldfarm -Don’t bot in hot spots, use places like Zeah You’re going to have a ton of people say, “oh I suicided for 11 years straight, never logged out, I make $500k/year”, etc. They simply don’t. Either they haven’t botted long enough or their claims are baseless. If you want to keep your account relatively safe then don’t bot longer than the times I recommended above. Time played is a key factor into profiling a bot, it’s been even talked about on official livestreams during live bot busting events. 3. Misconceptions The biggest misconception is that the company doesn’t have any automatic detection systems. Although the detection vectors improve over the years, there are official statements claiming that all bans are manually reviewed before being issued. THIS DOES NOT MEAN ACCOUNTS ARE NOT AUTOMATICALLY FLAGGED. Common situation: Suicide bot on the weekend without getting banned, account gets a ban on the following Monday or Tuesday. This is because your account was probably flagged over the weekend, then eventually reviewed for the final determination on the following business days. Another misconception is that if you “survived the weekend”, then you are safe. This is certainly not true, most anticheat will "flag and monitor". This means that you were in fact detected but the anticheat is watching your actions very closely to grab more information about what you are doing. Information from these monitoring sessions are used to quickly detect and ban in the future. For Runescape, one example is the use of bot worlds. Another non-Runescape example is Valve-AntiCheat profiling numerous hacks over the course of months and then issue behemoth ban waves all at once for games like Counter-Strike. 4. Antiban/Antipattern Scripters who include antiban/antipattern methods in their scripts are either naive, new scripters, or are trying to earn more sales by making false promises. Competitor clients further this perpetuation by forcing script writers to implement these methods. It’s a gimmick and overall you’re going to get banned whether you use these "special methods" or not. Some of these “special” (aka worthless) methods are: -Moving your mouse randomly -Checking your exp -Examining random objects -Moving your camera angle randomly -Implementing “fatigue” systems -Diversifying the way you interact with objects One of the special methods I’d like to talk about which was not listed above was randomizing sleep time between actions. This is especially special because there are numerous flaws with it. 1. Your computer doesn’t perfectly execute actions in the same time every time 2. Your script doesn’t perfectly loop in the same time every time 3. Your ping fluctuates causing a delay between the client and server 4. If the top three all remained constant, you could find the upper and lower bounds of the mean and use statistics to recreate the sleep time. Anti-pattern is a bit different, but a lot of scripters have been wrongly claiming their script having “antipattern” when they’re really using the same “special methods”. Examples of antipattern: - Talking to other players (Cleverbot) - Mixing up tasks (perhaps after accumulating X gold, go to the Grand Exchange and sell) The goal of anti-pattern is to reduce the chances of being manually reported by other players for botting. Although “antipattern” is more desirable than “antiban”, there is still no definitive proof of the impact it has in the total picture. 5. Client detection 5A. I’m going to keep this relatively brief because this is probably the most technical aspect of this guide. There is an overarching debate over Injection vs Reflection and it’s pretty silly. Both are detectable because both have different ways you can detect it. In the non-Java hacking world, this would be equivalent to something like ReadProcessMemory versus LoadLibrary. To better put it, reading memory from outside the process versus inside. There are ways to hide it, ways to find it, ways to hide against the ways to find it, and ways to find the ways how to hide it against from finding it. As you can see, it’s really cat and mouse and it boils down to implementation. 5B. Additionally, you can be detected for macroing without even using a client. You can banned for using Gary's Hood or AutoHotKey. Both of these use some sort of Windows API function like SendInput, from protected mode. This is how color-bots also get detected without injecting/reflecting the client. 5C. Mirror Mode adds some protection to users where the normal OSBot client can be detected. Think of mirror-mode as a safety catch rather than a comprehensive antiban measure; and yes mirror mode has genuinely protected users at least on one confirmed occasion. In summary, you will still get banned because mirror-mode only protects you from one aspect of botting and there are potentially hundreds of detection vectors. 6. Conclusion and final remarks Having good botting habits like I outlined in section two, and having a good script which is reliable and not prone to getting baited (locked behind doors, etc), is your safest bet. There are people who do “studies” and “research” but ultimately their results are inconclusive, non-definitive, and certainly only proves a correlation and not causation. There are too many variables to isolate to make any data worthwhile; ip address, computer, scripts, clients, botting locations, skills, account time, bot time, quests, RWT, java exceptions, client detection, the list goes on and on. Too many variables to isolate, too much that we cannot prove. The bottom-line is that the only people who know specifics about the anticheat system are the anticheat developers.