-
Posts
619 -
Joined
-
Last visited
-
Days Won
1 -
Feedback
100%
Everything posted by FushigiBot
-
Haven't had any issues with the new client launch feature. Would be nice to have the ability to select the world it launches on when in cli. (Ex. 336, f2p, p2p)
-
In simple terms: 99% chance of a ban and less than 99% chance of a ban.
-
Follow this guy's signature's advice right here. Also, you got banned because of the injection. Mirror is a must.
-
Background SF has a Is Interacting and Is Not Interacting checks. However, these are general checks and only come true if an (any) npc is interacting with the player. It doesn't take into account whether the distance you're trying to check comes from that interacting npc or whether the action you want to perform will be performed on the interacting npc. Having the following would be extremely useful for making more advanced scripts. Methods: If Player Distance to Entity <-- Add isInteracting filter Interact with NPC <-- Add isInteracting filter If NPC Overhead Prayer is <-- Add isInteracting filter If NPC Overhead Prayer is not <-- Add isInteracting filter If NPC Health percent is <-- Ad isInteracting filter isInteracting(Character<?> character) Returns whether this character is facing/interacting with the specified character. Why is this useful? There are certain actions in osrs that require for you to take an action based on the interacting npc rather that any npc. This includes trying to keep a safe distance from an npc in a room full of other, similar npcs (Undead Druids, Brutal Dragons, etc.). Switching to correct attack style (Demonic Gorillas). Also, when creating a slayer script so that the slayer items such as bag of salt, ice, etc. are used in the interacting npc rather than any npc in the room. How can it be used? Moving away from melee range in Undead Druids: [0, Variables, getBoolean, 1:shouldMoveAway, 3:false] [0, MyPlayer, getDistanceTo, 1:Undead Druid, 1:NPC, 1:<=, 2:1, 3:true] (isInteracting Filter) [0, Variables, editBoolean, 1:shouldMoveAway, 3:true] Changing to the correct weapon in Demonic Gorillas [1, NPC, getPrayerIcon, {true}, 1:Demonic Gorilla, 1:PROTECT_FROM_MELEE] (isInteracting Filter) [1, Variables, editString, 1:Weapon Type, 1:enableRangeWeapon] Interacting with the correct NPC during slayer: [2, Variables, getBoolean, 1:shouldUseSlayerItem, 3:false] [2, NPC, getCurrentHealthPercent, 1:Rock Slug, 2:10, 1:<=] (isInteracting Filter) [2, Variables, editBoolean, 1:shouldUseSlayerItem, 3:true] [3, Variables, getBoolean, 1:shouldUseSlayerItem, 3:true] [3, NPC, getCurrentHealthPercent, 1:Rock slug, 2:11, 1:>=] (isInteracting Filter) [3, Variables, addOr] [3, Variables, getBoolean, 1:shouldUseSlayerItem, 3:true] [3, MyPlayer, myPlayerIsInteracting, {false}] [3, Variables, editBoolean, 1:shouldUseSlayerItem, 3:false] [4, Variables, getBoolean, 1:shouldUseSlayerItem, 3:true] [4, Inventory, interactWith, 1:Bag of salt, 1:Use] [4, NPC, interactWith, 1:Rock slug, 1:Use, 3:true, 3:false, 3:true, 3:false, 3:false] (isInteracting Filter)
-
I sell those exact same accs for $150 (Albeit with a bit more randomized stats)
-
Manually did tutorial island and then botted agility for 24 hours and got a ban
-
Laughs in making 1b gp every 2 days with scripts I made in SF. Edit: SF is actually a tool that lets you create your own scripts without java knowledge. The community scripts are extra, free content. A lot of them work, though. Some people are just more experienced than others.
-
Script Factory Request - If Grand Exchange Is Not Full
FushigiBotreplied to Zackaery's topic in Feature Requests[41, Variables, getBoolean, 1:setGrandExchangeIsFull, 3:false] [41, RS2Widget, isActionVisible, {false}, 1:Buy, 3:false] [41, GrandExchange, isOpen, {true}] [41, GrandExchange, isOfferScreenOpen, {false}] [41, Variables, editBoolean, 1:setGrandExchangeIsFull, 3:true] [42, Variables, getBoolean, 1:setGrandExchangeIsFull, 3:true] [42, GrandExchange, isOpen, {true}] [42, GrandExchange, isOfferScreenOpen, {false}] [42, RS2Widget, isActionVisible, {true}, 1:Buy, 3:false] [42, Variables, addOr] [42, Variables, getBoolean, 1:setGrandExchangeIsFull, 3:true] [42, GrandExchange, isOpen, {false}] [42, Variables, editBoolean, 1:setGrandExchangeIsFull, 3:false] Use this for now xD -
We have the if string = but no if string != Would be useful for numerous things. :D
-
You have to innteract with item in inventory. Manually select the spell and hover over the mithril ore.in your inventory Take note of the action (should be "Use", I think). Replace all your Object actions with the following 1. Select spell 2. Inventory actions (Use?) Also, you need more checks to make this script work well.
-
Method Request - Gets Time Until Next Break
FushigiBotreplied toFushigiBot's topic in Feature RequestsBribe attempt: I'll make a Vyrewatch Sentinel Fighter for the network if this is added. -
More than enough -- the API eliminates much of the need to know extensive java.
-
It's on the SF network ^^
-
This is the official thread of the snippet. What's in the snippet? Custom breaks. Randomized TIMED actions that I designed myself, such as checking a random tab, xp, moving camera, moving mouse slightly, etc. Randomized restore hp logic. Randomized enable running logic. Banking logic. Randomized hop worlds logic. Core renew bond logic. Core restocking logic and basic GE interactions. Areas and positions for commonly used banks. Useful booleans. Examples of how to use it Randomized healing Basic logic [85, Variables, getBoolean, 1:shouldRestoreHp, 3:false] [85, Variables, getInteger, 1:generateEatAtHp, 1:==, 2:0] [85, MyPlayer, getCurrentHealthPercent, 1:<=, 2:40] [85, Variables, addOr] [85, Variables, getBoolean, 1:shouldRestoreHp, 3:false] [85, Variables, getInteger, 1:generateEatAtHp, 1:==, 2:1] [85, MyPlayer, getCurrentHealthPercent, 1:<=, 2:55] [85, Variables, addOr] [85, Variables, getBoolean, 1:shouldRestoreHp, 3:false] [85, Variables, getInteger, 1:generateEatAtHp, 1:==, 2:2] [85, MyPlayer, getCurrentHealthPercent, 1:<=, 2:70] [85, Debug, debug, 1:[Restoring Hp.]] [85, Variables, editBoolean, 1:shouldRestoreHp, 3:true] [85, Variables, generateRandomInteger, 1:generateEatAtHP, 2:0, 2:2] [86, Variables, getBoolean, 1:shouldRestoreHp, 3:true] [86, MyPlayer, getCurrentHealthPercent, 1:>=, 2:90] [86, Variables, editBoolean, 1:shouldRestoreHp, 3:false] When the boolean 'shouldRestoreHp' is set to true, it also generates a random integer that will determine the hp threshold to activate healing the next time. By default, this integer is 0 and the hp threshold is less than 40% hp. You can edit the hp values by changing the hp% check for getCurrentHealthPercent. In order to do the actual healing, you have to do a true check for the boolean shouldRestoreHp, and then set the action such as eating a lobster or whatever food you choose.
-
Giants Foundry Script coming soon?
FushigiBotreplied to ajbelge's topic in Forum Feedback/SuggestionsYou cannot but anvil smithing is only worth it in f2p. Therefore useless in p2p as both money maker and training method. -
Giants Foundry Script coming soon?
FushigiBotreplied to ajbelge's topic in Forum Feedback/SuggestionsYeah the double cannonball mould is the only nice reward imho. The outfit is just meh since you can't use it in f2p. -
Method: If time until next break > or < (I don't think we need all the operators since the timer is always running when not breaking) int getTimeUntilNextBreak() Gets the time (in seconds) until the next break will occur. Why is this useful? As of right now, there is no way to make the bots do a particular action when the breaking timer is a certain value without using custom breaks. The problem with custom SF breaks is that you have to turn off OSBot breaks for it to work properly. Not every SF script and/or SDN script supports custom breaks, making the turning on/off of OSBot breaks a bit dangerous/tedious (especially when using cli) since you might forget to turn them back on when using another script and the bot will go YOLO for 12 hrs. How can it be used? It's all about dangerous activities that can result in the death of the bot. For example, say you're doing Undead Druids. One could tell the bot to walk to a safe area if the timer until next break is, say, less than 10 seconds. The applications are many and it would give scripters more flexibility when writing scripts, especially on activities where the bot can die or any other inconvenient situation caused by breaking on the spot.
-
Giants Foundry Script coming soon?
FushigiBotreplied to ajbelge's topic in Forum Feedback/SuggestionsDon't think there is high demand for it since BF is just better in every aspect except for the unique rewards part. -
Working flawlessly as far as I can tell.
-
Will run it tonight with accs that have and dont have the reqs
-
This is why we all love Token.
-
This one issue with placing the orbs may have to do with Token using map positions (Correct me if I'm wrong) to place the orbs, since the object has the same id. If the camera angle is in a way where the target map coordinate and another, interactable interactable object, are within the same MOUSE position on the screen, it will interact with the one closest to the camera. Keeping the camera pitch above 55 on this part of the quest would completely eliminate this issue.
-
Just so that you have an idea, my farm makes around 2b per week and I have nearly 200 accs running + have been botting for years.