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

Compensation for Downtime

Recommended Posts

Compensation for the downtime over the past few days as well as the downtime earlier this year has been applied to all current VIP(E) members and members whose VIP(E) expired during the downtime earlier this year. The extension was one month.

  • Like 12

Share this post


Link to post
Share on other sites
1 minute ago, Todd said:

Hey guys if you still haven't received your compensation please fill out this form. Note: This does NOT include users that are seeking compensation for premium scripts. This is ONLY vip/vipe compensation.

https://docs.google.com/forms/d/e/1FAIpQLSfbdRsOQmk4kQtN6NhX9WOb4p2elfkMYH-CSWWPFmtXx6AEtw/viewform

Hey will you be compensating for premium scripts in the future? 

Share this post


Link to post
Share on other sites
Just now, mayhs said:

Hey will you be compensating for premium scripts in the future? 

That's a complicated issue. Sadly, there is no really happy compromise here. We will gladly take the hit to compensate you for our downtime but we can't force our burdens on the scripters. If we extended the subscriptions it would hurt them, many of which rely on tribot to pay for basic things. Looking forward as developers we are securing a way to ensure that this doesn't happen again. That subscriptions are paused and that nobody loses any days during period that the bot is down. This is all coming soon in the future.

We're leaving it up to the scripters to manage whether or not they want to compensate for the time. I think in the right circumstances they will gladly refund you. However, I'm certainly not forcing them to do it. In the end, how they manage customers is up to them.

I wish I had a better answer for you. Our infrastructure at the moment was not built with down times in mind. Which is why compensation even for VIP and VIPE is so complicated. Compensating premium scripts is another level of impossible at the moment. This was the longest down time in the 7 years of TRibot history and we don't plan on it happening ever again.
 

  • Like 4

Share this post


Link to post
Share on other sites
1 minute ago, Todd said:

That's a complicated issue. Sadly, there is no really happy compromise here. We will gladly take the hit to compensate you for our downtime but we can't force our burdens on the scripters. If we extended the subscriptions it would hurt them, many of which rely on tribot to pay for basic things. Looking forward as developers we are securing a way to ensure that this doesn't happen again. That subscriptions are paused and that nobody loses any days during period that the bot is down. This is all coming soon in the future.

We're leaving it up to the scripters to manage whether or not they want to compensate for the time. I think in the right circumstances they will gladly refund you. However, I'm certainly not forcing them to do it. In the end, how they manage customers is up to them.

I wish I had a better answer for you. Our infrastructure at the moment was not built with down times in mind. Which is why compensation even for VIP and VIPE is so complicated. Compensating premium scripts is another level of impossible at the moment. This was the longest down time in the 7 years of TRibot history and we don't plan on it happening ever again.
 

Okay no problem thanks. 

Share this post


Link to post
Share on other sites
3 hours ago, Todd said:

That's a complicated issue. Sadly, there is no really happy compromise here. We will gladly take the hit to compensate you for our downtime but we can't force our burdens on the scripters. If we extended the subscriptions it would hurt them, many of which rely on tribot to pay for basic things. Looking forward as developers we are securing a way to ensure that this doesn't happen again. That subscriptions are paused and that nobody loses any days during period that the bot is down. This is all coming soon in the future.

We're leaving it up to the scripters to manage whether or not they want to compensate for the time. I think in the right circumstances they will gladly refund you. However, I'm certainly not forcing them to do it. In the end, how they manage customers is up to them.

I wish I had a better answer for you. Our infrastructure at the moment was not built with down times in mind. Which is why compensation even for VIP and VIPE is so complicated. Compensating premium scripts is another level of impossible at the moment. This was the longest down time in the 7 years of TRibot history and we don't plan on it happening ever again.
 

Im filling out the doc, where can I see payment history for VIP? All i have is my script history. I bought vip the same day as my hunter script so.

@Todd

Edited by roklobster315

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 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
      • 61 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
    • This release will:

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



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

    No registered users viewing this page.

×
×
  • Create New...