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
  • DreamBot's SDN Guidelines [ALL SCRIPTERS READ]


    Pandemic

    Recommended Posts

    DreamBot’s SDN Guidelines
     
    This is a post that will explain all of our new guidelines for SDN scripts, these apply to existing scripts as well.

     

    If your script does not conform to these within one weeks time, it will be hidden until you have a chance to change it.
     
    Simplicity
     
    Users should be able to use your script without entering any game IDs, including object ids, item ids, npc ids, etc.
     
    You should instead stick to using names, as names are far more user friendly and understandable. Any user shouldn’t have to use a single one of our debugging tools to use your script.
     
    If you’re script uses rocks for mining (or something like that, where you actually need IDs), you’ll need to think of a better way of getting that data, such as:

    • Making a list of nearby rocks, that users can click and add (highlight them with the paint)
    • Adding a click-to-add system, so users can simply click objects to add them
    • Using the objects model IDs to separate them

    Clean GUI Design
     
    Make sure your GUI is well designed, clear to understand, and very simple to use.
     
    You should only use the default look and feel, and the default font.
     
    Also, use different background colors sparingly, and don’t use bright/neon colors.
     
    Examples of BAD GUI design:
     
    Overall good design, but terrible colors:
    b6c8b8ec51280d366e3e953698ddef66.png
     
    Window is too small, which makes it confusing:
    b9a1db179456505eec4f76401a4cbff3.png

     

    Alright design, but the window is too small for the top label, and the types should be easily readable (Lumbridge Trees vs LUMBRIDGE_TREES):
    247bc1754d977b6eb7e61e6c0a508703.png
     
    Examples of GOOD GUI design:
     
    A little small, but overall very simple and straightforward:
    5ec45dfb976189ba3c3de35c9d40c0a1.png
     
    Perfectly sized window (everything fits), list of NPCs instead of using ID’s OR names, and easy to use:
    564428b1da592e0df833d6465b3d4318.png
     
    Again small (same script writer), but simple and concise:
    c1e46305e0dc7a8c35af761917ed2a34.png
     
    Intuitive Script Settings
     
    Top scripts will read the environment and automatically decide (or select in a GUI) for your script’s settings.
     
    Here are a few great example of this:

    • An AIO woodcutter detecting the closest bank for the starting selection for bank location
    • An AIO cooker detecting what to cook based off of what raw food is in your inventory
    • Any script that eats food that detects what you’re eating based off the food in your inventory

    These can go on and on and on, whenever you’re making your script, you should ALWAYS think about the end user using your script. A script can never be too easy to use, and if it’s over complicated, many users will just get frustrated and end up not being satisfied.
     
    Thank you for reading, and I can’t wait to see all of our great scripts transform into something better.

     

    The Dream Team

    Link to comment
    Share on other sites

    Archived

    This topic is now archived and is closed to further replies.

    ×
    ×
    • 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.