Jump to content
Sign in to follow this  
TRiLeZ

TRiBot Repository Version 2.0

Recommended Posts

TRiBot Repository Version 2.0
 
Today marks the release of the TRiBot Repository Version 2.0. I have spent countless hours working on the TRiBot Repository to make it the best it can be. It has many new functionalities which will be useful for both users and scripters.
 
More Script Info
Clicking the title of scripts within their tiles will now show a list of details about the script.
 
User Count
The default sorting method for scripts is now their user count. User counts are calculated on a daily basis.
 
New Navigation Bar
The navigation bar has been improved both by aesthetics and functionality.
 
AES Script Encryption
The TRiBot Repository now uses US military grade encryption when storing scripts. This is on top of the Allatori class obfuscation. Scripters will have to worry less about people cracking their script.
 
Premium Scripts
Scripters are now able to sell their scripts via the TRiBot Repository. They can either sell for a one-time fee, a monthly fee, or auth/instancing based.
 
Credits
In order for users to purchase premium scripts, they must first purchase credits. This can be easily done through the User Panel within the TRiBot Repository. Credits will make it easy for users to purchase scripts, and for scripters to refund users if they need to.
 
Automated Script Submission Queue
Scripts submissions are now automatically handled. No more waiting on a Repository Admin to approve your request. The wait time for approval is about 10 minutes.
 
No More Third-Party Script Loaders

Now that the TRiBot Repository is now able to handle payments for scripts, we are going to eliminate third-party script loaders. This is being done for a number of reasons:

  1. Any downtime for third-party script loaders creates a bad image for TRiBot. Users are prone to blame TRiBot itself for the downtime, even though TRiBot is not affiliated with the third-party.
  2. To create a universal source for scripts. Users don't want to spend time installing multiple script loaders and having to handle multiple auth codes. With the TRiBot Repository, they just have to find the script they want, purchase/activate it, and it's available for them to use with TRiBot. It's just that easy!
  3. The TRiBot Repository is more secure. All scripts are encrypted with AES on top of Allatori obfuscation. Additional methods are also used to prevent users from ever getting their hands on a separate copy of the script.
  4. Disputes between users and scripters can be more easily handled. Administrators have the ability to reverse payments for scripts whenever they see fit.

We are giving users and scripters until Friday October 4 (inclusive) to switch over from loaders to the TRiBot Repository. To make this transition as seamless as possible, the TRiBot Repository has some tools to import a list of auths or a list of users which should be granted access to their premium scripts. Scripters: please check the Scripters forum for more information about this.

 

Happy Botting!

-TRiLeZ

  • Like 1

Share this post


Link to post
Share on other sites

Could you provide details on how the payments will work? Also it'd be awesome to see mobile payments :)

 

The user has to purchase 'Credits' to be able to purchase scripts. Currently, the only way to attain these Credits is via PayPal. However, we are looking for more ways for users to pay - such as but not limited to rsgp.

 

With these Credits, users can purchase any script they want (given they have enough Credits for the script). The script publisher will be able to see the purchase logs from within the Scripter Panel and will also be able to refund the transactions if they wish.

Share this post


Link to post
Share on other sites

The user has to purchase 'Credits' to be able to purchase scripts. Currently, the only way to attain these Credits is via PayPal. However, we are looking for more ways for users to pay - such as but not limited to rsgp.

 

With these Credits, users can purchase any script they want (given they have enough Credits for the script). The script publisher will be able to see the purchase logs from within the Scripter Panel and will also be able to refund the transactions if they wish.

 

Do scripters then get paid in credits which they'll need to cash out, or do they automatically get paid $?

Share this post


Link to post
Share on other sites

Do scripters then get paid in credits which they'll need to cash out, or do they automatically get paid $?

 

After each purchase transaction, the publisher will get their 70% share. Then they need to wait until the payout period to get the money in dollars.

Share this post


Link to post
Share on other sites

 

Will there be an automatic auth licensing system?

