runescapeThank you. But what does the 2 do? Isn't 0 global and 1 team chat?
0 = global
1 = team
2 = server
Server I am assuming would always be seen.
runescapeThank you. But what does the 2 do? Isn't 0 global and 1 team chat?
0 = global
1 = team
2 = server
Server I am assuming would always be seen.
runescapeAny number between chat.say and the message works, tried 0 to 9 with both message and /padmin command.
Any number is not valid and only sets you up for potential issues; I'd stick to the specific channels:
0 = global
1 = team
2 = server
Please see the above replies.WhileAnyone else unable to keybind automatic upgrading after the last patch?
WhileAnyone else unable to keybind automatic upgrading after the last patch?
instead of « bind KEY chat.say /COMMAND » try « bind KEY chat.say 2 /COMMAND ».
rfc1920
Sadly, none of these are working for me. I unloaded BetterChat just in case and still have the same issue.
Chat.say is handled by the game. The method the Better Chat uses is correct, but I'd check with any other chat plugins you may have installed as well.
bringer0deathAt the moment, it appears you can't access the NightVision mod from key binds or console commands. There is an issue going on with Chat.Say due to the new Team Chat update in the November 2019 for Rust. Is there any work around for this planned. I get TRUE coming up in chat when I try to run the NightVision command and it doesn't activate anymore. This is happening though on most mods at the moment, not just limited to NightVision
Please see the above replies regarding chay.say handling changes in Rust.