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

When a premium script doesn't get updated

Recommended Posts

Now that we're doing weekly/monthly payments for these premium scripts, are there anything keeping the scripters in check in terms updating their scripts in a timely manner? Back then, it didn't really matter since it was lifetime and we'd just wait patiently for the scripter to update the scripts but what do we have going for us as users? Is there any way we can give the privilege to scripters to extend auths for x amount of days that their script is down? If not, why not? Atm it seems the mentality is "don't sub for another month if you don't like the scripter, you have the freedom to choose hur-dur."

Yes we can avoid the scripter in the future but most skills have only one particular scripter that's dominating with no other competition and this has been the case for couple years now. Aside from woodchopping and fishing, all the other skills have pretty much one premium scripter in that category with no competition so we don't really have that "freedom" to make the scripter feel the urgency of updating or even improving their scripts. 

Maybe if the Premium scripters are willing to come out of their comfort zone and compete against other pre-established category of skills, this monthly payment switch that was SUPPOSE to incite competition therefore bringing out improvements. However, there isn't really a competition and the only premium scripter that seemed to be fueled to bring about innovation and energy was @Einstein.

I think the simplest solution would be for @TRiLeZ to allow premium scripters to extend auths x amount of days of downtime. Don't allow them to extend for individual users if you're worried about abuse on their end but maybe allowing them to extend for all their users at once for x amount of days?  

From a user's perspective, it feels like we're getting milked and don't think it's out of reach to request for: at the very least, allow scripters to extend their users' auths for x-amount of days for downtime.  

I do like all the client updates that's been rolling out but that's what we pay VIP monthly for and which isn't something new. What I'm ranting about is the users/scripters dynamic. I understand that most premium scripters have other things in life and that keeping their scripts up to date promptly isn't a realistic expectation. However, with that said, what's the harm in allow extension of auth to compensate for these downtimes? 

 

TLDR; allow scripters to extend auths for downtime of their scripts. Perhaps allow users to flag the thread of the script in some way to gain attention of global mod/admins and freeze the auths? 

Thank y'all for taking the time to read my rant if you read this far. Have a great day!

  • Like 6
  • thonking 1

Share this post


Link to post
Share on other sites

Although I fix any problems in my scripts rather quickly, I would definitely like the ability to extend all auths for a period of days whenever something major happens (additionally in cases where a client bug causes tribot to stop working for a few days).

If you don't like a specific script that has no other alternatives, then say something and I'm sure someone may be interested in making one.

Edited by Naton
  • Like 1

Share this post


Link to post
Share on other sites

Agreed. Both with refunding days for downtime for critical bugs. But also feel like Premium scripts should be scrutinized a bit more when it comes to adding new features/updating less than optimal features. 

We got a lot of premium scripts, as you say, monopolizing a specific mini-game or a specific skill, while not having been really updated or changed in years. You'll notice this if you browse through every premium script category, and looking at the most used scripts, and then looking at the last 5 pages of their thread. Some of them just post after post of people saying "This thing is slightly bugged" or "You should really add X because of Y", long in-detail posts, with no fixes or replies from the author.

Sometimes you get the feeling that some premium scripters just churn out as many premium scripts as possible, and then don't maintain them to the standard you'd hope to find on Tribot. Quality > Quantity

Share this post


Link to post
Share on other sites
6 hours ago, Underpaw said:

@OptimusThis applies to you. You said you would fix the Yak fighter script but you haven't done anything... you're the most inconsistent script writer of all time.

Did you read his post? 

22 hours ago, MuleTraveler said:

TLDR; allow scripters to extend auths for downtime of their scripts. Perhaps allow users to flag the thread of the script in some way to gain attention of global mod/admins and freeze the auths? 

Thank y'all for taking the time to read my rant if you read this far. Have a great day!

My yak fighting script is working great, still have happy customers and there is little to no downtime. You've been asking for a new feature that isn't advertised on the thread, and I will do it when I have time. 

Share this post


Link to post
Share on other sites
On 11/4/2018 at 12:00 PM, Optimus said:

Did you read his post? 

My yak fighting script is working great, still have happy customers and there is little to no downtime. You've been asking for a new feature that isn't advertised on the thread, and I will do it when I have time. 

you've also blown off my posts about your puro puro script (2 days now, although i've known u to wait weeks to finally reply based of previous interactions), the bot has difficulties with properly logging back in. Gyazos supplied for reference, babysat them for about 5 hours so far. sidenote: still has potential to be literally the best imp scripts out rn,... i used one over on osbot out of impatience... i have aids now.

 

