Jump to content
Sign in to follow this  
fegmo

WalkingPreference always set to MINIMAP

Recommended Posts

Hey all,

I'm fairly new to the scripting scene as well as Java, but tend to try figuring out issues I'm having with my own code by myself in hopes of becoming a better programmer. Although I'm getting tangled up with confusion with WalkingPreference. Here's the code:
 

public static void walkPrefTest() {
	ABUTil abc = new ABUtil();
	while (true) {
		int i = General.random(4, 13);
		System.out.println(abc.generateWalkingPreference(i) + i);
		General.sleep(100);
	}
}


I'm unsure if I'm using it completely incorrectly, if it's a stupid little mistake or if the SCREEN pref is insanely rare.
When using other generated preferences i.e. the bank preference, both preferences show up.

Thanks all in advanced! 

Share this post


Link to post
Share on other sites
17 minutes ago, fegmo said:


I'm unsure if I'm using it completely incorrectly, if it's a stupid little mistake or if the SCREEN pref is insanely rare.
When using other generated preferences i.e. the bank preference, both preferences show up.

Thanks all in advanced! 

From the api:

Some profiles specify that the player should walk using the screen if the distance is short. Others will specify to always use the minimap. 

Could just be the specific profile for your character, could be that it in general it is rare for screen pref, or it could be that the random number you are testing is a bit high, who knows. Try it with a static, lower number and see if it has any difference?

Share this post


Link to post
Share on other sites
10 minutes ago, FALSkills said:

Could just be the specific profile for your character, could be that it in general it is rare for screen pref, or it could be that the random number you are testing is a bit high, who knows. Try it with a static, lower number and see if it has any difference?

Hey FALSkills, thanks for the quick responds.

I also thought that was the case, which is why I tried on multiple accounts but had the same outcome (forgot to mention). Maybe I'm just absurdly unlucky haha. Thank you for the input though, I appreciate the help!

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
Sign in to follow this  

  • Our picks

    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 8 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
    • 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


      Bug fix for intelligent banking


      Improvement to the stability of LG over time



      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
      • 10 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×