Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
MSO

Leespiker private script dispute

Recommended Posts

Agreements aren't necessarily limited to the Scripter's terms of service in the thread, they are what you two agree upon during finalizing the deal. My suggestion to you is to outline those in a more finite structure next time so it is easy to refer back to them when you feel you are being wronged.

If you have issues in the future and you feel like he is being unresponsive, you can use this subforum to get a second opinion. That is what it is here for.

Same instructions apply, @Leespiker let me know when this is resolved.

Share this post


Link to post
Share on other sites

You've just acknowledged that he made an agreement, an expectation, for how often updates will come, @Usa. Since @Leespiker said nothing in Skype that contradicted anything from his ToS, this actually helps my case - especially since no one has bothered to pull up his old thread to see what he promised. Here are a couple of screenshots of our conversation about updates: 1st and 2nd. It's ironic that he has parts outlined to prevent people from making him wait, a 2-month limit at that, but that wasn't what I wanted to address. The part I wanted to address was, "Normally I can fix bugs one at a time quickly." Now we're talking about a handful of bugs here, about 4+, but let's focus on the 2 bugs he supposedly fixed after this dispute was posted. I don't think an 8-month delay can be described as 'fixing bugs quickly', so right there he breaks his own agreement. He breaks this agreement multiple times, and I've already posted proof of it. If you're going to argue that he said "normally", he's been dodging bugs and disappearing for weeks, months, since day-one, so that's all that constitutes as 'normal' behavior. 

I'm not sure if you're trying to defend @Leespiker yourself, but that's what it's coming across as. He didn't even lift a finger to protect himself, and he still got away with murder. Speaking of which, I'm actually surprised by how many people came to his defense considering how inactive he is and how even his public scripts are reportedly in shambles, without updates for months or years also. You couldn't have been more blatant turning a blind eye.

Edited by MSO

Share this post


Link to post
Share on other sites

The case is, if you report these items sooner it will work more in your favor. This is your first report, the main issue you are having is that he did not make the necessary changes. Your dispute has brought attention to that aspect and it resulted in him making the required changes. The dispute has been resolved.

Should this occur again, this thread will be taken into account and depending on the issue can result in a similar or different outcome.

Share this post


Link to post
Share on other sites
57 minutes ago, Usa said:

The case is, if you report these items sooner it will work more in your favor. This is your first report, the main issue you are having is that he did not make the necessary changes. Your dispute has brought attention to that aspect and it resulted in him making the required changes. The dispute has been resolved.

Should this occur again, this thread will be taken into account and depending on the issue can result in a similar or different outcome.

That isn't sound logic. If I started a dispute of inactivity because a scripter was gone for a few hours, then the dispute wouldn't be taken seriously. Unless you have an alternative and optimal time-frame for disputing inactivity, then I don't see how that could work.

My main issue was only 'brought to attention' after I had to bring it up multiple times - you would have not acknowledged it otherwise - which was scripter inactivity. The only thing @Leespiker did as a result of this dispute was update the script, which does not resolve my issue - only the symptom of my issue. If you appreciate analogies: if I have a life-threatening illness that causes rashes and I only treat the rashes, not only will I get the rashes back after time but I will still be stuck with the illness. 

Share this post


Link to post
Share on other sites
2 hours ago, MSO said:

That isn't sound logic. If I started a dispute of inactivity because a scripter was gone for a few hours, then the dispute wouldn't be taken seriously. Unless you have an alternative and optimal time-frame for disputing inactivity, then I don't see how that could work.

My main issue was only 'brought to attention' after I had to bring it up multiple times - you would have not acknowledged it otherwise - which was scripter inactivity. The only thing @Leespiker did as a result of this dispute was update the script, which does not resolve my issue - only the symptom of my issue. If you appreciate analogies: if I have a life-threatening illness that causes rashes and I only treat the rashes, not only will I get the rashes back after time but I will still be stuck with the illness. 

While a few hours is clearly an exaggeration, a few weeks is not. In your case, you stated this has been an issue for eight months; you had ample time to present a case. How these things work is you present an issue with a Script and we attempt to get the Scripter to resolve those issues in a timely fashion. If analogies paint a better picture for you, imagine starting with a small rash and instead of going into the doctors for a simple ointment, you instead wait eight months and it develops into full-body Psoriasis.

It is your responsibility to alert us via this subforum when you feel you have reached a point in your relationship with the Scripter that requires outside intervention.

Keeping a prolonged discussion over months and months and then expecting that you will be awarded a full refund on your first report isn't ideal, that is always a last resort as you paid and have been using a product for some time and the best resolution is to return the product to you in the order it was promised upon your payment.

The script has been updated, this matter has been resolved. Should you experience issues in the future, please use this subforum and we will be happy to help.

Share this post


Link to post
Share on other sites
On 11/9/2016 at 4:19 PM, Leespiker said:

I am working with @MSO tonight to make the transaction go completely through the repository. We have already been working on fixes for the script.

Thank you for the update, hopefully this is the last case from your past transactions. Let me know when it is complete.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Our picks

    • Hello everyone,

      Last week we tried to roll out Auth0 Login, but we lost that battle. Now it's time to win the war!

      Important changes

      When logging into the client, you'll now have to enter your Auth0 account credentials instead of your forums credentials

      Note: 2FA is still handled through your forums account (for the time being)



      Changes for existing users

      You'll have to link your Auth0 account to your forums account here: https://tribot.org/forums/settings/login/?service=11


      Auth0 accounts have been created for most existing users. Please use your forums email address and password to login.



      Important notes

      Make sure to verify your email address upon creating a new Auth0 account


      When we mention your Auth0 account, we mean your account used for auth.tribot.org as displayed below
      • 62 replies
    • To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.

      All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.

      What does this mean for users?

      Your account credentials are now even more securely stored


      You'll be able to login via Facebook, Google, and others in the future


      Is there anything users have to do differently now?

      Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account


      New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account


      Why was this change made?

      The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins


      To centralize all user accounts in one area


      To ensure that the client login doesn't go down when the forums are having problems


      To speed up our development


      Other considerations

      There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out


      We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)


      It's not possible to change email addresses for the time being (this will be resolved this August)


      Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page
        • Like
      • 11 replies
    • Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.

      Today we are going to share what we've been working on!


      Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.

      We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.

      Thank you all for being patient. I hope everyone is excited as much as I am!
        • Like
      • 17 replies
    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 50 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 86 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...