Edited by switchonline

Share this post


Link to post
Share on other sites
On 11/4/2018 at 7:00 PM, Optimus said:

Did you read his post? 

My yak fighting script is working great, still have happy customers and there is little to no downtime. You've been asking for a new feature that isn't advertised on the thread, and I will do it when I have time. 

Wtf? Do you even read my other post about fixing the ammo detection for darts? You know, the issue which caused my character to box for 2 hours...

Also, the camera issue is NOT A NEW FEATURE. It's something that needs get fixed. You really need to get consistent.

  • Sad 1

Share this post


Link to post
Share on other sites

Hey guys, this wasn't a thread intended to flame Optimus but since the ship's already sailed, @Optimus your tp+alch has been down for at least a year 😕

Edit: But to his defense, I still liked using his script with everything else regardless!

Edited by MuleTraveler
  • Sad 1
  • thonking 1

Share this post


Link to post
Share on other sites
On 11/4/2018 at 6:00 PM, Optimus said:

Did you read his post? 

My yak fighting script is working great, still have happy customers and there is little to no downtime. You've been asking for a new feature that isn't advertised on the thread, and I will do it when I have time. 


Stun + alch hasn't worked on your combat script for a while though and you have given 0 updates about it.

Share this post


Link to post
Share on other sites
16 hours ago, ConnorM said:


Stun + alch hasn't worked on your combat script for a while though and you have given 0 updates about it.

On 11/6/2018 at 7:03 PM, MuleTraveler said:

Hey guys, this wasn't a thread intended to flame Optimus but since the ship's already sailed, @Optimus your tp+alch has been down for at least a year 😕

Edit: But to his defense, I still liked using his script with everything else regardless!

Just tested and both are working perfectly. Sounds like you're setting it up wrong.

ezgif-4-339829e6adda.gif

ezgif-4-13a5cb3b1b82.gif

Share this post


Link to post
Share on other sites
21 minutes ago, MuleTraveler said:

Well, unless you had a major GUI change, I've been using it perfectly fine in the past so I know it wasn't my set up😕

Please show me your gui settings, haven't updated the script in the past 2 weeks as it's been working perfect ^_^

Share this post


Link to post
Share on other sites
On 11/6/2018 at 12:03 AM, MuleTraveler said:

Hey guys, this wasn't a thread intended to flame Optimus but since the ship's already sailed, @Optimus your tp+alch has been down for at least a year 😕

Edit: But to his defense, I still liked using his script with everything else regardless!

 

42 minutes ago, Optimus said:

Please show me your gui settings, haven't updated the script in the past 2 weeks as it's been working perfect ^_^

It may be working now but i was talking about the past year. I'm maxed out combat so I haven't used your script in a while. 

Share this post


Link to post
Share on other sites
On 11/3/2018 at 9:16 PM, MuleTraveler said:

the only premium scripter that seemed (...) to bring energy was @Einstein.

Energy = mass × (speed of light) ²

 

In regards to your concerns for the lack of competition: yes, the repository won't change overnight, but it is happening, slowly but steadily. New scripts have been released and the already existing ones are being re-written. One of the reasons for this delay is the fact that software development is very time consuming, and most of us either have full time jobs, are in school, or both at the same time.

But if you were to take a "screenshot" of the repository from February, when the lifetime changes have just been announced, and compare it to the repository we have today, you will observe that it's vastly improved. At least 20 scripts have either been released or re-written.

Competition exists, and although at a slow pace, general improvement will continue to happen. This is an undeniable fact.

 

In regards to your suggestion for offering scripters the ability to extend the duration for their own scripts: It's a very good idea, granted that they use it to extend the days in which the script was dysfunctional due to their own bugs (not caused by client downtime, RuneScape downtime, or any other objective factor).

But more importantly than extending the duration due to script downtime, is fixing the bug in a timely manner, so the downtime doesn't occur at all.

 

Lastly, I really appreciate the kind words, but if you think that I was the only scripter that was fueled to bring innovation and energy, you haven't seen @Naton's work.😉

 

  • Like 1
  • Thanks 2

Share this post


Link to post
Share on other sites

Completely agree with this and i'm glad to see the script developers agree as well as this is a win-win situation, with less stress on premium scripters fixing the problem and customers concerned about losing script availability. Noticed it myself when i bought a premium script for the first time and the client + LG was down immediately after for a few days.. That hurt my soul a bit. An addition to this would be if we were also reimbursed vip for the client downtimes 🙄 just putting it out there :D 

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)
      • 148 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.
      • 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.
      • 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
      • 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
      • 68 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...