Results 1 to 4 of 4

Thread: SetScreenMouse

  1. #1
    Join Date
    Mar 2007
    Posts
    5,125
    Mentioned
    275 Post(s)
    Quoted
    901 Post(s)

    Default SetScreenMouse

    Since EoC, when the action-bar is enabled, the procedure 'SetScreenMouse' can sometimes fail due to the action-bar being enabled on-screen blocking the initial right-click of the mouse as it right-clicks in the actionbar

    Forum account issues? Please send me a PM

  2. #2
    Join Date
    Aug 2007
    Location
    Colorado
    Posts
    7,421
    Mentioned
    268 Post(s)
    Quoted
    1442 Post(s)

    Default

    Ah yes I've noticed this as well. In line 371 of antiban.simba (SRL/core) you'll see this:
    Simba Code:
    YStart := RandomRange(MSY2, MSY2 - 55);

    We could simply change that to something like...
    Simba Code:
    YStart := RandomRange(MSY2-50, MSY2 - 105);

    Assuming the ActionBar is around 50 pixels in height. We could also have it first check if the ActionBar is currently enabled and yes that modified line I posted above, or if it's disabled then use the current "RandomRange(MSY2, MSY2 - 55)". Either way, that should fix it.

    Current projects:
    [ AeroGuardians (GotR minigame), Motherlode Miner, Blast furnace ]

    "I won't fall in your gravity. Open your eyes,
    you're the Earth and I'm the sky..."


  3. #3
    Join Date
    Nov 2011
    Location
    England
    Posts
    3,072
    Mentioned
    296 Post(s)
    Quoted
    1094 Post(s)

    Default

    Setscreenmouse slowly lowers the angle over time for me, kind of annoying since we cant check the angle.

  4. #4
    Join Date
    Jan 2012
    Posts
    2,568
    Mentioned
    35 Post(s)
    Quoted
    356 Post(s)

    Default

    This isn't going to be a simple fix. Based on the original code
    Simba Code:
    YChange1 := YStart + RandomRange(278, 280);
    YChange1 := YStart - RandomRange(278, 280);
    our YChange have to be => 278 to switch from the lowest to highest or vice versa, but now the action bar limits our Y2 to 261, so to change from lowest to highest we will either need 2 tries, or close the action bar, and re-enable it afterwards.

    EDIT: the current mechanism always moves to the max Y first, then makes necessary adjustment to the desired level (eg. to move from 1 to 9, it will first move =>278 to get to 10, then moves back slightly to reach 9), though we can change this mechanism, our limitation remains at max YChange of 261 (and to achieve this we must start from MSX1, or 261 if moving upwards, which is pretty botlike), so this function must be revamped to try twice when necessary, or we just close the action bar, adjust then reopen? But that's a bit bot-like imo.

    EDIT2: oh now i realize why this mechanism of adjusting to the max first is made, as there is no way to detect our current angle, so the exact YChange required cannot be calculated unless starting from the lowest/highest angle.
    Last edited by riwu; 12-23-2012 at 04:49 AM.

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
  •