tt2468

package main

import (
	"flag"
	"log"
	"fmt"
	"os"
	"os/signal"
	"io"
	"context"

tt2468

Privacy Policy

The use of this application ("Bot") in a server requires the collection of some specific user data ("Data"). The Data collected includes, but is not limited to Discord user ID values. Use of the Bot is considered an agreement to the terms of this Policy.

Access to Data

Access to Data is only permitted to Bot's developers, and only in the scope required for the development, testing, and implementation of features for Bot. Data is not sold, provided to, or shared with any third party, except where required by law or a Terms of Service agreement. You may view the data we store about you by asking in our #support channel in the counting guild.

Storage of Data

tt2468

obs-websocket API v5.0.0

Redesign Objectives:

• Abstraction of identification, events, requests, and batch requests into new messageType.
• camelCase for all key names.
• Conformity of request naming using similar terms like Get, Set, Get[x]List, Start[x], Toggle[x].
• Conformity of OBS data key names like sourceName, sourceKind, sourceType, sceneName, sceneItemName.
• Error code response system - integer corrosponds to type of error, with optional comment
• Possible support for multiple message encoding options: JSON and MessagePack

tt2468

Salutations

As some of you may have noticed over the past few months, counting has not been very stable. It suffers from lag and constant crashing, and has frustrated many with it.

Believe it or not, we've been working incredibly hard to fix these issues. Multiple valiant attempts have been made to try to fix the issues with counting's stability, but we have reached the limit of the amount of Discord Servers the discord.py library can reasonably handle, and we realized that it was time to grow out of it. It's been multiple weeks of hard programming, but the next edition of counting is now available for beta testing. This means that countingbeta is officially back! This time with the prefix b!.

If you believe you have found a bug, let us know in #questions in the Support Discord

And just like before, anyone who participates in the beta will recieve a free save slot when the rewrite goes live on the real bot.

tt2468

Good evening all

It's been a few days, and we're happy to announce that the first version of the counting rewrite is available for public testing!

We have created a separate bot called countingbeta which uses the command prefix cb! and works in channels called #countingbeta. Count to your collective hearts' desires. If you believe any activity of the bot to be a bug, put it over in #questions in the Discord

And one bonus - Anyone who participates in the beta will recieve a free save slot when the rewrite goes live on the real bot.

You can invite the bot here

tt2468

The problem:

Counting has grown a lot in the past, and with that growth, some fundamental problems have emerged. In order to allow counting to continue growing, we have been rewriting various parts of the bot. Unfortunately, in the process we have identified a few problems that would likely result in data loss.

The options:

Because of this problem, there are 2 possible options.

• Proceed with slowly rewriting the bot, and in the process risk things like votes and counts being completely reset
• Schedule a date to completely reset all data. This gives us the opportunity to do a complete rewrite and fix the fundamental problems with the bot, without worrying about preventing data loss