Jump to content
Frequently Asked Questions
  • Are you not able to open the client? Try following our getting started guide
  • Still not working? Try downloading and running JarFix
  • Help! My bot doesn't do anything! Enable fresh start in client settings and restart the client
  • How to purchase with PayPal/OSRS/Crypto gold? You can purchase vouchers from other users
  • xyz111

    Scripter+
    • Posts

      196
    • Joined

    • Last visited

    • Days Won

      4

    Everything posted by xyz111

    1. Another insane release Thank you for bringing us into the golden age of botting!
    2. Mad inspirational group of developers. Nice release
    3. Pushed an update for the mule, let me know if you're still seeing issues after it's live
    4. I'll look into this.
    5. Terribly sorry about this. I have created a fix, I'll test it for few hours then push it to live. Thank you for reporting it.
    6. Hey, I found the issue and pushed out a fix. Please wait for the next update and let me know. Thank you for reporting it!
    7. What does the console log show?
    8. Thank you for reporting this, and sorry for the unexpected behavior you're seeing. It's certainly not typical. To help investigate this issue, would you be kind enough to send a screenshot the next time you encounter this problem? I would like to try replicating this issue as accurately as possible. In the meantime, I will be reviewing my code looking to pinpoint the root cause of this anomaly. Also, please refer to my previous message regarding the file issue, and you are welcome to reach out on Discord too.
    9. I recently deployed an update which might addresses this issue. Please delete the existing 'RevBracelets' folder. Run the script to generate a new json config file. Open, edit, and save over the newly generated file. Finally, try running the script again. Apologies for the frustration this might be causing. I invite you to connect with me on Discord, you can find my details on my profile. I am fully committed to supporting you and resolving any issues you are facing
    10. Bad copy and paste, sorry for the confusion. I've corrected the information in that post. (Just to clarify, MultiTool is another script that I sell) For your RevBracelets setup, you'll find a configuration file in the RevBracelets folder, which ends with a '.json' extension. Please open this file, make the necessary changes to the values as per your requirements, and then save your changes. After doing this, kindly restart the script for the changes to take effect
    11. I believe the answer is covered below, but if not, please accept my apologies. 1.3.2 Analytics and Other Data https://dreambot.org/forums/index.php?/topic/21484-official-dreambot-scripter-guidelines/
    12. xyz111

      Flinching

      Thinking out loud, don't scold me if this isn't the purest way. (Might also need to wait for start of tick, not sure) When the health bar of NPC is not visible: Retrieve the tile location of the NPC. Attack NPC. Use HitSplatListener to monitor when NPC is hit. Walk 2 tiles away from NPC tile (+2 or -2 to npc.getX or Y, something like that) after hitting it
    13. Thank you it means a lot!
    14. I have implemented an additional correction for the bug: combining noted bracelets. Kindly await further updates. Users should anticipate a rise in hourly profit with latest
    15. xyz111

      xyzMule

      Hi everyone, I've pushed an update addressing the obfuscated config issue. Following this update, please perform the following steps: Please delete the existing config folder for this script. Allow the script to generate a new config folder. Note: Previously, the config might have been located in your Dreambot folder. The new config will now be generated in the DreamBot Scripts folder. Here are the new config paths for different operating systems: Windows: C:\Users\YOUR_NAME_HERE\DreamBot\Scripts\xyzMule Linux: /home/YOUR_NAME_HERE/DreamBot/Scripts/xyzMule Mac: /Users/YOUR_NAME_HERE/DreamBot/Scripts/xyzMule Please replace YOUR_NAME_HERE with your actual username.
    16. Hi everyone I've pushed an update addressing the obfuscated config issue. Following this update, please perform the following steps: Delete the existing config folder for this script. Allow the script to generate a new config folder. Note: Previously, the config might have been located in your Dreambot folder. The new config will now be generated in the DreamBot Scripts folder. Here are the new config paths for different operating systems: Windows: C:\Users\YOUR_NAME_HERE\DreamBot\Scripts\RevBracelets Linux: /home/YOUR_NAME_HERE/DreamBot/Scripts/RevBracelets Mac: /Users/YOUR_NAME_HERE/DreamBot/Scripts/RevBracelets Please replace YOUR_NAME_HERE with your actual username.
    17. Hi everyone, I've pushed an update addressing the obfuscated config issue. Following this update, please perform the following steps: Delete the existing config folder for this script. Allow the script to generate a new config folder. Note: Previously, the config might have been located in your Dreambot folder. The new config will now be generated in the DreamBot Scripts folder. Here are the new config paths for different operating systems: Windows: C:\Users\YOUR_NAME_HERE\DreamBot\Scripts\MultiTool\Scripts\ Linux: /home/YOUR_NAME_HERE/DreamBot/Scripts/MultiTool/Scripts/ Mac: /Users/YOUR_NAME_HERE/DreamBot/Scripts/MultiTool/Scripts/ Please replace YOUR_NAME_HERE with your actual username.
    18. Any output in the log?
    19. +---------------------------------------------------------------------------------+ | Initial Setup | +---------------------------------------------------------------------------------+ | Upon first run, MultiTool creates a directory in the following locations: | | | | Windows: | | C:\Users\YOUR_NAME_HERE\DreamBot\Scripts\MultiTool\ | | | | Linux: | | /home/YOUR_NAME_HERE/DreamBot/Scripts/MultiTool/ | | | | Mac: | | /Users/YOUR_NAME_HERE/DreamBot/Scripts/MultiTool/ | | | | This directory contains the file MultiTool_config.json for easy configuration. | +---------------------------------------------------------------------------------+ +---------------------------------------------------------------------------------+ | Configuration Details | +---------------------------------------------------------------------------------+ | Default Configuration: | | - Delete and reset the file if issues arise after modifications. | | - Note: JSON syntax structure (brackets, spacing, commas) is crucial. | | Be careful not to accidentally delete a bracket, comma, or add/remove | | spacing. | +---------------------------------------------------------------------------------+ +---------------------------------------------------------------------------------+ | Setting Details | +---------------------------------------------------------------------------------+ | MULE_TIMEOUT_MINUTES: (int) Time in minutes to reset mule requests. | | GE_TIMEOUT_MINUTES: (int) Time in minutes to cancel GE offers. | | RETRY_LIMIT: (int) Number of attempts to create a GE offer. | | PORT_NUMBER: (int) Port used for muling on xyzMule. | | BOND_CHARACTER: (boolean) If true, requests coins for bond purchase & redeems. | | LOGOUT_ON_TASK_COMPLETE: (boolean) If true, logs out after all tasks complete. | | UPDATE_CHARACTER_SETTINGS: (boolean) Set to true to enable below settings: | | - ENABLE_WORLD_HOP_CONFIRMATION (boolean) | | - ENABLE_ACCEPT_AID (boolean) | | - ENABLE_SELL_PRICE_WARNING (boolean) | | - ENABLE_BUY_PRICE_WARNING (boolean) | | - ENABLE_TRADE_DELAY (boolean) | | - ENABLE_LEVEL_UP_INTERFACE (boolean) | +---------------------------------------------------------------------------------+ +---------------------------------------------------------------------------------+ | WalkTo Details | +---------------------------------------------------------------------------------+ | WalkTo commands bots to move to specific in-game coordinates. | | Coordinates are represented as (x, y, z): | | - x and y represent the horizontal and vertical positions on the map. | | - z represents the in-game elevation or floor level. | | | | To find these coordinates in DreamBot: | | 1. Activate 'Developer Mode' in the DreamBot client settings. | | 2. After enabling, navigate to the 'Entities' menu & select 'Show Player Pos.'| | 3. Your current location will display as 'Player Position: (x, y, z)' in | | white text within the client, when logged in. | | 4. Move to the desired location for your bots and note the coordinates. | | 5. Enter these (x, y, z) values into the MultiTool_config.json file. | | | | Alternatively, use the explorv.io website map to find coordinates: | | - Navigate the map with your mouse. Coordinates are displayed in the top | | left corner and can be entered into the configuration file. | | | | Enhancing WalkTo with teleports: | | - Pair WalkTo with InventoryLoadoutList or EquipList to enable teleporting. | | - Specify teleport items & jewelry in these settings to utilize the walker's | | teleportation capabilities. | +---------------------------------------------------------------------------------+ +----------------------------------------------------------------------------------------+ | SellList | +----------------------------------------------------------------------------------------+ | - Sells items in the Grand Exchange with custom sell price and quantity. | | - If uncertain of quantity, enter 0 to sell all owned items. | | - For fast selling, set sell price at 1. | | - Item names must be entered twice. | | - Handles scenarios when the item to sell is unavailable. | | - Max 27 items. Error logged if the item is unsellable. | | - Relevant settings: GE_TIMEOUT_MINUTES, RETRY_LIMIT. | | - Example format in 'sellList': | | "Greeen dragonhide": { "itemName": "Greeen dragonhide", "sellPrice": 1, "quantity":| | "Dragon bones": { "itemName": "Dragon bones", "sellPrice": 1, "quantity": 0 } | +----------------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------------------------------------------------+ | BuyList | +--------------------------------------------------------------------------------------------------------------------------+ | - Buys items in the Grand Exchange with set buy price and quantity. | | - Handles insufficient coin scenarios and logs errors. | | - Max 27 items. Error logged if the item buy fails. | | - Item names must be entered twice. | | - Relevant settings: GE_TIMEOUT_MINUTES, RETRY_LIMIT. | | - Example format in 'buyList': | | "Monkfish": { "itemName": "Monkfish", "buyPrice": 500, "quantity": 500 } | | "Varrock teleport": { "itemName": "Varrock teleport", "buyPrice": 1000, "quantity": 100 } | | "Divine super strength potion(4)": { "itemName": "Divine super strength potion(4)", "buyPrice": 20000, "quantity": 20| +--------------------------------------------------------------------------------------------------------------------------+ +---------------------------------------------------------------------------------+ | EquipList | +---------------------------------------------------------------------------------+ | - Assigns specified items to their corresponding equipment slots. | | - Ensure item names match exactly as they appear in-game. | | - Error logging is implemented for items that cannot be equipped. | | - Example format in 'equipList': | | "Hands": { "itemName": "Tormented bracelet (or)" }, | | "Chest": { "itemName": "Void knight top" }, | | "Legs": { "itemName": "Void knight robe" }, | +---------------------------------------------------------------------------------+ +---------------------------------------------------------------------------------+ | MuleGiverList | +---------------------------------------------------------------------------------+ | - Designate items to be transferred to the mule, including coins. | | - Automatically handles scenarios of item absence or untradeable items. | | - Set quantity to 0 to transfer all available quantities of an item. | | - Supports a maximum of 28 items per transaction. | | - Implements error logging for withdrawal or trade issues. | | - Ensure item names match exactly as they appear in-game. | | - Example format in 'muleGiverList': | | "Zulrah's scales": { "itemName": "Zulrah's scales", "quantity": 10000 }, | | "Anglerfish": { "itemName": "Anglerfish", "quantity": 1000 }, | | - Adjust MULE_TIMEOUT_MINUTES and PORT_NUMBER as needed for effective operation.| +---------------------------------------------------------------------------------+ +---------------------------------------------------------------------------------+ | MuleTakerList | +---------------------------------------------------------------------------------+ | - Specify items to be requested from the mule, including coins. | | - Capable of handling scenarios where the mule lacks the requested item. | | - Set quantity to 0 to request all available quantities of an item. | | - Limit of 28 items per request to ensure smooth transactions. | | - Error logging in place for issues with item retrieval or trading. | | - Ensure item names match exactly as they appear in-game. | | - Example format in 'muleTakerList': | | "Zul-andra teleport": { "itemName": "Zul-andra teleport", "quantity": 50 }, | | "Divine bastion potion(4)": { "itemName": "Divine bastion potion(4)", "quant| | - Adjust MULE_TIMEOUT_MINUTES and PORT_NUMBER as needed for effective operation.| +---------------------------------------------------------------------------------+ +------------------------------------------------------------------------------------+ | InventoryLoadoutList | +------------------------------------------------------------------------------------+ | - Facilitates the withdrawal of items from the bank into specific inventory slots. | | - Accommodates both teleport items and items in noted form for various activities. | | - Ensure item names match exactly as they appear in-game. | | - Slots are labeled from 0 (top left) to 27 (bottom right) in the inventory grid. | | - Example format in 'inventoryLoadoutList': | | "Slot0": { "itemName": "ExampleItem", "quantity": 0, "noted": false }, | | "Slot1": { "itemName": "ExampleItem", "quantity": 0, "noted": false }, | | - Avoid using this tool for items involved in Buy/Sell Lists; the script will | | handle them separately to ensure proper processing. | +------------------------------------------------------------------------------------+ +---------------------------------------------------------------------------------------------+ | QuickStart params | +---------------------------------------------------------------------------------------------+ | - The parameter allows you to specify the path of a configuration file. | | - This parameter is optional. If not provided, a default file will be used. | | - To use a custom configuration file, provide its full path as a string. | | - Ensure the path is valid and the file is accessible. | | - Example of how to enter the parameter: | | "C:\Users\Zezima\DreamBot\Scripts\MultiTool\gdksetup.json" | | | | Minimum Settings to Use QuickStart: | | java -jar C:\Users\Zezima\DreamBot\BotData\client.jar -script "MultiTool" -account "myMain" | | -params "C:\Users\Zezima\DreamBot\Scripts\MultiTool\gdksetup.json" | +---------------------------------------------------------------------------------------------+
    ×
    ×
    • Create New...

    Important Information

    We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.