flutes

Changed Status from Pending to Closed

Hi, First of all, I'm really sorry for the extremely late response. You were absolutely right to expect support for this, especially for an issue that affects something as important as RCON/BattleMetrics communication. From your description, it sounds like the plugin was intercepting global chat in a way that prevented the normal Rust chat event/logging pipeline from reaching RCON, BattleMetrics and Discord integrations. Team chat being unaffected would also be consistent with that behavior. The plugin has been updated since this report, so if you're still using it, could you please test the latest version and let me know if the problem still occurs? If it does, please send me your current plugin version, whether you're running Oxide or Carbon, and which RCON/Discord integration you're using, and I'll investigate it properly. Since this support request is quite old and I don't know whether the issue still exists in the current version, I'm going to close this request for now. If you're still experiencing it, please reply/reopen the request or create a new one and I'll take care of it. Again, sorry for the lack of support at the time and for the very late response.

Changed Status from Pending to Not a Bug

Hi, Sorry for the late reply, and thanks for your patience. Yes, I agree that having global chat translated automatically makes more sense from a usability standpoint. The reason it is currently opt-in is mainly to avoid automatically sending every player's chat messages to the translation API by default, which could also result in unexpected API usage and costs for the server owner. You can grant the permission to all players with: oxide.grant group default aitranslationpro.chat.use Players will still need to enable translation with /ait.chat on for now. I'll consider adding a configuration option in a future update to allow server owners to enable chat translation by default for everyone, so servers that want fully automatic translation can opt into it. I'll mark this request as resolved for now. Thanks again for your feedback, and sorry again for the delay.

Hi! I’ve just granted you free access to the Vote Reward bundle. You should now be able to download it from your Codefling account. It includes Custom Rewards, which lets you configure item rewards for your players without writing any code. If you run into any issues or need help setting it up, feel free to contact me through Codefling support or on Discord: d.0ne_. I usually respond faster on Discord. Happy to help!

Hi! Sorry my previous reply gave the impression that you needed to create your own plugin — that wasn’t what I meant. The product page lists VoteSystem’s features: it handles vote tracking and points, includes developer/API tags, and directly references Custom Rewards for reward integration. Built-in item rewards aren’t listed as an included feature, but I understand you expected to configure them directly in VoteSystem. I’d like to help you get the setup you were looking for. I can offer you free access to the Vote Reward bundle, which includes Custom Rewards for item rewards. Alternatively, I’m happy to support your refund request, although approval and processing would be up to Codefling. Let me know which option works best for you!

Hi! Economics is entirely optional and can be disabled in the configuration. VoteSystem handles vote tracking and provides points, hooks and APIs for reward integrations. To give items, you can use VoteRewards or CustomRewards, or develop your own plugin using VoteSystem’s hooks/API. Item rewards aren’t configured directly in VoteSystem.

This error means Rust-Servers.net returned a response that the plugin couldn’t read as JSON. An invalid API key can cause this: the service returns Error: invalid server key, which produces the error you’re seeing. Could you please check the following? Open oxide/config/VoteSystem.json. Under Vote Servers Settings → RustServers, check API Token. Copy your server’s API key from Rust-Servers.net again, making sure there are no extra spaces. Use the API key, not the server ID. Save the file and run oxide.reload VoteSystem in the server console. If the error persists, please send me your VoteSystem version and the RustServers configuration section, with the API key removed. There’s also an issue on our side with how this error is reported — the message should explain the API failure clearly. Sorry for the confusion!

Hello! I'm really sorry for the late reply. I'll look into your issue today and get back to you as soon as I have a solution. Sorry for the inconvenience!

Hello, That was my mistake. I'll send you a ZIP file with sample configurations and the fixed plugin later today, and then I'll update the plugin. Sorry for the inconvenience!

Hello, We have disabled this feature for security reasons. However, if you'd like, we can re-enable it.

Thanks for the details. You’re correct: no language file is required for general chat translation. In AITranslation Pro 1.1.2, chat translation requires explicit opt-in, which the older version did not require. Please verify that: Both the sender and recipient have aitranslationpro.chat.use. Both players run /ait.chat on. /ait.chat status shows translation enabled for both. The players have different Oxide/Carbon language preferences. The message is sent in global chat; team chat is not translated. If all players use the same language, no translation request is made. You can also disable LangFilesConfiguration.Enabled if you only want chat translation. If it still does not work, please send your plugin version, Oxide/Carbon version, whether BetterChat is installed, and any relevant console error—without sharing your API key.

Hi! Yeah, what's your problem?

Hello, Thank you for your patience. The two issues appear to be different. @Farmer Elias It seems that the procedure for wiping is no longer present in the documentation (I will update it). After a wipe, you need to use the command "votesystem_wipe" (in your server's console). This might resolve your issue. If not, please let me know. @Kaho Your issue seems to be different. It looks like the problem is with the player's nickname ('toaster :3'), likely due to special characters. If the problem persists, I can provide you with a temporary solution. I will update the plugin so that certain special characters no longer cause issues. Best regards.

Hello, Have you downloaded the latest update of the plugin (VoteSystem / CustomRewards)? Regarding SkillTree, I don't think my plugin has any conflicts with it. In any case, I haven't implemented support for this plugin, so maybe you should check with the developer of that plugin. By the way, the logs are quite strange; it looks like a player voted with the name "SkillTreeRegen." I don't have the SkillTree plugin, so it's difficult for me to reproduce your issue Thank you for your feedback, and I hope we can find a solution to get the plugin working correctly for you.

I have successfully fixed the error and I'm ensuring that it doesn't introduce any other issues. I will release an update on 17/07/24 (tomorrow in my time zone), in the afternoon (GMT+2).

I want to assure you that I am still working on resolving the issue. I hope to provide you with an update as soon as possible. Thank you for your patience.

Hi, Thank you for your feedback. I will investigate this week to identify the source of the problem and provide an update. Sorry for any inconvenience caused, and thank you for your patience.

Changed Status from Pending to Closed

Changed Status from Pending to Closed