安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
0 
举报此帖
I know the error looks like it comes from EasyChat but it does really seem like this addon is using the chat wrong. And by that I mean using the functionalities of the chat wrong. Which is why it also breaks EasyChat naturally.
RtD intercepts the trigger message and resends it manually to preserve the order of operations, ie:
1. Player writes !rtd to chat
2. Something random happens
3. Feedback is sent to the player's chatbox about the roll's outcome
This would normally create an infinite loop, because the hook triggers and the function resends the command continuously. To prevent this, the function appends an extra space after the message (so that it no longer matches the command on the next call and returns immediately).
I haven't looked at EasyChat's code extensively, but if I'm right, it trims the extra space after the command and causes the mentioned stack overflow as a side effect. I might be able to fix it by using a different method for preventing this loop.
I'll look at this in the coming days and report back about the success. Until then, I'd appreciate @Eapy if you could check it and confirm if my assumption is correct about EasyChat trimming messages. Either way, this change should be an improvement to RtD, but I hope this will also fix the issue.