Results 1 to 5 of 5

Thread: Yellow Minimap Dot Color ID Changing?

  1. #1
    Join Date
    Jul 2015
    Location
    AZ
    Posts
    103
    Mentioned
    2 Post(s)
    Quoted
    56 Post(s)

    Default Yellow Minimap Dot Color ID Changing?

    So I have been using OgLib for scripting lately and am loving it (got my first ever 2 hr+ proggy on my own script today ) but have stumbled across an issue and need some ideas on how to fix it.

    My walking procedure basically clicks based on the location of a yellow dot on the minimap (which I find by checking the color ID to see if it is actually yellow and not a nearby red), but every single time I reload the client the color ID of the yellow dot changes, breaking my walking. Any ideas on how to fix?

  2. #2
    Join Date
    Dec 2011
    Posts
    2,147
    Mentioned
    221 Post(s)
    Quoted
    1068 Post(s)

    Default

    Quote Originally Posted by Hanar View Post
    So I have been using OgLib for scripting lately and am loving it (got my first ever 2 hr+ proggy on my own script today ) but have stumbled across an issue and need some ideas on how to fix it.

    My walking procedure basically clicks based on the location of a yellow dot on the minimap (which I find by checking the color ID to see if it is actually yellow and not a nearby red), but every single time I reload the client the color ID of the yellow dot changes, breaking my walking. Any ideas on how to fix?
    Try adjusting your color tolerance to a value that will ensure the search's success. The default value is 4, and should probably be returned to after your dot search.

    Simba Code:
    procedure someProcedure();
    begin
      ogl.setColourTolerance(someHigherValue);
      myDotSearch();
      ogl.setColourTolerance(4);
    end;

    This is one of the textures that has changing IDs. Similarly, model IDs for granite change every client load. This is one of the reasons we have avoided creating a public database of IDs.

    If you come up with a color tolerance that works (and does not false positive for the other dots) please share! Perhaps we can create a 100% working minimap.getDots() procedure for ogLib.

  3. #3
    Join Date
    Jul 2015
    Location
    AZ
    Posts
    103
    Mentioned
    2 Post(s)
    Quoted
    56 Post(s)

    Default

    Quote Originally Posted by Clarity View Post
    Try adjusting your color tolerance to a value that will ensure the search's success. The default value is 4, and should probably be returned to after your dot search.

    Simba Code:
    procedure someProcedure();
    begin
      ogl.setColourTolerance(someHigherValue);
      myDotSearch();
      ogl.setColourTolerance(4);
    end;

    This is one of the textures that has changing IDs. Similarly, model IDs for granite change every client load. This is one of the reasons we have avoided creating a public database of IDs.

    If you come up with a color tolerance that works (and does not false positive for the other dots) please share! Perhaps we can create a 100% working minimap.getDots() procedure for ogLib.
    Thanks for the fast reply! I will be sure to give this a shot tomorrow, I'm too tired today. Thanks again and I'll try to get that number!

  4. #4
    Join Date
    Jun 2012
    Posts
    586
    Mentioned
    112 Post(s)
    Quoted
    296 Post(s)

    Default

    I've never really seen that. Dots have always had the same colourID for me. Please post your results!

    If all else fails, you could just grab all dots, by textureID, and use the lowest colourID (since yellow < white - I believe).




    Skype: obscuritySRL@outlook.com

  5. #5
    Join Date
    Jul 2015
    Location
    AZ
    Posts
    103
    Mentioned
    2 Post(s)
    Quoted
    56 Post(s)

    Default

    Quote Originally Posted by Obscurity View Post
    I've never really seen that. Dots have always had the same colourID for me. Please post your results!

    If all else fails, you could just grab all dots, by textureID, and use the lowest colourID (since yellow < white - I believe).
    The yellow dot (and all dots) have changed colorID Every. Single. Time. I relog. It doesn't seem to have any correlation to the other dots, sometimes it is the highest number other times the lowest. I am finding it next to a red dot btw.

    Update: I tried to adjust tolerance today and to be completely honest had no idea what I was doing and gave up when I kept returning zeroes. I did just have a sudden realization of a way that would work though and have begun to write that up instead. Thanks for the help!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •