Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
CyberWizard

add sort by last update to repository

Recommended Posts

This would be a very bad idea, because any scripter can write an auto-updater that automatically submits the same source code every 24 hours (or any other interval).

Furthermore, even if this didn't open the gates for abuse, the script's last update time is not an accurate indicator of its quality. Anyone can update the same bad code as many times as they wish, and on the other hand there are certain scripts that haven't been updated in months because they are extremely robust and they are working perfectly even after dozens of game updates.

 

There are many other changes that can improve the repository, this is not one of them.

 

Share this post


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

This would be a very bad idea, because any scripter can write an auto-updater that automatically submits the same source code every 24 hours (or any other interval).

Furthermore, even if this didn't open the gates for abuse, the script's last update time is not an accurate indicator of its quality. Anyone can update the same bad code as many times as they wish, and on the other hand there are certain scripts that haven't been updated in months because they are extremely robust and they are working perfectly even after dozens of game updates.

 

There are many other changes that can improve the repository, this is not one of them.

 

If you don't like it don't use it, if people abuse it warn/punish them. It's a feature I'd love personally and I think some others would like. 

Share this post


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

If you don't like it don't use it, if people abuse it warn/punish them. It's a feature I'd love personally and I think some others would like. 

Me not liking the idea was not among the arguments I brought up, because it is not a valid argument.

Sorting scripts by the latest update date is a very dangerous idea that:

  • Will almost certainly result in abuse, with some scripters effectively "bumping" their scripts through auto-updaters
  • Deceive the users into believing that one script is better than the other one, based on its index
  • Tells absolutely nothing about the quality of the code submitted. Just because it was recently re-uploaded, it doesn't mean that it's better than the previous version, or other competing products.

 

I understand that this idea was based on the observation that active scripters that are frequently updating their scripts also have high quality scripts, but correlation doesn't imply causation. The said scripts are good not because they are being frequently updated, but because they are maintained by a good scripter that cares about his work, and also happens to update frequently.

In most cases, the last time a script was updated tells absolutely nothing about the script itself, and should not even be taken into account by the users. If there is anything that can be done about the "last update date", that would be removing it completely.

 

  • Like 1

Share this post


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

This would be a very bad idea, because any scripter can write an auto-updater that automatically submits the same source code every 24 hours (or any other interval).

Furthermore, even if this didn't open the gates for abuse, the script's last update time is not an accurate indicator of its quality. Anyone can update the same bad code as many times as they wish, and on the other hand there are certain scripts that haven't been updated in months because they are extremely robust and they are working perfectly even after dozens of game updates.

 

There are many other changes that can improve the repository, this is not one of them.

 

I agree

  • Like 1

Share this post


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

Me not liking the idea was not among the arguments I brought up, because it is not a valid argument.

Sorting scripts by the latest update date is a very dangerous idea that:

  • Will almost certainly result in abuse, with some scripters effectively "bumping" their scripts through auto-updaters
  • Deceive the users into believing that one script is better than the other one, based on its index
  • Tells absolutely nothing about the quality of the code submitted. Just because it was recently re-uploaded, it doesn't mean that it's better than the previous version, or other competing products.

 

I understand that this idea was based on the observation that active scripters that are frequently updating their scripts also have high quality scripts, but correlation doesn't imply causation. The said scripts are good not because they are being frequently updated, but because they are maintained by a good scripter that cares about his work, and also happens to update frequently.

In most cases, the last time a script was updated tells absolutely nothing about the script itself, and should not even be taken into account by the users. If there is anything that can be done about the "last update date", that would be removing it completely.

 

This.

  • Like 1

Share this post


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

I'm not opposed to having this as an option as long as it is not the default sorting option.

This. When I just came here and was looking around for scripts I bumped into loads of outdated scripts. On the first rows of the repository without using any filter/sort function there are still some really outdated scripts which don't even work. 

Edited by angelheartz

Share this post


Link to post
Share on other sites
12 hours ago, Encoded said:

I'm not opposed to having this as an option as long as it is not the default sorting option.

^ This .

When i search for scripts i do check the freshness and assess the quality through trials.

So if you are saying that people would abuse this by bumping their script, honestly if you choose a script based on the latest then you are retarded.

If you look in the repo you would find scripts not updated for 1-2 years and they don't function fully.

The game is always evolving and some of the script writers on tribot do not update their scripts to support the latest methods.

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
Sign in to follow this  

  • Our picks

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

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
        • Like
      • 21 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×