CanLockSign and CanUnlockSign not working

Discussion in 'Rust Development' started by miRror, Nov 3, 2016.

  1. miRror

    miRror

    Don't work hooks
     
    miRror, Nov 3, 2016
    #1
  2. Wulf

    Wulf Community Admin

    What exactly isn't working about them? How are you using them? Details are needed.
     
    Wulf, Nov 3, 2016
    #2
  3. miRror

    miRror

    Code:
    void CanUnlockSign(BasePlayer player, Signage sign)
{
    SendReply(player, "CanUnlockSign works!");
}void OnSignLocked(Signage sign, BasePlayer player)
{
    SendReply(player, "OnSignLocked works!");
}

    but hook CanUpdateSign now worked:

    Code:
    void CanUpdateSign(BasePlayer player, Signage sign)
{
    SendReply(player, "CanUpdateSign works!");
}
     
    miRror, Nov 3, 2016
    #3
  4. Wulf

    Wulf Community Admin

    They haven't moved and are still called from what I can tell.
     
    Wulf, Nov 3, 2016
    #4
  5. miRror

    miRror

    @Wulf, I already checked this hooks, but they not working. What I'm doing wrong? Can you check by yourself?
     
    miRror, Nov 3, 2016
    #5
  6. Wulf

    Wulf Community Admin

    Are you using an official build or did you patch on your own?
     
    Wulf, Nov 3, 2016
    #6
  7. miRror

    miRror

    Official build
     
    miRror, Nov 3, 2016
    #7
  8. Wulf

    Wulf Community Admin

    Testing the hooks right now.
     
    Wulf, Nov 3, 2016
    #8
  9. miRror

    miRror

    Thanks.
    [DOUBLEPOST=1478198357][/DOUBLEPOST]@Wulf, So, do they works? Thanks for reply.
     
    miRror, Nov 3, 2016
    #9
  10. Wulf

    Wulf Community Admin

    Not sure why, but that whole method in Rust isn't being called. You could use CanUpdateSign though, that's essentially the same thing.
     
    Wulf, Nov 3, 2016
    #10
  11. miRror

    miRror

    Damn, that's bad. We really need this hooks, any way you can fix them?
     
    miRror, Nov 3, 2016
    #11
  12. Wulf

    Wulf Community Admin

    If Rust doesn't use it, it won't be called. CanUpdateSign is literally the same as CanLockSign/CanUnlockSign with the exception of checking if the door is locked or not, which you can do if you need.
     
    Wulf, Nov 3, 2016
    #12
  13. SannyOK

    SannyOK

    CanUpdateSign not match, because it sends when contain of the table refreshes. He needs to block ability to "block action" (close for changing) tables.
     
    SannyOK, Nov 3, 2016
    #13
  14. Wulf

    Wulf Community Admin

    You can block the action with CanUpdateSign, just return true. If Rust doesn't call the others, there isn't really anything that can be done. The CanUnlock and CanLock locations literally rely on CanUpdateSign and what it returns.
     
    Wulf, Nov 3, 2016
    #14
  15. miRror

    miRror

    https://pp.vk.me/c637826/v637826897/1aa91/gEJ6SN0KVAA.jpg
     
    miRror, Nov 3, 2016
    #15
  16. Wulf

    Wulf Community Admin

    Yes, what about it? You can see from your screenshot that both locking hooks call CanUpdateSign. The other locations is where the hooks are that are not working that you are complaining about, but the one for locking is never called. The best way to do it right now is with CanUpdateSign.
    Code:
    bool CanUpdateSign(BasePlayer player, Signage sign)
{
        if (Signage.IsLocked()) && !player.IsAdmin()) return false;
}
    ^ Quick and easy example of checking if they can unlock if they are admin.
     
    Wulf, Nov 3, 2016
    #16