Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
willin

purchasing the same premium script multiple times

Recommended Posts

Hello, i have been using Zulrah Slayer on 1 account for the past few weeks, I now have a 2nd account ready for zulrah, here's my question. curently its $14.99 for 1 instance for 14 days or $79.99 for 5 instances for 30 days. I'm wondering if i purchase the 1 instance twice will it allow me to run 2 insatnces or will it just give me 28 days for 1 instance?

Share this post


Link to post
Share on other sites
1 hour ago, willin said:

I'm wondering if i purchase the 1 instance twice will it allow me to run 2 insatnces or will it just give me 28 days for 1 instance?

If you purchase the 1 instance twice you will end up with 2 instances, and not 28 days for 1 instance 🙂

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
13 minutes ago, Buckets595 said:

Hows that script been treating you? Im thinking about getting it possibly. How many hours a day you run it and how much profit? If you don't mind me asking

the script is absolutely flawless, never had an issue with it,  i usually try and run it for atleast 12 hours a day split into two 6ish hour sessions without breaks, probably not the best idea i know but ive been using the script about a month so far with no issues, the gp/h varies between 1.5-3m an hour, 1.5m an hour without any rares but upto 3m/hr with rares, ive been making approximately 15-25m per day, and just now started running 2 accounts and in the process of training 3 more. i would definately recommend buying the script.

EDIT: just worked it out from my signature average just over 2m/hr over 288 hours on just one account.

Edited by willin
add info

Share this post


Link to post
Share on other sites
1 hour ago, Buckets595 said:

Hows that script been treating you? Im thinking about getting it possibly. How many hours a day you run it and how much profit? If you don't mind me asking

Get it and try it.

One thing I would just say is to keep in mind (as with any form of botting) is to be logical and not overdo it or you'll get burned pretty quick esp. w/ this script. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • This update features:

      Fixed broken hooks from today's update


      Fix wilderness level with RuneLite (Thanks @Todd)


      Add support for Kotlin .class files in scripts (Thanks @wastedbro)


      Overhaul Inventory API (Thanks @wastedbro)


      Add List support for common methods


      Change method grouping to make more sense (by functionality)


      Refactor methods to utilize Java 8 streams instead of cumbersome loops




      Recognize chatbox minimization (Thanks @JoeDezzy1)


      Fix Screen#isInViewport when NPC chat is open (Thanks @JoeDezzy1)


      Fix login bot bugs (Thanks @erickho123)


      Fix hint arrow return values (Thanks @Encoded)


      Fix depositAllExcept functionality (Thanks @wastedbro)


      Change containing box interface bound and adjust for Y values (Thanks @erickho123)
        • Like
      • 20 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Thanks
        • Like
      • 28 replies
    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
        • Like
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 68 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...