StuxGeek's Development Thread

Discussion in 'Projects' started by StuxGeek, Nov 11, 2015.

  1. In this thread I'll be posting all my bots with a detailed explanation on the bot. This thread will also contain future updates per bot and will also give updates on what changed in each version. I'll be using the thread to provide a structured view on all the bots. Links to the bot store will be added as soon as the bot is pushed to the store.

    Finished:
    • none
    Work In Progress:
    • StuxBronzeMiner: This bot is designed to run between Varrock east bank and Varrock east mine. The bot will mine 14 tin ores and 14 copper ores. The amount of copper ore may differ because of the random gems you get while mining.
      Plans: Adding support for multiple locations and adding a paint to follow the progress of the bot.
      Issues: Added paint but it doesn't show up message given --> [Notice] blocked access to openGL display mode
      Status: Bot works as I had imagined and is waiting approval to the bot store
      LINK: StuxBronzeMiner

    • StuxBronzeSmelter: This bot will smelt tin and copper into bronze bars
      Plans: Adding support for multiple locations and adding a paint to follow the progress of the bot.
      Issues: Added paint but it doesn't show up message given --> [Notice] blocked access to openGL display mode
      Status: Bot roughly works still need to tweak it.
      LINK: StuxBronzeSmelter
    Future Plans
    • StuxBronzeSmither: This bot will smith all the acquired bars into armour
    This thread is not finished yet. This thread will be updated continuously
    Whenever you've got an idea that you might want me to work out, just PM me and we'll talk about it.
     
    #1 StuxGeek, Nov 11, 2015
    Last edited: Nov 14, 2015
  2. Dutch people be taking over RM.



    Client-based autoclicker would be nice;)
     
  3. Hmm not a bad idea... :D
     
  4. Tell me more about your idea please, here or in PM. Your choice :p
     
  5. Basically an autoclicker you can use with RM, so that you can minimize the rs window without fucking up.
     
  6. For things like alching?
     
  7. I'd say universal stuff due to the fact that autoclicking can be used for various purposes.
     
  8. Yeah ofcourse but alching is the only thing I know of :p
     
  9. Alching, ivy and a couple events where you can autoclick af.
     
  10. Ah I see.
     
  11. Not allowed, it defeats the entire purpose of having bots. If something is as easy that it can be done by an autoclicker, it's also relatively easy to write a bot WITH antiban for it.
     
  12. I wouldn't say its not allowed but i do get your point @Bertrand .
    But, i also understand @Insomniac ... lets say there is something which is perfectly autoclickable, and there is not yet a bot for it... then the user will need to get through the hassle of requesting that bot, waiting for it... and by the time the bot would be released the activity can either be patched to not be autoclickable or the activity will be gone :)
    An autoclicker or a mouse recorder can be a good addition to Runemate. < my oppnion
     
    Insomniac likes this.
  13. Autoclicker with different intervals?
     
  14. Exactly what I was thinking, I shouldn't take more than an hour to get a bot roughly ready to do an auto-clickable task.
     
    Derk likes this.
  15. If we upload such a bot it gets declined. It's not allowed.

    Just as bad. :/
     
  16. Fk... autoalcher with an autoclicker implemented? Antiban with chatting options like "im high i cant talk rite now ayy lmao."
     
  17. Really? @Cloud @Arbiter
     
  18. @Bertrand is right. Such a highly detectable bot won't be allowed on the Bot Store. In fact it may get auto-rejected due to use of unpublishable API methods.


    Sent from my iPhone using Tapatalk
     
    Derk likes this.
  19. Looks like the case has been solved. thanks @Arbiter
     

Share This Page

Loading...