安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
I RECOMMEND YOU TO USE THIS MOD IT MAKES FINDING HOOKS 100X EASIER
I apologize for not being helpful.
All you need is to gather the event names relative to damage and see what this add-on identifies.
You don't need an automated conflict compass when you know what you need to inspect.
And for the slow-down problem, you should give my lag finder a try. This other add-on is easier to use than the conflict finder, since the only things it's able to detect are slow-downs, which is why you would use the tool in the first place.
For the step 1, it is in files. The rest of the procedure assumes that you located the hook that does not work.
There is a conflict though, I see that the Sound() function was replaced with a string value.
My suggestion, to begin with, is to display the value of Sound . You can type in your console:
lua_run print('Sound =', Sound)
Maybe you will see a value that guides you to identify the guilty add-on.
Consider adding me on Discord if you need to share your screen or something.
[Brutal Deaths] lua/autorun/server/death.lua:58: attempt to call global 'Sound' (a string value)
1. v - lua/autorun/server/death.lua:58
2. unknown - lua/includes/modules/hook.lua:84 (x2)
im unsure how to use the command properly, little help?
I perfectly agree that this tool is very hard to use without knowledge.
Do not worry, you are already forgiven! ;-)
Either they saw a bad add-on and thought it is mine, or they were just saying crap because this add-on is too brilliant.
Sorry for taking a long time, I did not expect to be unsubscribed from comments.
If it's an addon that fails then it's likely to use a hook added with hook.Add(). You probably have not selected the right event, or you did not catch this message during the failure.
During an event, the hook from the gamemode happens after all hooks added with hook.Add(), so your message does not display a conflict.