Like someone buys the script and its instantly in their repository. 

Or do I have to make an auth for everyone?

 

 

 

It is fully automatic, once they buy credits.. they buy your script and the credits get transferred to your account and they get licensed to use your script for whatever you have set the script to sell for.

 

Example,

You are selling for 6 credits each, 2 instances, and on a monthly subscription.

 

They pay you 6 credits, ($6.00), they can run two instances of your script, and it will automatically be removed one month from the purchase date.

Share this post


Link to post
Share on other sites

Will there be a way for us buy using rsgp? like a voucher system for scripts.

 

Say someone wants to buy USA Merchanter's script. It is 10 credits (10$) And i'll buy the 10 credits and then  Either 1. Send him the 10 credits or 2. give him a voucher for the 10 credits

 

Would that work?

Share this post


Link to post
Share on other sites

Will there be a way for us buy using rsgp? like a voucher system for scripts.

 

Say someone wants to buy USA Merchanter's script. It is 10 credits (10$) And i'll buy the 10 credits and then  Either 1. Send him the 10 credits or 2. give him a voucher for the 10 credits

 

Would that work?

 

Yes, they've stated that they're looking in to other methods like RSGP for credits. 

Share this post


Link to post
Share on other sites

Yes, they've stated that they're looking in to other methods like RSGP for credits. 

 

Great. Would this be site based or user based? Like would they need someone like me to sell for 07 gp or would a user pay like a moderator/admin in 07gp like they do for verified VIP resellers?

Share this post


Link to post
Share on other sites

 

 

It is fully automatic, once they buy credits.. they buy your script and the credits get transferred to your account and they get licensed to use your script for whatever you have set the script to sell for.

 

Example,

You are selling for 6 credits each, 2 instances, and on a monthly subscription.

 

They pay you 6 credits, ($6.00), they can run two instances of your script, and it will automatically be removed one month from the purchase date.

 

Okay that doesn't sound too bad :), the only thing I'm concerned about the monthly payments. Scripting is my main source of income and I pretty much rely on weekly payments. Paypal already takes about a week to send the money to your bank account.

Also whats the difference between One Payment and Auth Based, and can we use both ?

Share this post


Link to post
Share on other sites

   

Okay that doesn't sound too bad :), the only thing I'm concerned about the monthly payments. Scripting is my main source of income and I pretty much rely on weekly payments. Paypal already takes about a week to send the money to your bank account.

Also whats the difference between One Payment and Auth Based, and can we use both ?

 

We could have payments more frequent than monthly. In the future, we will also have an option to have the money wire-transferred straight into your bank account. Wire transfers usually take about 3 business days to complete.

 

The "One Payment" option is the life-time payment option. Users pay once and they get unlimited access to the script.

"Auth Based" means users have to buy individual auths according to how many instances they want to run. Script publishers control how many instances are given per auth.

Share this post


Link to post
Share on other sites

We could have payments more frequent than monthly. In the future, we will also have an option to have the money wire-transferred straight into your bank account. Wire transfers usually take about 3 business days to complete.

 

The "One Payment" option is the life-time payment option. Users pay once and they get unlimited access to the script.

"Auth Based" means users have to buy individual auths according to how many instances they want to run. Script publishers control how many instances are given per auth.

 

Okay cool, also one more question. I can issue auths without people purchasing the script right? So I can give friends auths and use my own scripts without purchasing them aye ( not locally :P )

Share this post


Link to post
Share on other sites

Okay cool, also one more question. I can issue auths without people purchasing the script right? So I can give friends auths and use my own scripts without purchasing them aye ( not locally :P )

 

Well, with the current conversion tools that is possible. However, these tools will be removed after the conversion is complete. If you want your friends to be able to run your scripts, they'll have to either run them locally or with the "Online Jar Loading" in the scripts settings.

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:

      Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 27 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 38 replies
    • This release includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
      • 33 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
      • 25 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
      • 30 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×