Jump to content

Recommended Posts

First of all, if you haven’t seen TRiLeZ’s post, please go read that first before continuing. 

Company
My new position at TRiBot will be President and CEO. @Nullable will be Vice President of Engineering. We will be the only two paid staff members until the transition of ownership is complete and we have a good grasp of TRiBot’s financials. Our current plans do not involve the hiring of any new staff, but we are not opposed to new hires in the future. I will be transitioning to full time by the end of this month and Nullable will continue to be part time as he has a full time position outside of TRiBot. My focus will be on every aspect of TRiBot’s operations which includes but is not limited to development, customer support, and administration. Nullable will be mainly concerned with the development of TRiBot while still having the ability to assist in administrative tasks as well as customer support.

TRiBot X
TRiBot X has been postponed indefinitely. Nullable and I both feel that there are many other areas of TRiBot that we need to improve upon and while the current bot client isn’t perfect, a new client doesn’t solve many issues customers are facing and it potentially introduces new bugs and we don’t want to have another TRiBot 11 fiasco. TRiBot X needs to be as good as TRiBot 12, if not better, and it is a long way from that currently. With that being said, TRiBot X will continue to be developed by TRiLeZ at his leisure.

TRiBot 12
One of our first projects is going to be a new loader for TRiBot 12. The current loader has many issues and often straight up doesn’t work with no signs of what went wrong. We plan on introducing a new self updating loader that will be more in line with the TRiBot 10 loader. We will continue to develop TRiBot 12 and we have some updates in the works that we believe will fix some of the issues users have been having. We’re also looking into how we can update the scripting API and include services such as Dax Walker directly into the client.

TRiBot Mobile
TRiBot Mobile will be released as a standalone client and no longer bundled with TRiBot X. This is mostly Nullable’s domain and he will make an announcement with more information on TRiBot Mobile when it is closer to launch. TRiBot Mobile is low on the development priority, but it still exists and will be released in due time.

TRiBot Store
Many customers and scripters are unhappy with the store and we are also financially unhappy with it as well. While we currently are not moving away from the new store, we will be making changes to the store to reduce its cost and these changes will be announced when they are made. We will not be increasing any prices and any script pricing changes will be at the request of the scripter, not TRiBot.

Free Scripts
You may remember the announcement of discontinuing free scripts when the new store was released. This will not be the case. Free scripts will be overhauled slightly, but they are not going away. We will have more information on this when we get closer to making these changes.

TRiBot Repository
Our main development focus is to rewrite the repository and the rest of TRiBot’s server sided backend. This will fix bugs like ghost instances, bring back features like the bot panel, and allow us to implement a new store that isn’t reliant on shopify if we choose to do so. Our current repository is very dated and hasn’t received any updates in years. This was supposed to be done with the new store release, but the store ended up being released separately. 

TRiBot Forums
The forums are mostly a ghost town now ever since the introduction of Discord and scripts no longer having links to their support threads. I’d like to revive the forums if possible, but I’m not sure of how to do that at this time so if you have any suggestions, please let us know.


If there is anything I did not address that you would like to discuss, feel free to reach out to myself or Nullable. We will be happy to answer any questions you might have or provide more clarity on what is discussed in this post.

Happy Botting!
 

  • Like 17
  • Thanks 2
Link to post
Share on other sites
  • Encoded featured this topic

Damn this is really exciting for the future of tribot and I can't recall the last time I've ever said that.

Seemed like unexplained update after update that degrades the user experience, but I'm exited for the new era of TRiBot, been excited since wasted showed me his progress with mobile.

 

Good luck and congratulations 😃

  • Like 1
Link to post
Share on other sites

Here are some suggestions:

1. Ditch any costly licenses and replace them. HelpDesk, Auth0, Shopify, Invision, LightHTTP. I'm sure there is more.
2. Drop AWS or at least scale back the complications of the hosting. I know TRiBot used to run fine on a dedicated machine. I'm unsure of the amount of traffic you all get any more but a simple 3 tier architecture would probably be sufficient. We run an efficient site that gets 1 million average users daily and currently has half the infrastructure in AWS that I remember TRIBot implementing.
3. Ditch the forums more or less, or move to something that somebody else hosts.
4. Re-code the back-end with something fast and make sure you implement everything as micro-services so it's cost effectual to scale. We recently started using NATS messaging, cloud-events, hexagonal architecture and Kubernetes and development is super fast.

Good luck @Encoded and @Nullable. Let me know if you ever need any help.

  • Like 9
  • Thanks 3
Link to post
Share on other sites

The store pricing I think is the biggest deal for me, with how expensive things have got, it's completely destroyed my will to experiment with bot scripts, and my ability to farm en mass. There needs to be a significant reduction in costs for end-users, in my opinion, by a roughly 50% margin. Even if that means throw away the reward system, who cares, just drive the script price down, please. A lot of us know the store needs another near complete overhaul, with how spaghetti it functions, so any improvements here, are appreciated.

 

Thank fuck you're keeping free scripts, it is a terrible idea to remove them.

 

Good idea that you want to fix the client. It's good for what it is, but there's a bunch of spaghetti around what's going on with stuff, and just stream-lining Tribot to update itself, and work reliably, would be great. Also, a focus on reducing CPU usage is always appreciated. Overall, still miles ahead of other clients though.

 

Reviving the forums would be nice, give people more to talk about than just botting, off-topic sections,

 

 

