ScarDocs
Ask or search…
K
Links
🤖

Old Bots

Let's take a trip down memory lane to explore the evolution of Scar.
From failure to resilience, Scar's story is marked by setbacks and triumphs. Born in a realm of challenges and learning, Scar emerges as the embodiment of persistence and the pursuit of perfection.
See below all the older brothers of Scar
RamboBOT
BlackBot
StayNight
ElixirBot
Scar

RamboBOT

RamboBOT Avatar

History

The genesis of this extraordinary journey traces back to August 18, 2018. It was a day like any other when curiosity led me to stumble upon a captivating YouTube video on creating Discord bots (out of curiosity, the video was this).
Intrigued by the possibilities, I decided to take a leap of faith. With each step meticulously followed, my passion ignited as I delved deeper into the realm of bot creation.
Fueling my ambition further, I ventured into the YouTuber's server, seeking guidance in bringing my vision to life. There, amidst the bustling community, an invaluable ally emerged. He extended a helping hand, and together, we embarked on an exhilarating collaborative journey.
Thus, RamboBOT materialized, forever etching its name in the history. What began as a humble experiment blossomed into a testament to determination and creativity. Little did I know that this first step would pave the way for remarkable innovations and astounding achievements to come.

What did the bot do?

Initially, RamboBOT had modest functionalities, grappling with an abundance of bugs 🐛. Developed on DiscordJS version 11 and fully Portuguese, my native language, the bot possessed a repertoire limited to basic moderation commands and a sprinkle of entertaining features. While its capabilities were somewhat constrained, RamboBOT served as a stepping stone, paving the way for future growth and refinement.

Why it ended

Unfortunately, RamboBOT's journey came to an untimely end due to an unforeseen incident.
As a novice in the field, I inadvertently exposed the bot's token, leaving it vulnerable to malicious actors. Consequently, the bot fell victim to hacking, resulting in indiscriminate spamming across multiple channels.
And you say, "just reset the token!" Yes, that's true but the overwhelming shock and confusion led me to make a hasty decision. Filled with a sense of dismay and frustration, delete RamboBOT, bidding farewell to a project that held both promise and lessons learned.
This being the case, I leave a tip to everyone who also develops a bot, or any other application: be very careful with your passwords, how you store it and with whom you share it.

BlackBot

BlackBot Avatar

History

On January 1, 2019, RamboBOT's journey came to an end. However, the passion for bot creation persisted, driving SirRamboia to embark on a new endeavor.
You can see the story of SirRamboia, the creator of all these bots here:
In the early months of 2019, the second bot was born, bearing the name BlackBot. This time, a stronger focus was placed on implementing robust security practices. Alongside a wealth of additional commands, an informational website was created to enhance the user experience.

What did the bot do?

BlackBot retained its language support solely in Portuguese (native language of SirRamboia), but it offered a more extensive array of commands and operated with significantly fewer bugs than its predecessor. The development process also prioritized the creation of an informative website to provide users with essential resources and guidance. Additionally, the support server for BlackBot received heightened attention, ensuring that users' inquiries and concerns were met with swift and helpful responses.

Why it ended

As BlackBot gained popularity and its user base expanded, it eventually reached a crucial milestone — bot verification at 75 servers.
Unfortunately, this milestone also marked the beginning of a challenging chapter in BlackBot's journey. The bot verification process confronted an array of servers that were solely occupied by bots, some with thousands of bot members and others with only two members: the creator and the bot itself. This disproportionate distribution of servers led to BlackBot being swiftly rejected for "Inorganic Growth" without the opportunity for a second review. Despite the bot's legitimate growth, these anomalous server patterns resulted in an unfavorable outcome, ultimately leading to the cessation of BlackBot's operation.
The story of BlackBot serves as a reminder of the complexities and challenges developers may face in navigating the intricacies of bot verification. Despite its untimely end, BlackBot's impact on its user community and the valuable lessons learned during its development continue to influence future bot creations.

StayNight

StayNight Avatar

History

On July 1, 2020, after the unfortunate end of BlackBot, I was determined to create another bot that could surpass its predecessor.
This led to the birth of StayNight, a bot with even more features and functionalities. The vision for StayNight was to provide users with a powerful and comprehensive experience, complemented by a beautifully designed website (using NicePage kekw) and a dedicated team that was gradually forming to support its development.
The StayNight website, based on NicePage is public, you can find it here:

What did the bot do?

