Anyone else having trouble with FaceTo? - [TBC Classic][2.5.3.42598] menu

User Tag List

Results 1 to 5 of 5
  1. #1
    UsuallyHome's Avatar Member
    Reputation
    1
    Join Date
    Nov 2019
    Posts
    8
    Thanks G/R
    0/0
    Trade Feedback
    2 (100%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Anyone else having trouble with FaceTo? - [TBC Classic][2.5.3.42598]

    Code:
    void __fastcall sub_1306A40(__int64 a1, float a2)
    {
      __int64 v2; // [rsp+28h] [rbp-30h]
      __int64 v3; // [rsp+30h] [rbp-28h]
      __int64 v4; // [rsp+38h] [rbp-20h]
      __int64 v5; // [rsp+40h] [rbp-18h]
    
      if ( *(_QWORD *)(*(_QWORD *)(a1 + 392) + 192i64) > 0i64
        && xmmword_2F71208 == *(_OWORD *)*(_QWORD *)(a1 + 5656)
        && *(_DWORD *)(qword_31A0AC0 + 92)
        && !(*(_BYTE *)(a1 + 59322) & 0x20) )
      {
        v2 = 0i64;
        LODWORD(v3) = 0;
        v4 = 0i64;
        v5 = 0i64;
        sub_12EECF0(a1, 3i64, &v4, &v2, LODWORD(a2));
      }
      JUMPOUT(0x1306AD5i64);
    }
    FaceTo(playerPtr,angle)
    Appears to be unchanged from last time I was using it / had it working(v40617 - 0x122B920). CTM(0x1306A40) is functioning as expected, however, FaceTo is crashing. Alternate solution not expected. A simple sanity check "simple call is no longer viable" would be greatly appreciated if this is the case. Thank you in advance.

    Edit: My apologies, should have looked more into this before firing off a post, will re-examine this evening(12ish hours) and hopefully come up with a more purposeful question/solution.
    Last edited by UsuallyHome; 03-14-2022 at 09:52 AM.

    Anyone else having trouble with FaceTo? - [TBC Classic][2.5.3.42598]
  2. #2
    oiramario's Avatar Established Member
    Reputation
    85
    Join Date
    Mar 2021
    Posts
    133
    Thanks G/R
    36/51
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    address is correct.
    this call is functional.

  3. #3
    nfgstar's Avatar Member
    Reputation
    1
    Join Date
    Oct 2020
    Posts
    6
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Adddress is 0x1306CF0

    sorry, 0x1306A40 is correct. and your code looks correct too.
    Last edited by nfgstar; 03-14-2022 at 05:05 PM.

  4. #4
    oiramario's Avatar Established Member
    Reputation
    85
    Join Date
    Mar 2021
    Posts
    133
    Thanks G/R
    36/51
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by nfgstar View Post
    Adddress is 0x1306CF0
    It's ClickToMoveTargetTo, not FaceTo.

  5. #5
    nfgstar's Avatar Member
    Reputation
    1
    Join Date
    Oct 2020
    Posts
    6
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by oiramario View Post
    It's ClickToMoveTargetTo, not FaceTo.
    Yes, 0x1306A40 is correct., my mistake.

Similar Threads

  1. Replies: 2
    Last Post: 05-01-2018, 11:16 PM
  2. [How-To] Issues with sniping and nox gps, anyone else having this problem?
    By hphln in forum Pokemon GO Hacks|Cheats
    Replies: 5
    Last Post: 07-26-2016, 11:39 AM
  3. anyone else having trouble trading timeless pieces
    By Koldhearted in forum World of Warcraft General
    Replies: 1
    Last Post: 09-25-2013, 08:26 PM
  4. Is anyone else having a problem with Ripway?
    By parinoia in forum WoW Scams Help
    Replies: 11
    Last Post: 03-06-2009, 07:15 PM
  5. Replies: 3
    Last Post: 11-29-2008, 10:05 PM
All times are GMT -5. The time now is 06:34 AM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search