Maybe something Tribot executives should consider to bring in new users, and bring up profits, is "sponsor" premium scripters like Einstein, Naton, Dentist, Aropupu, LAN, etc, to create premium scripts for Tribot. Example: Executives give a scripter $200 USD, and the scripter is to develop a certain type of script Tribot needs, at a price both parties agree on, and will maintain it for minimum X years. Or give bonuses to scripters where for the first X months after a premium script is released, no profits are given to Tribot, and all to the scripter. I am not into scripting myself, but I definitely think there needs to be more incentive for scripters a bit, that is not increasing the prices for end-users, as I think end-users are already paying too much. I just think current Tribot pricing is not competitive for what's offered, although what offered, to be clear, is still the superior product to the alternatives.

  • Like 1
  • Thanks 1
Link to post
Share on other sites
On 3/15/2021 at 8:34 AM, CyberWizard said:

The store pricing I think is the biggest deal for me, with how expensive things have got, it's completely destroyed my will to experiment with bot scripts, and my ability to farm en mass. There needs to be a significant reduction in costs for end-users, in my opinion, by a roughly 50% margin. Even if that means throw away the reward system, who cares, just drive the script price down, please. A lot of us know the store needs another near complete overhaul, with how spaghetti it functions, so any improvements here, are appreciated.

Yeah, the way it is now.. a single auth for a main account is fairly priced, and the way auths are for 250+ auths is affordable, but anything in-between that it feels like youre forced to overbuy and use a coupon just to get a decent price, which actually deters me from wanting to buy new scripts and experiment around. After bond costs, proxy costs, server costs, potential ban costs(which realistically shouldn't be included in the cost, but it is another possible expense) and having to pay near full price to run 10-15 bots, the margin for error and the profit margin are both extremely slim.

  • Like 1
Link to post
Share on other sites
  • 4 weeks later...
1 hour ago, casters said:

All the premium scripts should implement the option to 'dismiss' when an ingame operator comes near you. That's why most people got banned...

I saw it one time in a script every time he rightclick on the person and dismiss it...

There's no known correlation between random events and getting banned, Jagex has stated that they are not used in the same way as years ago due to annoying too many legitimate players. If it makes you feel better, you can configure tribot to dismiss randoms from within the client.

  • Like 1
Link to post
Share on other sites
  • 2 months later...

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

    • We've heard your complaints - the TRiBot API could be much easier to use. We've been dedicating our time to improving the scripter experience here and spent the past year working on a new and improved API - the TRiBot Script SDK.

       

      The TRiBot Script SDK is an easy-to-use library for building TRiBot scripts. It is the recommended approach to building scripts moving forward over the old TRiBot API. It contains all the core things you need to build a script, and a ton of additional helpful stuff to get you using your scripts quicker. See the documentation section for everything offered, and check out the brief overview link too.

       

      The SDK was announced in preview here:

       

      It is now officially released. The official release guarantees we will support backwards compatibility for some period of time. See the 'backwards compatibility' section below for more info.

       

      How to use:

      There is multiple options, listed in the order they are recommended.

      1) Use the gradle template mentioned below

      2) Obtain through gradle

      Add this dependency: api("org.tribot:tribot-script-sdk:+")

      Add this repository: maven("https://gitlab.com/api/v4/projects/20741387/packages/maven")

      3) Take from your local filesystem in your .tribot/install folder. For example, on windows, you'd find it at "C:\Users\[user]\AppData\Roaming\.tribot\install\tribot-client\lib\tribot-script-sdk-[version].jar"

       

      Documentation:

      Java docs: https://runeautomation.com/docs/sdk/javadocs/index.html?overview-summary.html

      Kotlin docs: https://runeautomation.com/docs/sdk/kdocs/index.html

       

      Backwards compatibility:

      We will be following a deprecation schedule whenever we perform a possible breaking change. We will deprecate the respective methods or classes and announce it in a topic. It will remain deprecated for some period of time (weeks or months), and then removed. This will give you time to fix anything, if we need to make a breaking change.

       

      Gradle template:

      Easily build scripts with a new pre-configured scripting gradle template

       

      Users of the current API:

      There is no plans to remove TRiBot API. It will still be available. However, non-critical bugs probably won't be fixed. The SDK does depend on some of the API so fixing some things in the SDK will indirectly fix the API. However, bugs that have existed in the API for awhile will likely not be fixed. It's recommended to use the SDK moving forward. Let us know if there's something the SDK is missing.

       

      Brief overview of the changes:

       

      Bug reports:

      Post bug reports in the bug reports section of the forums

       

       

      Let us know what your thoughts are! If you have questions, feel free to ask below or in discord.

       
        • Like
      • 0 replies
    • Support for the gradle launcher is being dropped. Read more about the new launcher here.
        • Like
      • 8 replies
    • What to expect from TRiBot moving forward.
        • Thanks
        • Like
      • 11 replies
    • TRiBot 12 Release Candidate

      The TRiBot team has been hard at work creating the last major version of TRiBot before the TRiBot X release. We've noticed many problems with TRiBot 11 with a lot of users preferring TRiBot 10 over 11. We've heard you, so we took TRiBot 10, added the new features introduced with 11, introduced some other new things, and created TRiBot 12. So without further adieu, here's TRiBot 12.
        • Sad
        • Like
      • 40 replies
    • Gradle is a build tool used to accelerate developer productivity.

      We recently setup a Maven repository (TRiBot Central) to make it easier for scripters to create scripts. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-central/-/packages

      Furthermore, we've released a simple Gradle project to make it easy to run TRiBot and develop scripts for it. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher

      The goals of TRiBot Central are to:

      Deliver updates to TRiBot faster


      Better organize TRiBot's dependencies (AKA dependancies)


      Make it easier to develop scripts for TRiBot


      Make it easier to use and run TRiBot


      Note: TRiBot won't be able to run scripts from within this project until TRiBot's next release.
        • Like
      • 13 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...