StayNight inherited the core functionalities of BlackBot and expanded on them significantly. It was designed to be a versatile and efficient tool, capable of performing a wide range of tasks to meet the diverse needs of its users.
As the community grew, so did the pace of updates. We took pride in actively listening to our members' feedback and suggestions, promptly addressing issues, and implementing new commands to enhance the overall user experience. StayNight was becoming a beloved companion for many Discord servers, steadily carving its path towards success.
However, little did we know what awaited us...

Why it ended

Despite our best efforts, StayNight's journey eventually came to an abrupt and disappointing end. The bot faced the same fate as its predecessor, BlackBot, and was taken down due to concerns of "Inorganic Growth" upon verification.
Regrettably, we were denied a second review, leaving us without the opportunity to resolve any misunderstandings or rectify potential issues. It was disheartening to see the bot, which we had poured our passion and dedication into, being removed without a fair chance to prove its legitimacy.
This unforeseen setback left a sense of incompleteness in the story of StayNight, and it remains an unfortunate chapter in the bot's history.
As we bid farewell to StayNight, we carry the valuable experience gained from its creation and journey, which will undoubtedly shape our future endeavors.

ElixirBot

ElixirBot Avatar

History

On January 1, 2021, ElixirBot took on the challenge of bot creation once again. This time, the bot's development was accompanied by a brand new website, a dedicated support server, and an expanded repertoire of commands.
Establishing partnerships with prominent servers played a significant role in ElixirBot's growth, allowing it to gain recognition and attract users more organically and swiftly. This approach was a response to previous difficulties faced during bot creation, ensuring a more strategic and promising trajectory for the new bot.

What did the bot do?

Through its partnerships with large servers, ElixirBot identified an intriguing opportunity to innovate and stand out in the bot landscape. These servers had multiple bots, each catering to specific tasks. ElixirBot sought to revolutionize this by providing a single, high-quality solution that could perform all the functions offered by those separate bots.
By consolidating various features and offering them with top-notch quality, ElixirBot aimed to be the ultimate multifunctional bot for users.

Why it ended

ElixirBot's growth exceeded expectations, signifying apparent success. However, this rapid and substantial growth eventually became a significant issue.
During the bot verification process, ElixirBot was flagged for "Suspicious Growth", causing concern among the Discord Team. The bot was granted a second review, with a suggestion to wait for one month to observe a more normalized growth pattern. Following the advice, ElixirBot managed to amass 99 servers before reaching the verification cap. After one month, the developer contacted the verifier again, hopeful for a favorable outcome. However, despite the apparent normalization of growth, the verifier surprisingly and irrevocably disapproved the bot, citing persistent suspicions.
The unexpected rejection left me feeling frustrated and disheartened, as there seemed to be no alternative path forward. The decision to delete the bot was made, as it appeared to be an unfortunate waste of time and effort. However, amidst the disappointment and contemplation, a new glimmer of hope emerged...

Scar

Scar Avatar

History

Finnaly, at December 1, 2021, the moment had arrived! Armed with donations, I took the initiative to invest in the bot's future by acquiring a domain and hosting services. The journey began with a complete overhaul of the bot's codebase, aiming for improved practices, enhanced performance, and the introduction of new and better commands.
However, I learned from past experiences and approached server selection more cautiously this time. Before reaching the verification stage, I diligently monitored the servers the bot was joining. When the count reached 75 servers, I proactively removed 37 servers that had either fewer than 20 members or a bot-to-member percentage surpassing 40%. By doing so, I fostered a more organic and supportive environment for the bot, allowing meaningful connections to develop within the community over time.
It took over 6 months to reach 75 servers, but it was worth it.
On May 5, a date that holds immense significance for me, the bot's verification finally materialized. This marked a remarkable moment, as it symbolized over three years of unwavering determination to create a bot that could genuinely aid and support the community. After enduring five failed attempts, the bot was now verified, granting it the opportunity to fulfill its intended purpose and serve its users to the fullest.

What did the bot do?

Following the successful verification, my commitment to the bot's growth intensified. Recognizing the importance of inclusivity and expansion, I introduced a comprehensive multilanguage system, enabling the bot to cater to users from different countries. Moreover, the website underwent a complete transformation, enhancing accessibility, and user-friendliness.
Check out Scar's website here:
This fresh approach opened up exciting possibilities for the bot's future, as it could now connect with users across linguistic and cultural boundaries. The diverse functionalities and improved web presence aimed to create a more welcoming and adaptable space, ensuring that the bot remained a valuable asset to the ever-evolving needs of the community. With the journey still unfolding, the bot's capabilities and impact were set to expand even further, guided by a passion for assisting and supporting users in their diverse pursuits.

Why it ended

🔥 Scar will never end!