DSBot Update Oct`20

It was troublesome typing "general-response start" and "creator-response start" all the time, everyday and everytime heroku resets the dyno. This was the result of the bots old logic. Where the Bot Stance (Public/Private/Personal) determined the Bots User Response.

With the implementation of Environment Response Controls (PR and SR: private messages and server environments) and Command Response Controls (Base/Raw/Social/Admin Command Responses: BCR/RCR/SCR/ACR). User Response Controls (GR and CR: user targetted) seems to be useless all of a sudden. However, there can be uses in the future when troubleshooting is needed.

Thus the old logic of binding Bot Stance to control the User Response Controls is removed. General and Creator Response is now set to true regardless. Filters for Bots running the DSBot script will be verified and split into different levels of classifications:

• None / No Filter

  1. User Response Control: General Response (GR) - non DXC users; to be set to true regardless from now onwards

  2. User Response Control: Creator Response (CR) - DXC users: to be set to true regardless from now onwards

• Filter by if bot is Valid DSBot / Authorised Bot

  1. Environment Response Control: For both Private Response (PR) and Server Response (SR) - Only the infrastructure is implemented, the function has yet to be implemented and there will be a need to wait till it becomes available

  2. Command Response Control: For Base Command Response (BCR) and Raw Command Response (RCR) - Base (with Prefix <> and >< and etc...) and Raw (the UwU and OwO and etc...) will be made available for all only when Bot is Valid/Authorised. As the bots all share these commands and it will be sad if UwU and OwO is gone. The prefixes to send messages via the whisper command (built on logic acquired via the punch and say command) is one of the key features to making the bot a success.

• Filter by Bot Group (MAIN/MISC)

  1. Bot Group is currently not in use as filters as Bot Stance will now handles Social (prefix ><><) and Admin commands. Bot Group will be planned to filter Environment Response Controls in the future.

• Filter by Bot Stance (PUBLIC/PRIVATE/PERSONAL)

  1. Command Response Control: Social Command Response (SCR) will be made available for Bots with Stance: Public only. The ><>< command can be disruptive if 8 bots replied all at once. In the case of the only MainBotHEC going down, the other bots can be activated to have their SCR change from false to true.

  2. Command Response Control: Admin Command Response (ACR) will be made available for Bots with Stance: Public and Private. With this being said, Misc Bots are getting their Admin Commands: OldAdmin and NewAdmin thus the replacement of DXAuth of the Misc Bots DXAuth command to DXAdmin. Again, if PersonalBotDXC is required to activate Admin Commands, its ACR state can be changed from false to true.

  3. With changes to Admin Commands, it is safe to say that in the near future, SUDO commands for Misc Bots DXAuth19 and DXAuth20 will change. With DXAdmin moving down to Admin Command, DXRoot will takes its place, with its name having roots from linux terminals and the root user.

This concludes my logs for this update. If anything else, the redirection sites are changed for the Misc Bots.

Introducing >< and ><>< for DXC DSBots.

The Misc Bots have their own prefixes [xx yy zz aa bb cc] but the Main Bots are limited to '<>' for both MainBotHEC and PersonalBotDXC. Thus changes are required.

MainBotHEC will continue using '<>' as its default prefix. PersonalBotDXC is assigned '><' to prevent prefix overlap resulting in multiple response from different bots.

The raw command '<><>' returns the bot prefix. However, social prefox ()[]{}<> was too long and was thus changed to '><><' without the quotes.

List of incomplete commands are <>shout / <>help / <>ping (ping pong commands):

• Work for <>shout is server channel echo. There are no complete plans on executing that function yet

• Extended function for help needed

• ping pong has been broken for some time as it only takes in one ping or pong but does not take in repeated pings in a single command

• Extra work needed for taking in additional spaces as the commands are split via spaces into string arrays. There is a need to cut the command from the message on commands like ping pong, uwu, whisper/shout/say commands that require bot to output user input minus the commands the in the user input

With that being said: this dev currently in a slump. Till next time.

What happened? Setup Discord Server Connection VIER - Invite link will soon be available.

What problem? On local environment, the scripts can run, the bot responds, and accessing localhost:{port} works. On Heroku, everything works except for the localhost:{port} thing to redirect the visited page to one of the 6 misc bot pages for the 6 misc bots: 

• MiscBot19X 

• MiscBot19Y 

• MiscBot19Z 

• MiscBot20A 

• MiscBot20B 

• MiscBot20C

What changed? All above have been changes revolving around what I have done. Here is what changed:

• Upgraded the <>whisper command:

  • Changed the output. Now it will be able to distinguish between sending to others or sending to oneself. It will react accordingly.

  • Reduced the amount of error outputs. Now, it is not necessary to tag a oneself to send a PM/DM to oneself. Meaning "<>whisper Test" will have the bot send "Text" via PM to you.

  • Tagging other users still follows the default minimum two arguments with the first being a discord tag "<@{string_of_numbers}>" This means the only errors you can get from this command is either the no_args_error or the not_valid_user error - when the user is non-existent (for the bot cache) or is a bot.

• Integrated 4 new SUDO level commands:

  • Base Command Response: all commands that requires a prefix such as "<>"

  • Raw Command Response: commands that require no prefix, like UwU and OwO commands

  • Social Command Response: social links, that can be called using ()[]{}<>

  • Admin Command Response: not implemented yet, this will be when API is implemented in order to enable server level control, unlike SUDO level commads that will affect the bot globally regardless of server

• The merger of codes for the New Misc Bots: 20A (DXChiam), 20B (DXCellon), 20C (DXCC) - The Misc Bots function is built on what a discord bot has and some bad end web archiving service that triggers web.archive.org to save a webpage of the page in the domain. I have spent 2 months spliting the codes and merging them into HEC (Main Bot) and DXC (Personal Bot); where one holds bot functions and the other the backend archive services.

Edit: Information that was missed.