Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Information about the 1.2.4 Update.
If you need help at any point join our Discord Server and someone will help you.
Dev only Command handler has been added in to enable fast changes to command restrictions.
Lots of little things, nothing of consequence.
!tr history
shows Development History of the bot.
!tr stats server [ServerID]
shows stats for the targets server.
!tr blacklist [ServerID]
Blacklists a server (Developers Only).
!tr unblacklist [ServerID]
un-Blacklists a server (Developers Only).
!tr warn [ServerID]
Warns a server (Developers Only).
!tr unwarn [ServerID]
un-Warns a server (Developers Only).
!tr eject [ServerID]
Removes RITA from the target server (Developers Only).
!tr check [ServerID]
Checks Warn & Blacklist status of the given server.
!tr checkperms [bot/user]
checks permissions of the bot and the user for RITA compatibility.
A new column has been added to manage blacklisting and Warning, backwards compatible to all previous versions.
Once again Zycore broke something (a lot of times) Zycore fixed it again.
Help muenus update with new commands.
Help menus has been reworked, Still a work in progress but they look much better now.
Information about the 1.2.3 Update.
If you need help at any point join our Discord Server and someone will help you.
Environment changes - MESSAGE_DEBUG
- For servers that want to show debug message content to find out what pesky message is causing that error, set this to 1. By Default it is 0. Rita global bot is also 0 and will remain that way.
With the changes to the google-translate-api
it dug up a load of new bugs, Lazarus & EDW have been hard at work fixing them, (DM Lazarus to say thank you, he will love it.)
@everyone
& @here
will now also be conveyed across channels correctly.
Emojis, roles and user pings will now function as intended. With a new system used to manage and correct them
!tr stats global
/ !tr stats server
now show message based stats, take a look.
It working so were not going to touch it. (Well Zycore wont)
Zycore broke something (alot of times) Zycore fixed it again.
All debug messages have been commented out in all files, This make the console log look so much cleaner.
Information about the 1.2.5 Update.
If you need help at any point join our and someone will help you.
db.js has had a overhaul
Database has been migrated to a larger DB, We wont be needing to do that again for a good 5 years.
Color now working in Embed on
and takes user role color.
Stop command for @user has now been fixed
Welcome message added for all new servers. System Channel is default, if not available it will pick first channel that has Write permissions.
Announcement command added, This is Restreicted to DEV ONLY.
Opt in and out commands added for announcements.
!tr settings persist [on/off]
command has been added, this will prevent bot responses from being deleted.
Validation Checks added at startup to avoid Blacklist and Stats SQL Errors
New Debug Settings for console.
MESSAGE_DEBUG
0 - Error's Only
1 - Console for all Messages
2 - Console for Translate Messages only
3 - Content of all Messages
4 - Content of Translate Messages only
5 - Commands Only
Information about the 1.2.0 Update.
If you need help at any point join our and someone will help you.
No Code changes, just URL updates for New name of Bot
Published to NPM
Non code changes will be appended with Version-** from now on.
Various Spelling mistakes in ReadMe have been corrected.
Dev Dependencies core to this bot, the google-translate-api
& google-translate-token
have been updated
Setup on a Raspberry Pi instruction Section added.
gulp-watch updated dependencies. (Moved to Local Repo as it was out-of-date and full of Security Issues.)
Patch for Chinese language support.
Various Security vulnerabilities fixed.
Various commands re-activated.
Information about the 1.2.2 Update.
If you need help at any point join our and someone will help you.
Rita now uses Discord.js V12.
Same channel translation is now working. You no longer need to have multiple channels set up, you can do it all in one channel.
Example !tr channel from english to spanish for #SameChannelMention
Will translate any English messages to Spanish in your current channel
AUTO Translate is now working, you can define the "from" language as "AUTO" and it will detect the language for you.
Example !tr auto to lang for #channel
So running !tr auto to en for #channel
will auto translate anything not in English to English for that channel.
DM Translations have been fixed and enabled, thanks to Artanis and Brozer.
You can enable this by running the following command !tr channel to de from en for @user
That will translate English messages to German for the user. Which they will receive in a DM.
Duplicate language translation bug is now fixed, meaning you can not translate English to English or French to French etc.
Various fixes to Nickname Bugs, this should now be working.
Desktop Client Gif keyboard caused error due to exclusive embed style.
google-translate-api
has been changed to RCP to reduce and mitigate the load limiter.
We have found a way to speed up the translation process, so it should be a little snappier in future.
New commands added (debug
, donate
, prefix
, help commands
, create
)
debug
Is for debug options. Examples below:
!tr debug on
- turns on debugging, creates debugging channel and webhook
!tr debug off
- turns off debugging
!tr stats debug
- prints webhook "ID" and "Token" in channel
donate
- If you would like to donate to RITA you can find the info with this command. Since RITA bot is 100% free donations are greatly appreciated to help with server costs. Examples below:
!tr donate
- Will return donation options
!tr donate github
- You can Donate at Github Sponsors
!tr donate oc
- You can Donate at Open Collective
prefix
- You can now change the prefix of your bot, you can make it whatever you want. Examples below:
!tr prefix
- Will list your current prefix. Default prefix is!tr
!tr prefix $tr
- your prefix would now be$tr
instead of!tr
!tr prefix reset
- resets your prefix back to!tr
So if you changed the prefix to$tr
you would run$tr prefix reset
help commands
- Shows a list of all available commands. Example below:
!tr help
create
- Allows you to use RITA to create a new channel. Example below:
!tr create bob
- will create a new channel named bob
Command Changed (stats global
, stats server
)
stats global
- Stat tracking of messages sent in global servers.stats server
- Stat tracking of messages sent in local server.
Command Removed (settings dbfix
, cpu
)
settings dbfix
- This is no longer needed as DB is repaired (If needed) on each startup.cpu
- It was broken and I have no idea how to fix it.
As the new variables above are stored in the DB, we have made a few changes to how these are handled and they are auto-created upon load. Meaning you no longer need to worry about them again. (If you get any error's please let us know)
Various Security vulnerabilities fixed.
Fixed various issues.
Major code changes
Dev Dependencies core to this bot, the google-translate-api
& google-translate-token
& gulp-watch
have been updated
Information about the 1.2.2 Update.
If you need help at any point join our and someone will help you.
New commands added (embed, bot2bot, settings updatedb)
embed command allows you to change the type of message that is sent to the translation channel, in embed format or standard text. Standard text shows the users avatar and name instead of the bot.
bot2bot allows for messages sent from other bots, in non embedded format to be translated as well. (Due to limitation this has been implimented but is disabled for now)
As the new variables above are stored in the DB, they need new Columns to be added, as such updatedb will complete these actions.
Major code changes, new code implementations will change the DB and produce errors on first build, but this is a safe version to update to. Follow the below instructions.
Step 1: Make a pull request and update from Master branch.
Once you update the bot and it initializes you WILL get a db error, this is normal. (we are working on suppressing these)
Step 2: !t settings updatedb
This will throw another error but it will build the missing columns.
The default value for embed is on and botbot is off.
Running this multiple times will cause error to be posted to webhook chan, this is a "Value exists" error. Preventing you from destroying the DB
Step 3: Completed, and now working.
Once you have completed Step 2, the bot will have come online, but it wont have fully Initialised.
To prevent a never ending loop of errors, the VERY FIRST message or command sent on the server will Initialise the DB fully. Meaning you will have to send that message again.
Please Note Due to the first message after each restart will share the same behaviour as above.
Added in command triggers and command deletion to clean up command channels.
Custom Emoji's are now supported and will be sent with the translated message correctly, with the exception of a few languages.
DM Translation have been disabled as it has been identified they never worked as intended. they will be re-introduced in a later update.
Various Security vulnerabilities fixed.
Dev Dependencies core to this bot, the google-translate-api
& google-translate-token
& gulp-watch
have been updated
eslint
has been replaced with babel-eslint
!t settings updatebot
Has been DISABLED - This is not needed as of yet and with the similarities to the !t settings updatedb
command it may cause issues.
Deploy with Heroku Setup and integration.
Version History for 1.2.?
Information about the 1.2.6 Update.
If you need help at any point join our Discord Server and someone will help you.
Sharding is now automatic, this should auto scale to the needed amount.
A Major memory leak causing rita to restart every few hours has now been fixed.
!tr announce on/off
has been fixed.
!tr settings
has been unrestricted.
!tr blacklist {ServerID}
has been fixed.
!tr channel from {lang} to {lang}
no longer defaults to a DM task.
!tr react on/off
now turns on and off flag reactions.
Added in 3 new columns ready for auto-warn and eject management
Servers will be allowed 10 Permission Errors Before a Warning
Server will be given a Maximum of 3 Warning before they are Ejected
If your server should be Ejected a second time it will be blacklisted
Sooooooo Many spelling mistakes corrected that it would be too many to list here.
Help Menu updated with new commands.