You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client version: 1.9.4 Server OS: Linux Commit id:b403ad4
I am trying to prevent players from using flint and tinder to set blocks on fire under certain conditions. Although whatever is supposed to happen (in this case setting a block on fire) is correctly blocked, the client still sees the fire. Relogging fixes this and the fire is gone.
Expected behavior
The client receiving a block update telling the block is not on fire
Actual behavior
The client receives no update and thinks the block is on fire
Steps to reproduce the behavior
Prevent fire from happening when a player uses flint and steel by using the HOOK_PLAYER_USING_ITEM hook. If you want to see if the fire is properly blocked or not, relog or use a second account.
The text was updated successfully, but these errors were encountered:
The code in cClientHandle::HandleRightClick looks like it'll resend blocks if the UsingItem hook was cancelled. Pending testing I believe this has been fixed.
Client version: 1.9.4
Server OS: Linux
Commit id: b403ad4
I am trying to prevent players from using flint and tinder to set blocks on fire under certain conditions. Although whatever is supposed to happen (in this case setting a block on fire) is correctly blocked, the client still sees the fire. Relogging fixes this and the fire is gone.
Expected behavior
The client receiving a block update telling the block is not on fire
Actual behavior
The client receives no update and thinks the block is on fire
Steps to reproduce the behavior
Prevent fire from happening when a player uses flint and steel by using the HOOK_PLAYER_USING_ITEM hook. If you want to see if the fire is properly blocked or not, relog or use a second account.
The text was updated successfully, but these errors were encountered: