Table of Contents
- Foreword — Why We Are Responding
- Who Is .qroze — Background & Role in the Community
- The Accusers — Satwik / Technocrat & melo: Motive, Coordination & Collapse
- Allegation I — Rape Threats — Context, Culture & What Was Actually Said
- Allegation II — Slurs — Casual Language Among Friends vs. Targeted Harassment
- Allegation III — Racism Against Indians — Banter Disguised as Evidence
- Allegation IV — Real Money Trading (RMT) — Zero Transactions, Zero Proof
- Allegation V — "Semi-Nude Pics to a Minor" — Deliberate Mislabeling Exposed
- The "Misc" Folder — Irrelevant Content Used as Padding
- Summary of Findings
- Conclusion
- Appendix — Original Drive Archive & Proof of Publication
Why We Are Responding
This document was prepared by members of the GUIs Bot development team in direct response to a publicly shared Google Drive folder titled "proofs against roze," which was uploaded with the apparent intent of damaging the reputation of our team member, known in the Discord community as .qroze.
We want to be upfront about who we are and why we are involved. .qroze is not just a Discord user — he is a developer and integral member of our team, someone we work with directly, communicate with on a regular basis, and whose safety and standing in the community matters to us. When a coordinated effort is made to defame a colleague using decontextualized screenshots, deliberately misleading folder names, and fabricated framing, we have both the right and the responsibility to respond formally.
We have reviewed every single file in the uploaded Drive folder. We have traced the origins of each screenshot, identified the individuals involved in compiling and distributing this material, and cross-referenced what is shown against what we know about the nature of those relationships and conversations. What we found is not a legitimate collection of evidence. It is a curated package of in-group banter, private jokes between close friends, and at least one entirely mislabeled folder — assembled by people with documented personal grievances against .qroze and circulated without any fair attempt to obtain his response or provide context.
This document goes through each allegation one by one, presents the relevant screenshots, explains the actual context, and concludes with our formal findings. We also include an appendix with the original archived materials and direct proof of who published this folder. We ask that anyone who received the original "proofs" folder or heard second-hand claims about .qroze read this in full before forming an opinion.
Who Is .qroze
.qroze has been an active and prominent figure in the Discord community since at least mid-2021, with his profile indicating membership since July 2, 2021. Over those years, he built and maintained multiple Discord servers — including Shadow Garden (SG), which at its peak was a genuinely active community. His Discord bio at the time of the screenshots lists him as a developer of GUIs Bot and owner or co-owner of several servers including gg/danker, gg/high5, gg/heistcircle, and gg/homies.
Within Shadow Garden specifically, .qroze held the VIBE role — a senior staff designation. He ran events, managed donations, oversaw partnerships, and was involved in day-to-day moderation decisions. Many of the people he is seen talking to in the screenshots — beans, aash_45, Lag, Visuality, and others — were not strangers or subordinates he was abusing. They were his close friends and fellow admins who had spent years building that community alongside him.
This context is not a minor detail. It is the entire lens through which the conversation screenshots must be understood. The language that flows between people in a tight-knit, meme-heavy Discord admin group looks nothing like the language you would use if you were actually threatening or harassing someone. Both things can look identical on the surface if you strip away everything surrounding them — which is exactly what happened here.
The Accusers — Motive, Coordination & Collapse
Before addressing the allegations themselves, it is important to establish who put this "evidence" together, why they may have done so, and what has already happened to their coalition since they started this campaign.
Technocrat (Satwik / satwikalternate77) — The Compiler
The Drive folder was created and is owned by the Google account satwikalternate77 — which we can confirm is linked to the Discord user Technocrat, whose real name is Satwik, as evidenced by his connected GitHub, Spotify, and YouTube accounts all displaying the name "Satwik" or "Satwixxx" on his Discord profile. His username was also visible as the active admin account in server logs captured in the screenshots (roze16.webp, Shadow Garden message logs).
Technocrat was previously a member of .qroze's clan, Shadow Garden, and was removed from that position after .qroze decided to stop funding him with Dank Memer coins and stripped him of his clan rank. This is a straightforward and well-documented personal grievance. Someone who was removed from a position of privilege within a community that .qroze managed has taken screenshots spanning years of casual conversation and framed them as a misconduct file.
melo — The Informant
melo appears throughout the screenshots as the primary person feeding content to Technocrat and driving the public campaign. The coordination between them is visible in the following screenshot, where melo approaches Technocrat in public and offers a deal before taking the conversation to DMs.
In a public #discussion channel, melo asks if anyone knows "some dank mod" and Technocrat responds "or will i." melo then says "Tell the deal and I give u ur roles" — offering Discord roles in exchange for cooperation — before taking it to DMs. Suggests the two parties aligned to build this case together.
However, something interesting happened almost immediately: the coalition started falling apart from the inside. The following four screenshots show the internal chaos of their own campaign server.
melo created a "Pursue this — Yes/No" poll with only 4 votes, targeting .qroze. Someone confirms "it's technically roze." The fact that a poll was needed at all indicates the group wasn't even unified on whether to proceed.
BulChi openly admits "Yeah and we are yet to get proofs" — His own members telling about not to create a scene and poll etc as such until the proofs have been recieved and so on... BulChi then tells the group to "hold your horses."
Koala discusses a ban in "amigos" and says it would only stick with "solid evidence" on appeal — even members of their own group acknowledged the evidence bar wasn't met. Technocrat sends an attachment in this thread, continuing to feed material into the discussion.
melo publicly announces: "I'm removing Technocrat off admin perms cuz I don't trust him as of now." The two people who built this case against .qroze could not even maintain trust in each other long enough to see it through. melo then immediately runs a coin giveaway — likely to distract or retain server engagement after the drama.
"Rape Threats" — What Was Actually Said
This is the most serious-sounding allegation in the folder. Every single screenshot in this section comes from the #admin-esex channel — an internal staff-only channel in Shadow Garden. The name of the channel itself ("esex" is a well-known ironic meme term in Discord culture for playful, exaggerated banter) signals the tone of the space. This was not a public channel where vulnerable community members could be harmed. It was a private room for the server's own staff.
.qroze tells the channel "So no more raping staff members" and tags @beans (a close friend) with ghost emojis. This is clearly a reference to an ongoing in-joke. No one in the channel reacts with alarm; beans responds "Okay" with a mild emoji. There is no target, no threat, no distress.
.qroze posted "@Staff vote for dank every 12hrs" with a strikethrough on "Or be raped" — the strikethrough itself signals this was written as a joke, not a genuine instruction. This is Discord humor about a server voting reminder, not a policy statement.
.qroze says "I'm gonna rape ur dad" to user Visuality during casual chat. Visuality responds "Hope you feel better, dude and stop, lmao" — laughing it off entirely. .qroze replies "Lol." There is no fear, no escalation, no complaint. Visuality's own response tells you everything about how this exchange was received.
A compiled collage of messages containing the word "rape" across various dates, scraped from over a year of chat history. Many of these are directed at beans and Lag — two of .qroze's closest friends who actively reciprocated this exact style of humor. In several instances the messages are clearly mutual jokes. The fact that this had to be compiled across an entire year to gather a handful of instances tells you how infrequent even that was.
.qroze and Lag are having a warm, casual conversation about thermostats and the cold. .qroze says "Can't wait to rape you" — to which Lag responds "pls do." This is two close friends using hyperbolic banter with each other. Lag's enthusiastic response makes it unambiguously mutual and comfortable for both parties.
.qroze says "I'm gonna rape em I swear" about someone who donated a large amount in a Dank Memer game context. aash_45 responds "Stop raping" with a crying laughing emoji. This is clearly reactionary humor about a game donation — no individual is being targeted with genuine intent.
A Carl-bot message log showing a deleted message by user rose9848 saying "I'll let you rape any staff." It is worth noting that "rose9848" may have been a previous username of .qroze — if so, this falls into the same category as all other instances: a joke made in the same private admin environment, consistent in tone with every other message shown. The message was deleted, which suggests it was considered inappropriate even in the moment. Either way, no complaint was ever formally raised about it.
Slurs — Friends Talking vs. Targeted Harassment
The "slurs" folder contains screenshots of .qroze using the n-word and the r-word in what are clearly casual staff conversations. We are not here to argue that these are words people should use carelessly. But there is a significant difference between using rough language in a private admin channel with your close friends — none of whom complained about it — and engaging in targeted racist or ableist harassment. This folder documents the former, not the latter.
.qroze uses a slur mid-conversation in #admin-esex while discussing server roles with beans. Nobody in the channel flags it, calls it out, or shows offense. This is a private admin conversation. It was never brought to .qroze's attention as a problem by anyone present — until it was quietly screenshotted months later.
.qroze uses casual language in conversation with Lag. Again, Lag does not react negatively in any way — this is the same Lag who throughout all these screenshots engages in identical styles of banter with .qroze.
.qroze says "What a retard" in reference to a server owner who reportedly stole ownership of a server. This is a reaction to a third party's behavior, not directed at any person present in the conversation.
In #partnership-logs, .qroze says "Don't let this retard lie he's owner" — referring to a third party (Frosty) who was misrepresenting their server ownership status. This was said in a server management context, not as personal abuse toward anyone present.
.qroze refers to certain server members who keep pinging a user as "retard members" — an expression of frustration in a staff context, not targeted harassment of any individual. aash_45 agrees with the assessment.
Racism Against Indians — Banter Among Friends
Three screenshots are presented under this heading. None of them involve a stranger being attacked. All of them involve .qroze talking with people he knew — and in at least one case, the conversation involves someone who was actively playing along.
Beast02 himself introduces the topic of Indian roads and supercars. .qroze responds with a roast-style comment. Beast02 does not object, report, or show offense. This was a two-way exchange, not a one-sided attack.
In a private DM conversation with melo, .qroze makes a joke about trampolines and India. This is a private DM between two people who were, at that time, close enough to be chatting casually. Notably, melo — who later became one of the primary accusers — did not flag this as offensive when it happened. He laughed and engaged.
The continuation of the same DM — .qroze sends a photo as part of the same joke. melo's responses show active engagement with the humor, not offense. If melo genuinely found this racist, this was the moment to say so. He chose not to.
The screenshots labeled "racism against Indians" were taken from a conversation with melo — one of the two people compiling this case. The fact that melo participated in and responded positively to these exact messages, only to later submit them as evidence of racism, is telling. It suggests the accusation is opportunistic rather than sincere.
Real Money Trading — No Transaction, No Proof
RMT — Real Money Trading — refers to exchanging in-game currency for real money, which violates the terms of service of most gaming bots including Dank Memer. This is the only allegation in the folder that, if true and documented, would constitute an actual rule violation. The problem is: it is not documented.
A Discord search showing 12 results for "rmt" in messages by .qroze. The visible messages include "Bn rmt clan?" and "Also I know for a fact Kyoki doesn't rmt." These are not evidence of .qroze conducting RMT — they are evidence of .qroze discussing the topic, which anyone in an active Dank Memer community does regularly. Notably, one message has .qroze defending someone else against an RMT accusation.
melo is the one who initiates the RMT conversation, asking "Can we rmt? Cuz we poor." .qroze responds saying he has no money at the moment. This is melo soliciting .qroze — not .qroze running an RMT operation.
The conversation continues with .qroze saying he has no money in his account right now but could potentially help in a few weeks. The conversation ends there. No transaction ever takes place. There are no payment confirmations, no Cash App records, no screenshots of any exchange — nothing.
"Semi-Nude Pics to a Minor" — Deliberate Mislabeling
Of all the manipulative choices made in assembling this Drive folder, the naming of this subfolder is the most egregious. The phrase "semi nude pics to a minor" is designed to trigger an immediate and severe reaction in anyone who reads it. It implies child exploitation. It is a label engineered to cause maximum reputational damage before anyone has even opened a single file.
Here is what the folder actually contains.
melo calls .qroze "a fucking kid." .qroze responds "No / It's old." After some more banter about a trampoline, .qroze sends a shirtless selfie — almost certainly to prove he is not a kid. melo responds with jokes about ribs and the conversation continues casually. There is no minor. There is no exploitation. There is nothing remotely concerning here beyond two friends joking around in a DM.
The conversation continues with melo commenting on the photo and .qroze responding. The exchange is entirely typical of two adults who are comfortable friends. Worth noting: melo himself uses a slur in this very conversation — the same melo who compiled slur evidence against .qroze.
Finding: This folder name is a fabrication.
There is no minor involved in any of these images. The folder contains a completely normal DM exchange between two adult friends. Whoever named this folder "semi nude pics to a minor" did so knowingly and deliberately, understanding that the name alone would cause harm to .qroze's reputation regardless of the actual contents.
This is not an honest labeling mistake. It is a calculated act of defamation. Anyone reviewing this case should treat this folder naming decision as direct evidence of bad faith on the part of whoever compiled and uploaded this Drive folder.
The "Misc" Folder — Padding with Irrelevance
The miscellaneous folder contains four files. None of them constitute meaningful evidence of wrongdoing by .qroze.
A Carl-bot log showing a deleted message by "rose9848" saying "Send nudes for bypass" in a giveaway channel. .qroze's visible response is "Ong who deletes @beans" — he is reacting to the deleted message, not participating in it. Also visible is an edited message by rose9848 about sliding a voter role — again Including this as evidence against .qroze without main context is intellectually dishonest and an attempt of forging friendly chat as a proof of character.
A Carl-bot message log from July 2022 showing deleted messages by "Me Short#6969" — a completely different user. The content references "a man getting his head shot" and "irl." .qroze is not the author of these messages. Their presence in a folder of evidence against .qroze is baffling unless the intent was simply to pad out the folder with alarming-looking content.
.qroze posts a photo of graffiti on a garage that says offensive things and includes symbols associated with hate groups. He captions it "Bro." This is someone reacting to something they presumably saw — sharing it with their server as a "can you believe this" moment. There is no indication .qroze created or endorsed the graffiti.
A Discord search result showing .qroze posted a Roblox prison meme in 2022. Including a meme from over three years ago in a misconduct report compiled in 2026 is indicative of how thin this evidence base truly is.
Summary of Findings
The following table summarizes our review of every allegation in the Drive folder against .qroze:
| Allegation | What Was Claimed | What Evidence Actually Shows | Finding |
|---|---|---|---|
| Rape Threats | Threatening sexual violence against staff/users | Hyperbolic banter in private admin channel; recipients laughed or reciprocated; no complaints ever filed | Unsubstantiated |
| Slurs | Using racial and ableist slurs in harmful way | Casual language in private staff channel; no one in the conversation complained; compiler screenshotted in silence for months | Decontextualized |
| Racism Against Indians | Targeted racist harassment of Indian users | Jokes in DMs with melo, who actively participated and laughed; melo later submitted same conversations as evidence | Opportunistic / Bad Faith |
| RMT | Conducting real money trading transactions | melo solicited .qroze; .qroze said he had no money; no transaction ever took place; zero financial records provided | No Evidence of Transaction |
| "Semi-Nude Pics to a Minor" | Sending sexual content to a minor | Two adult friends joking in DMs; one shirtless selfie sent after being called a kid; no minor involved whatsoever | Deliberate Mislabeling |
| Misc Content | General pattern of misconduct | Contains messages from entirely different users; a 2022 meme; a photo of graffiti .qroze was reacting to | Irrelevant / Misleading |
Our Position
We have gone through this material as thoroughly as any reasonable review could. What we found is not a credible misconduct report. It is a collection of screenshots taken from years of private staff conversations between friends, stripped entirely of context, labeled with deliberately inflammatory names, and distributed by two individuals who had documented personal and professional reasons to want .qroze's reputation damaged.
The person who named a folder of casual DM screenshots "semi nude pics to a minor" knew what they were doing. The person who admitted "we are yet to get proofs" mid-campaign was not acting in good faith. The person who offered Discord roles in public channels for cooperation and then turned on their own ally was not driven by principle. These are not the actions of people with genuine safety concerns. They are the actions of people running a smear campaign.
.qroze is a member of our team. He is someone we work alongside, communicate with regularly, and vouch for. We have seen the material that was assembled against him, we have read every conversation, and we are confident that none of it constitutes evidence of the kind of misconduct it was framed to represent.
That does not mean .qroze has never said anything rough or used language that some people would find uncomfortable — the screenshots make clear that he has, in the same way that many people in this kind of community do, among close friends, in private spaces. But there is an enormous difference between that and what was alleged. And the gap between what was alleged and what was actually shown is the story here.
We are asking anyone who received or acted on the original Drive folder to review this document, consider the full context, and where applicable, revisit any decisions made solely on the basis of that folder's contents.
Official Position of the GUIs Bot Team
We stand behind .qroze. We have found no credible evidence of genuine misconduct in the submitted material. We have, however, found clear evidence of coordinated bad-faith activity by the individuals who compiled and circulated the "proofs against roze" folder.
We call on any server, moderation team, or individual who received this material to treat it with the skepticism it deserves, and to afford .qroze the opportunity to present his own account before any permanent action is taken against him.
This document, and the evidence it contains, stands as our formal response.
Proof of Publication — Drive Archive & Identity
This appendix exists for one reason: to ensure that the individuals responsible for this smear campaign cannot later claim they were not involved, that the folder was not publicly shared, or that its contents were different from what is documented here. The following screenshots were captured directly from the Google Drive folder at its publicly accessible URL and show both the folder structure and the identity of the account that owns it.
The Google Drive folder "proofs against roze" and all its subfolders — including the deliberately mislabeled "semi nude pics to a minor" — are owned by the Google account satwikalternate77. All folders were last modified on March 13, 2026, confirming this was a recent and deliberate upload. The owner's email is [email protected].
The Discord profile of Technocrat shows connected accounts: GitHub username "Satwixxx", Spotify username "Satwik", and YouTube username "satwik" — all matching the "satwik" in the Google account satwikalternate77. His Discord profile also shows he is the owner of discord.gg/elegants and discord.gg/therich, is a Developer of Forge, and joined Discord on June 18, 2024. This conclusively links the Drive folder owner to the Discord user Technocrat.
📦 Original Evidence Archive
The complete original zip archive of the "proofs against roze" Google Drive folder is attached below for full transparency. This is the exact file as downloaded from the public Drive link, unmodified. It is included here so that any reviewing party can verify that our analysis above is accurate and that no files have been added, removed, or altered.
⬇ Download Original Archive (.zip)This document was prepared in March 2026 by the GUIs Bot development team. The Drive folder referenced herein was publicly accessible at the time of this writing at the URL shared by the account [email protected]. All screenshots in this document are reproduced for the purposes of counter-evidence and fair response to public allegations.