Jump to content
Sign in to follow this  
mjmfighter

Announcement regarding Divinus

Recommended Posts

Ok?  That is still distributing it.  Idk if you have heard, but there are password crackers out there.  Sure it was a long password, but give someone a few bucks and they will crack any zip file for you now adays.  

so because he was attempting to make a point you folks think the logical decision is to ban him and screw 4k people out of their scripts?

Share this post


Link to post
Share on other sites

YUP.

 

 

and then another mod closed down my dispute topic because it was causing too much spam and nothing was being resolved as thebat didnt wanna pay me cuz "he didnt have any gp himself, and he was a student" mods gotta stop backing up other mods please, if you are moderating a website you better know how to hold it down for yourself, or you shouldnt be staff.

Share this post


Link to post
Share on other sites

As many have seen, he has been banned.  I am making this announcement to stop all the rumors that are spreading throughout the community about why he was banned.

 

Divinus was NOT banned because of the vulnerability in his loader.  A member of the staff pointed it out to him and asked him to fix it in 48 hours or we were going to remove the links until it was fixed.  We NEVER said we were going to ban him over this.  We simply asked him to fix his vulnerabilities so all the scripts that were on it would not be leaked.

 

Instead of fixing a small flaw in his loader, Divinus proceeded to take USA's script and crack it.  He then distributed this cracked version through of USA's script in a skype chat to people.  As this is breaking the rules, he will remain banned.

 

As for what to do in the future for current "Premium Scripts", TRiBot has never endorsed premium scripts other than giving them a section to be organized in. Currently, TRiBot takes a 0% cut of all profits generated by these scripts. What does this mean? It means your script's author is entirely responsible for coding, updating, selling, and securing the script he or she creates and that TRiBot has no responsibility in this matter.

 

However, our store is currently our number one priority and TRiLez has now moved to TRiBot development as a full time position having left his previous job just recently. Once the store is set up, premium and free scripts will be distributed freely.

 

Sorry for any inconvenience this has caused,

- TRiBot Staff

 

I underlined a part that is important....IF OUR SCRIPT AUTHORS HAD PROBLEMS WITH IT THEY WOULD TAKE IT DOWN THEMSELVES NOT FOR USA TO DECIDE WHATS SAFE FOR OUR SCRIPTS LET THE AUTHORS DECIDE NOT U!

Share this post


Link to post
Share on other sites

Its his script, he is personaly disputing his own script. Divinus is hosting unsecured scripts there is a clear difference 

 

As stated before, no one else but USA had a problem. Not any other mods, not the scripters and not the people using the script. USA is just abusing his power. 

Share this post


Link to post
Share on other sites

The point Being mjmfighter, is that we don't care about USA's Script.. we don't care about the Drama or anything else.

WE the People of Tribot have payed for scripts and pay every month just to BOT.
its not right to make us have to Suffer for something that has nothing to do with us what so ever.
and in all honesty, this Kind of Drama is pretty pathetic.
We just want to Bot again.
i got banned by USA because i wanted to Divinius to be unbanned.
[ Hendrew ]

i Emailed TriLez and he unbanned me right away, what a nice guy.

anyway.. moving on.
even though its not MY fucking problem, i'm willing to pay $10 - $30 to Unban Divinius or get the scripts running within a few hours.
not only am i willing to fucking Donate, if nothing happens tons and tons of scripters will leave and loads of people will aswell.
this is just a huge Havok that shouldn't of been created to begin with.

~ HENDREW

Share this post


Link to post
Share on other sites

Its his script, he is personaly disputing his own script. Divinus is hosting unsecured scripts there is a clear difference 

It's my choice to allow him to do so. Nothing in Java is ever 100% secure. 

Share this post


Link to post
Share on other sites

Ok?  That is still distributing it.  Idk if you have heard, but there are password crackers out there.  Sure it was a long password, but give someone a few bucks and they will crack any zip file for you now adays.  

 

How about responding to the VIPs and people who have purchased premium scripts? A total waste of money on all of our parts because a simple lack of maturity on YOU the staff of Tribot's part.

Share this post


Link to post
Share on other sites

Its his script, he is personaly disputing his own script. Divinus is hosting unsecured scripts there is a clear difference 

Then shouldn't I decide If I want to use his service? Cracking USA's script would require changing a false to a true. Cracking the script loader requires a auth and more knowledge then I have.

  • Like 1

Share this post


Link to post
Share on other sites

Its his script, he is personaly disputing his own script. Divinus is hosting unsecured scripts there is a clear difference 

Horrible logic buddy. If the Script Writers were so concerned about the possible cracking of their scripts they would have stopped using Div's service. It is not for a power tripping mod such as USA to decide. 

Edited by skilled

Share this post


Link to post
Share on other sites

He was banned because he hacked a premium script, his loader "service" has security issues where the SOURCE of scripts were compromised with my script he performed a different exploit however my SOURCE was never compromised.

 

I gave him 48 hours to fix his service's issues, he responded by releasing my 'cracked' script to a conversation in Skype. That was his choice.

 

Who gets reimbursed? Take it up with your Scripter, we dont have a single penny of your money. It was their decision to out-source their security to an unverified user; that has nothing to do with the future of TRiBot.

 

Seeing how this conversation is going already, I'm going to lock this announcement until further notice. Any futher topics regarding this matter will be infracted.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Our picks

    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 23 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×