Jump to content
luck or skill

LG can't login????

Recommended Posts

Posted (edited)

Why has this been a problem for YEARS? 
I just don't get why this hasn't been fixed? seriously guys whats the issue with this problem?

Can we get an answer?
Break handler dosnt work... because the bot cannot log back on. 
Sometimes i find the bot on the original login screen (new user existing user) sometimes its in the "world select" sections (wtf)

sometimes it tries to login but fails ahha

An answer please? i've posted this several times over the years and have never had a response form trilez :P
@TRiLeZ @Usa @Fluffee @YoHoJo

Edited by luck or skill
  • Thanks 1
  • thonking 1

Share this post


Link to post
Share on other sites
Posted (edited)

Colour detection bugs out if you don't minimise the client you're hooking onto and the login bot relies on detecting certain colours to see what stage of the login it is at.

If it's spam clicking random spots on world selection then it's due to Jagex adding/removing worlds and tribots worldhopper is just hardcoded, imagine the world screen being split into pre-defined rectangles.

But as to why it bugs out I have no clue but hey at least you know what's causing it :P

Edited by magerz4

Share this post


Link to post
Share on other sites
Posted (edited)
6 minutes ago, magerz4 said:

Colour detection bugs out if you don't minimise the client you're hooking onto and the login bot relies on detecting certain colours to see what stage of the login it is at.

If it's spam clicking random spots on world selection then it's due to Jagex adding/removing worlds and tribots worldhopper is just hardcoded, imagine the world screen being split into pre-defined rectangles.

1.Yeah but minimizing the original client before hooking dosnt always work.
2. Why is it even on the world hopper? the bot i was using dosnt even support world hopping

And i repeat, this has been going on for years

Edited by luck or skill

Share this post


Link to post
Share on other sites
2 minutes ago, luck or skill said:

1.Yeah but minimizing the original client before hooking dosnt always work.
2. Why is it even on the world hopper? the bot i was using dosnt even support world hopping

1. I haven't used LG in ages but when I did, it always did the trick for me. You don't maximise the clients after hooking at all do you? Because that can cause it to bug out.
2. Not sure, it shouldn't be, I know that if you run out of members, it will automatically change to a f2p world for you but you're best off asking the scripter.

  • Thanks 1

Share this post


Link to post
Share on other sites

Very strange. I'm currently running a bit through looking glass and it just finished a break and logged back in flawlessly and resumed where it left off.

Never touch OSbuddy once you open it (I don't even let the client show rs log in screen I race to minimise it as the client first loads up. I get good FPS this way.) I've noticed if I don't beat the client to the rs screen I get bad FPS and then logging in becomes a problem.

  • Like 1

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

  • Our picks

    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 21 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.

×