Jump to content
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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • This release will:

      Fix key event handling issue


      Fix other event handling issue


      Fix RSServer hook


      Update world hopper to have it use OCR, thanks to Todd


      Use proper disposal of old Graphics objects


      Reformat code


      Rearrange code


      Organize code imports


      Apply around 8000 automated code refactorings


      Make preparations for Java 9


      Fix 11 various bugs


      Add more reliable debugging support


      Fix mouseEntered/Exited event dispatching bug


      Fix minimap walking bug where it opens the map


      Fix broken hooks for today's game update
        • Thanks
        • Like
      • 55 replies
    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 27 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×