Jump to content

Fluffee

Administrator
  • Content count

    3,254
  • Joined

  • Last visited

  • Days Won

    40
  • Feedback

    100%

Posts posted by Fluffee


  1. Just now, Naton said:

    I also think that there should be a “beta” category for scripts that are hidden unless linked (or maybe searched) because I often find myself with others looking to help search for bugs, so I’ll upload a closed beta to the repository which probably doesn’t help it look too clean (I know some others do this as well). 

    As a temporary fix, I can hide your scripts, so they're only viewable with the direct link. Feel free to PM me your script betas and I'll be more than happy to hide them!

    • Like 1

  2. 1 hour ago, Einstein said:

    At the time of writing, the dysfunctional scripts greatly outnumber the functional ones. Not only that this increases the likelihood of new users activating non-working or just horrible scripts, but it makes the whole repository look incredibly cluttered, which has the following negative effects:

    • It's very unappealing, and I've never seen any successful real-world shop that doesn't emphasize on its appearance.
    • Due to the immense amount of clutter, users are unable to find and activate the quality scripts that are currently available.

    I agree. Users need to see, and easily be able to find working, quality scripts to use, free or otherwise. Having a messy repository full of outdated scripts is hard for anyone to navigate, especially if you're new and naively assume everything on the repository works.

    1 hour ago, Einstein said:

    At least in my opinion, all the repository scripts should simultaneously meet the following criteria:

    • To be publicly available for all users. (removal of the so-called 'private' scripts hosted on the repository by non-Premium Scripters)
    • To be completely functional.
    • To be at least decent in quality if the author is a regular user.
    • To be high in quality if the author holds the Scripter rank or above.

    I again agree, especially with the private scripts. I have no idea why anyone, especially Scripters/Premium Scripters, feel it is appropriate to put private scripts publicly on the repository. While there isn't a rule against it, I definitely feel they should be hidden.

    1 hour ago, Einstein said:

    We already have a "Report non-working scripts" thread on the public forums, but it doesn't work for the following reasons:

    • The amount of work required to go through each and every report is too high.
    • This is a never-ending job, as new scripts are constantly being uploaded and older scripts are constantly getting outdated.
    • The regular users don't know what to look for. Recently, some fully functional, very well maintained scripts have been wrongfully reported.
    • The vast majority of users don't even know about that thread, or if they do know, they can't bother to report anything.

    Exactly. That thread may work well in the future, if the repository was deeply cleaned, then it would just need to be maintained. However, in the repository's current state, it's not going to work.

    Attempting to trust regular users to determine if a script is not working is, in my opinion, a bad idea. While theoretically nice, I personally wouldn't trust  most users to determine if script's are broken, as I don't have faith the issues wouldn't just be something with their setup. Furthermore, even if we could trust them, the job of reporting scripts shouldn't be on them.

    1 hour ago, Einstein said:

    The best way to tackle this problem would be to have a team of scripters that are actively searching for dysfunctional scripts, and reporting them on a special thread opened in the scripter's forums.

    An SqanLxV.png should oversee the whole process and will have the final word, on deciding whether or not a script remains in the public repository.

     

    Why scripters only?

    • It's in or best interest to keep the repository clean. The average user couldn't care less about this matter.
    • We write scripts ourselves, we know what to look for and we can tell the quality of a script within minutes or even seconds of running it.
    • Because of the previous reason, a scripter report is much more accurate and if a script was deemed sub par, it probably is. Therefore, and Administrator's review on the report shouldn't take more than a few minutes at most.

     

    Neat, I'm actually qualified to oversee this apparently 😂

    I agree with the idea of having a team of sorts to actively hunt down dysfunctional scripts. Having attempted, to clean the repository myself, the sheer volume of scripts to test is overwhelming. A group of people would still have a crazy amount of work to do, but it'd be much more manageable.

    I would be inclined to get Scripter's to help with this, mostly, because I trust them to know how to use the client. This process wouldn't work if I, or another Admin had to test every script ourselves after the report, as that would still be a crazy amount of scripts to test. I believe that for the most part, those on the team would have to be trusted to test the script so an Admin could remove it without personally testing.

    1 hour ago, Einstein said:

    but I think that a minimum of 3 high-quality, free scripts is within reason.

    This was actually a requirement of Scripter rank, not just for the entrance to the rank, but to be maintained while the rank is held. I'm pretty sure that, Premium Scripter was also meant to be only held if a person actually has a Premium Script (the rank couldn't be held to just write privates). However, I don't believe these rules have been enforced for years, but I believe they should be, as free scripts are vital to attracting new users.

    While I haven't spoken to Todd or TRiLeZ about this in months, as I abandoned my personal project of cleaning the repository, I'll mention this to TRiLeZ today, see if he has any input.

    • Like 2

  3. On 8/2/2018 at 11:48 PM, contemporary said:

    It might not trigger every break, but it's a major bug that happens often enough to disrupt botting significantly. Without babysitting, it's impossible to run multiple bots with breaks.

    Let us know if we can help with providing additional information or testing, this bug really needs to be addressed seriously and squashed.

    You can actually! See the information at the bottom of the post.

    On 8/3/2018 at 8:29 AM, theholyone said:

    Instead of trying to replicate this consistently which I honestly don't think it's even possible now because of how random it is, finding a temporary patch that will fix the problem for now seems like a more logical choice.

    Ideal situation IMO would be to leave the client as is for the people who for some reason don't trigger the bug while leaving a separate beta version of tribot for those of us who are desperate for any strand of hope.

    also it's been 14 days not 20 lol

    Client starter is also broken, does not load correct worlds whether you put 301 or 1 as selected world, didn't realize this til now 😐

    I actually misspoke about the consistent replication, well actually I misunderstood. Todd is looking for a consistent way to replicate the bug, but that's only because he hasn't been able to replicate it at all. He's currently running over 15 accounts non stop on various break profiles, trying to get the bug to occur, and he's been doing this for days. He still hasn't seen the bug, which is why there hasn't been a fix.

    I believe his new plan is to manually look through every line of code that was changed in the last update to see if there is anything obviously wrong, but I'm unsure how long that will take, as it depends on how much was changed with the last update

    On 8/3/2018 at 5:36 PM, contemporary said:

    When a bug is difficult or impossible to track down, rewriting small parts of code can be an easier and quicker solution.

    Judging by forum posts, some users with custom built break/login handlers aren't experiencing these issues.

    Todd isn't big on this idea. I would guess that the login bot/break handler, is more complicated than we think and rewriting it from the ground up could be a much bigger project.

    On 8/4/2018 at 10:57 PM, theholyone said:

    Would very much love it if we could get a confirmation on whether a separate beta version of the client is possible while we wait until this issue can be successfully recreated consistently.

    ( Separate not as in Developer release, because that doesn't support the built in client starter afaik )

    I am not a programmer, but from my POV, if someone is out looking for a consistent way to replicate a bug, there should theoretically be a solution or a temp fix for problem already, and they are just trying to find a way to make it a perm fix.

    @Fluffee

    P.S this wouldn't of hurt so much if there wasn't a huge 700 - 1000k membership sale going on... 💔

    See above, I was wrong about the consistent way, that's my mistake. Sorry about that.

    As we're still having issues replicating the bug. if anyone reading this is someone who experiences the bug frequently, Todd strongly encourages you to run the developmental release of TRiBot. While the dev release won't fix the bug with the login, it does print a massive amount of debug information which Todd can use to diagnose the problem.

    To run the Developmental Release tick the box in the TRiBot Loader labeled Developmental Release. Then, when you experience the bug, send the entire bot and client debug, either to myself or Todd. Hopefully then Todd can get a fix soon!

    • Like 2

  4. 9 hours ago, I_Merk16 said:

    When I click run it opens in safari

    EDIT: When I click on open it opens up in internet explorer and has the option to run , save and save as ..

     

     

    On 7/22/2016 at 8:53 AM, Fluffee said:

    You must open TRiBot_Loader.jar with Java for it to work properly. The latest Java Development Kit (x86, 32 Bit version) is recommended for optimal use with TRiBot which can be downloaded from this link Java Development Kit Downloads.

    After that has been completed, try running this program to fix the .jar file associations and allow TRiBot to run with the latest java http://johann.loefflmann.net/en/software/jarfix/index.html

    Alternatively, follow the steps in this thread to manually associate the proper java version with .jar files, and as a result, enable TRiBot to run properly. [PC] How To: Open the TRiBot_Loader.JAR file w/ Java [Pics]


  5. On 8/4/2018 at 3:50 PM, briefcase235 said:

    i cant get the client started on centos 6.9 and java 1.8.0 jre

    it starts the login screen when i login it gives some red code in the loader and shuts it down without starting the osrs client

    You'll need to post that red code here, so we can sort out what the issue is

    • Like 1

  6. This error is caused by a Java version that TRiBot does not support. TRiBot only supports Java 8 (the error message is out of date, and doesn't specify this). So you'll need to uninstall Java 10, and install Java 8, or manually force TRiBot to use Java 8.


  7. 7 hours ago, theholyone said:

    At this point, what can us as users do to help the situation, because tomorrow's going to mark the 2nd week that this has been happening and we've still got NO response from either of the admins.

    Sadly, you most likely won't get one, that is actually why they have me to be honest. They are aware of the issue, but they usually leave me to deliver information. I can get Todd to post if you'd like? But it'll simply be a restatement of what I've already said, as I got the information primarily from Todd.

    7 hours ago, theholyone said:

    Need data?

    Todd's still hunting a way to reproduce the issue consistently. If you can figure out a way to cause the login bot/break handler to break every time, then that'd be an amazing help!


  8. 6 hours ago, grammatoncleric said:

    I understand how to use the break handler, as Yohojo's vid clearly explains, however, these are very basic breaks, which is great, but I would like to have a cycle. This being a 24hr cycle, so I can just leave the bot running, and having it break when it needs to. No idea how to setup a 24hr breaking system. I understand single line breaks with the repeat option, but I do not understand multiline breaks. This is how I am assuming to get a bot that will run for x amount of minutes, break for x amount of minutes, continue, repeat until the duration of running the script has stopped, break for a day, then continue running the script for x amount of minutes, break for x amount of minutes, etc... 
    Have attempted to post in einstiens thread about this, however, it has been several days with no response. Could really use the help...

    Thank you,

    grammatoncleric

    As far as I know, you cannot loop entire break profiles, just individual breaks. You'd need to use the script queue, to manage re running the script multiple times, or setup a break profile to last for however many days you want to run the script


  9. 2 minutes ago, michaelpwn said:

    I am running Oracle java 8 and this is the outcome when I try to press start script:

    image.thumb.png.a1d58427bf0f1205721b053edd53d89e.png

     

    6 hours ago, Fluffee said:

    It looks like TRiBot is flagging your server's IP address as a spammer, and not allowing you to connect


  10. Try this:

    On 11/11/2015 at 9:23 AM, Laniax said:

    Looks to me like its trying to connect over IPv6 instead of IPv4, reinstalling java might do it, but i think you can also run this from a command line.

    setx _JAVA_OPTIONS -Djava.net.preferIPv4Stack=true

    if you are unsure where to type that, open Start, type CMD and hit enter. A black box will appear and you can paste the above line by right clicking somewhere and clicking paste. 

     

    • Thanks 1

  11. Try disabling the TRiBot Firewall. To do so, open a new TRiBot client, and click the "File" menu, and under that menu select "Settings" (it should be the top option). Once the settings window opens, the last checkbox in the window is labelled "Enable TRiBot Firewall", go ahead and uncheck that box, and close the settings window. You should get a prompt to save your settings, so go ahead and click yes on that. Then try starting the LAN Thiever script, it should hopefully load properly and not freeze your client this time!


  12. That error you posted doesn't have anything to do with Java, but rather has to do with your server's connection to TRiBot. It looks like TRiBot is flagging your server's IP address as a spammer, and not allowing you to connect


  13. On 7/27/2018 at 2:20 PM, Darkmax2 said:

    any news ??

    I haven't heard anything, but I haven't been around much over the weekend. I'll speak with Todd today, and see if any progress has been made.

    Edit: Currently still working on a fix 😦


  14. 8 hours ago, MuleTraveler said:

    Erm. So what I originally intended was to upgrade my pre-existing VIP to VIP-E. Not add a whole another month of VIP-E. So ideally, I wanted 30 VIP 30 VIP-E. BUT, I ended up getting 60 VIP 30 VIP-E accidently and I don't really use VIP without VIP-E. Am I just stuck with what I got? 

    Yes, you must have purchased a month of VIP-Extended on top of your regular VIP. To fix this, whenever your VIP-Extended runs out, just upgrade the remaining VIP to VIP-Extended to avoid wasting the money if you only want to use Extended!

    • Like 1

  15. 51 minutes ago, MuleTraveler said:

    Hello guys,

    I didn't know who to ask nor where to ask so I'm posting this as a general questions thread. Recently I had around 30 days of VIP and I wanted to upgrade it to VIP-E. I remember being able to upgrade it by throwing in a few extra credits. However, when I attempted it this time, instead of upgrading my existent 30 days of VIP, it added on 30 days of extended VIP on top of the current VIP. Is there any way a mod could take a look at this and do some sort of conversion? I wouldn't want VIP without VIP-E. So maybe instead of 60 days VIP + 30 days VIP-E, allow me to have 45 days VIP-E? 

    It worked as it was supposed to actually! VIP-Extended is an addon for VIP, meaning that every day of VIP-Extended consumes one day of VIP-Extended and one day of VIP (you'll notice that when you buy VIP-Extended normally you get 30 days of both). When you upgraded you just added the VIP-Extended part, which will consume your VIP and VIP-Extended with each day of VIP-Extended 🙂

    • Like 1
×