Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Trung giản thể)
繁體中文 (Trung phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bulgaria)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraina)
Báo cáo lỗi dịch thuật
I spent at least 3 hours trying various configurations. At least it made me optimize the code somewhat :D.
I think what happened with Uncle, is that he caught my mods mid-update on workshop, and I will not know better until he comes back with more information.
- 1.5 or 1.6
- What mods are enabled
- What errors do you see if you enable DevMode and press Console
I just tested and it seems to work fine on my end:
1) RimTek DigiPal-equipped pawn: https://i.imgur.com/JgzRsZr.png
2) Hurt by shooting: https://i.imgur.com/9VqfwIb.png
3) No errors: https://i.imgur.com/vGGOEsR.png
Just in case, if it's Workshop weirdness, try to unsub and resub to the mods, and relaunch your game.
The only idea I have is that maybe the fact that I updated Core and underlying mods synced with your activity on PC and workshop messed it up for you locally.