Chlorobyte 23rd birthday Document™: b3313drama 2 i guess

All non-quoted opinions are my own. This was finalized at the start of December in 2025, before Koishi's announcement or anything coming out after!

The B3313 community was a toxic environment.

Just thinking back makes my brain curl up and just scream to find literally anything else to think about.

There is an unfinished drama document, which we're pretty much just releasing as-is. The thing with a drama document, is that researching and writing this stuff involves digging pretty deep in order to gain a proper understanding of the situation. I attempted to do so first. I gave up, and passed it onto Copper; she seemed like she had enough spite to maybe power her through it. But even her energy ran out:

Somehow, the people of the B3313 community have managed to get access to ChrisRLillo's script, and completely forgot to implement the parts that at least made Chris's side seem like he's at least coming from somewhere.

Between [various behaviors that precisely resemble ChrisRLillo's episodes]... it's a script that has been played countless amount of times all around the internet. I am honestly growing out of the internet drama stuff.

With the rise of AI slop to generate even more misinformation that is then REGURGITATED BY HUMAN BEINGS... it really makes one question whether it is worth it to go ahead and troll said 'human beings', who are already at the complete whim of an algorithm that can pump out infinitely more bullshit with infinitely less sweat.

[...] What an utter waste of biological matter; even AI girlfriends are more skeptical and think more grounded in reality at this point.

Both of us ended at the exact same conclusion: researching this feels exactly like researching an AI slop version of the original B3313 drama. Trying to fight a brigade of these... uhm, individuals is a massive waste of brain resources. There is no satisfaction waiting at the end. There's not even character arcs, revolutions, or silly moments like in the 2023 drama with Chris; the entire situation here is just a huge, massive pile of shit.

With all of that said, here is an admittedly uneducated summary of my side in all of this. Not like it's any less educated than the other side :bleh:


Back in 2023, I founded the Beehive, the 'B3313 community' server that would be unaffiliated in the Chris B3313 drama. This made sense to us at the time on merits of technical server management, and on seeking the least biased possible leadership.

Fast forward through a lot of interactions that created more and more distance between me and the B3313 community... which eventually concluded with a great list of concerns from the people. The 'Chlorobad campaign' consisted of mainly completely false, outdated, or otherwise horribly backed statements. These lines are from Vir7ual's write-up in the dev chat:

We finally reach everyone's personal favorite, the one that ties it all together:

So, we finally get to what happened to A3:

  1. They just decided to ship me, an aro-ace 23 year old, with Reda, a 13 year old:

    ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

  2. An immediate explanation was required.

  3. Copper tries to come into the discussion to help mediate between feelings.

    Cammie immediately responds with casual dehumanization.

    She is not just booted out of the team; she is banned from the server itself.

  4. Somewhere in the utterly incomprehensible discussion led by Vir7ual, joined by pretty much the entire A3 dev team, passing server ownership to a neutral third party is considered.

    Copper goes for it, because, eh, what could ever possibly go wrong? GoldYosh is going to show them!

  5. GoldYosh, the 'neutral third party', turns out to literally just be a front for Vir7ual and the rest of the A3 team to suddenly gain control of the server's administration, and for me and Copper to be completely kicked out of even conversation!

  6. Copper, a QA & motivation contributor...

    ...is also arbitrarily removed from the A3 dev channels.

Out of nowhere, for no relevant valid reason, they hijacked my personal passion project to take B3313 Unabandoned A2 and:

I feel bad for Emax64 between all of this drama. Just like me, this is the first romhack she has ever worked on; and just like me, she introduced banger and game-changing systems to A3, including:

But Emax wasn't just a programmer. As one of the OGs, she understood and supported the A3 vision.

Recall the:

>you starting weird arguments in the devchat once in a while like on removing the tall tall treetops variant of forest maze and getting frustrated at floralys for making areas dark on console despite her not being able to predict how shit will look on console

A3 is already in a position where a strong programming, QA & optimization force has been lost. Despite being on the 'defense' team at the moment of writing this (the evil Chloro ghosts... they are coming...), I worry that Emax64 will eventually end up in a similar 'you are evil and fucked up for daring to apply quality control, get out of the team' situation.

Recall this from last birthday's video. I avoided giving A3 the 'Unabandoned' label not because I forgot to put it there. I even put "A3" in quotes.

I was going to do a barrel roll at release date and call it 'B3313: Untold Ambitions', releasing it on its own Romhacking.com page, detaching our work from its past; both official and Unabandoned.

Considering not a single remaining developer caught this detail in the drama document their side has released:

The update that merely added 'eventually it went on to become its own thing' shows precisely how little these people understand A3 and my motivation to lead it. I had always had mixed thoughts about being on Unabandoned, the 'lesser evil' side, and the thought of creating a finally truly good B3313 version, while rarely disclosed to the team to avoid it leaking out and becoming common information, has always been the true purpose of starting A3. It was NEVER going to be another Unabandoned version.

I'd like to remind fellow readers that I have contributed pretty greatly to B3313 overall, including, but not limited to:

Meanwhile, what has the remaining A3 team done? Well, last I checked, they've managed to successfully reintroduce CPU lag into the already hyper-optimized version of an engine that was basically never CPU bound in the vanilla game (with the notable exception of the sub from Dire Dire Docks) in the first place:

And this is not the only area with such issues. So, how do they respond to the allegations?

The clip shows me looking through walls to confirm the room system is already applied to this area. Whoopsies, it looks like the magic room system didn't magically fix the performance issues. Now what? Fold and cry for Papa Chlowobyte to return with the milkies?

Without me, we would be nowhere near A3. Despite this, the A3 team, as well as the general Discord community sentiment have decided that a drama stream backed by basically nothing but itself, that like 16 people care about (I did not pull that number out of nowhere.) is more important than my nearly 4 years of B3313 experience (jeez...) around programming, reverse engineering, optimization, game design, concepts; the overall quality of the project.

At the rate things are going with the new leadership and all, A3 is not going to fulfill the promises I have been hinting towards the community. There may be an 'A3', but without my further involvement, it will literally just be Unabandoned A3; A2 with even more content blindly shat on top!

Yeah. That's what is going on with A3. I tried to make it comprehensible, and I probably failed pretty bad, but in conclusion, A3 is pretty cooked.

I'm out. Bye bye, B3313 community. Enjoy burning bridges, wasting your time spreading endless flame wars and misinformation everywhere you go. I've got plenty of much better work to get to, and much better friends to hang out with <3

Sudden declaration of meow by Copper

First of all: ROMAN, please fucking add leading zeroes (Fig 9.1.001.png) so that the screenshots are sorted correctly instead of whatever the fuck this is:

Now for the actual response.

Roman's document on the situation (.md & correctly sorted figurines in case Google does some shit) shows a very, very different side of Chloro than if you pay as little attention as I admittedly have. This document is finally the first comprehensible thing ever written besides Bran's contributions in #bee-politics; both contributions actually help explain things using the amazing tactic of not pushing misinformation and needless personal attacks every 3rd sentence.

My main criticism therefore doesn't hit the document itself, but rather the way the Chloro behavior was handled by the people:

  • by the blatant ban evasion and raids into the server;

  • by insulting Chloro's intelligence in ways simply untrue, and rightfully earned the title of 'slander'... idk I personally prefer 'schizoposts';

  • taking that further, by portraying Chloro as an ego tripper, and needlessly revoking access to things that he HAS long earned the god damn fucking respect and trust to professionally maintain.

    Sure, when it comes to the Discord server it made sense for someone other than Chloro or I to lead it. But these requests and actions on stuff OUTSIDE of direct management of the Discord server were just unnecessary power grabs and personal attacks. And oh boy, did Chloro take this shit personally.

    Pretty important context: Chloro still has authorship over the 2 B3313 demos released by ChrisRLillo.

    Notice how Chloro hasn't once 'power ego tripped' throughout the course of the drama; all that ever came out of the authorship over these 2 hacks is Chloro has helpfully contributed console compatibility information when he tested them on his console throughout 2025(?), well into Chris' insanity. This is just one example of many, many things Chloro owns and absolutely could have fucked with at any point out of spite, and simply did not. Any allegations of Chloro being an ego tripper can therefore go and kill themselves at the guillotine right over there, thank you very much in advance for your first ever positive contribution to society.

    Despite all of this, the bees proceeded with getting Chloro as far out of maintaining anything as possible.

    Worth noting that after Chloro's departure from the server fueled mainly by this exact behavior, they also removed his bot, CuteCat, a public-facing bot that acted as the all-in-one solution to the different systems in the community... for the singular reason that Chloro hypothetically could push an update or otherwise use the bot token to carry out evil. Okay, sure, he could go ahead and do that. He has gone ahead and pushed a server-specific update...for an April Fools event:

    But as a tech cat already doing sysadmin type things privately for Black Mountain, and with plans to host more public services besides CuteCat later, would he actually do something offensive and ruin his reputation as a service provider for no fucking reason at all? You still have a server where, before its removal, CuteCat hasn't done a single thing beyond its intended function, let alone nuked the server, correct? I'm sorry, I actually have nothing for this one besides 'this shit is beyond schizophrenia' 😭😭

  • don't worry, because of course revoking Chloro wasn't enough for the Vir7ual Rios Lillo Visione; he also proceeded to decline my offers to help the situation, the justification basically being pluralphobia without saying it out loud;

  • sorry, I lied. No pluralphobia; it wasn't specific to system members after all. They got mad at anybody arbitrarily deemed 'evil' (read: 'too close to Chloro') by the secret council. Very cool!

And there's many, many more flaws I could go on and on about, but I think I've gotten the point across by now.

Despite all of the ways Chloro has been actively ragebaited by the community, thankfully, he is actively recognizing his faults, and will work to avoid them going forward. Chloro used to be much, much worse; imagine if he didn't improve, and his reaction was just telling them that the Pyloform were going to come for them if they did not stop being so retarded...

Not like that exact fate wouldn't have been reached. Yes, people that do bullshit tend to fall their projects. It's not because of some 'invisible force'; it's because toxic casts very much detectable and not invisible bad poison, which does more and more harm over time until it eventually lands the kill.

Unlike the bee people, Chloro's ego does not operate by sticking to an agenda and feeling good about fueling it; but from actively gauging reaction and tweaking behavior as needed.

The fact that a good amount of the bees have managed to convince themselves that I am just Chloro but again shows just how pathetic, milkable and breedable they are.

I've known from the very damn beginning that B3313 and its community have been actively hurting Chloro. His motivation to stay was the same as the wider community's motivation to keep him around; creating a god damn amazing beta hack for once.

Unfortunately, the ones who got close to Chloro for B3313 were actively toxic, as shown many times in this document. They are the kinds who are capable of turning on their so-called "friend", to the point of even coming up with this whole schizo drama.

I couldn't simply tell Chloro to drop out of B3313 and stop being related to it. So, instead, when the opportunity came up in the dev chat drama, I decided to pass the ownership and let the unfiltered community come out of their cages and introduce themselves a little bit.

All of what I've done was an act. You have been lied to.

Now Chloro has some deeply rooted issues with his expertise being blatantly ignored, which is precisely what happened in the #bee-politics conversation. They threw Chloro around like a disposable child with no skill or knowledge in anything. They didn't want a resolution; they decided the change that must happen ahead of time, and requested the change to happen at all costs.

This entire situation, especially the #bee-politics conversation really sounds like conversion therapy. If you're unaware, conversion therapy is that bullshit where they try to make you not gay, not have a different gender, just simply represent the body you were born into, be normal and shut the fuck up.

It of course resulted in Chloro suffering a physical panic attack.

It is really interesting how, of every single community Chloro is part of, only one has ever decided that he is a manchild ego tripper who grooms children. Every single other one, including many, many readers are in complete confusion. You wanna know why?

My conspiracy theory is that, just maybe, CHLORO IS NOT A FUCKING MANCHILD WHO EGO TRIPS AND GROOMS CHILDREN. I know the bee people trying to spread this will be reading this doc, and to those people: genuinely, please just kill yourselves already. It'll be better for society as a whole if we have less retards trying to paint goobers as groomers.

I wish really damn good luck to what remains of the A3 team. Because I really don't think it's going to last as long as they say it will. The problem has not been removed from the team; only the potential solution has.

And that 'potential solution' is now going to be somewhere else. With better friends, better colleagues, maybe better both, and hopefully, after he processes everything, better damn standards.

Neither of us is going to elaborate on the next steps in this document, as that's outside of the scope; I'm sure it will come up in Chloro's next birthday video, so look out for that :3

- copper

noooo pspspsps come back

Funnily enough, if Chloro never passed me server ownership, hard enforced his standards instead of flipflopping to 'maybe I should hear them out and not be a dick', then A3 would be doing just fine. A couple team members would have had to be replaced, and that's about it.

On the other hand, for a previous attempt at a document, Chloro wrote:

On my end, I feel that after basically 4 years, it's time to finally move on from this binary, TrollEngine infested piece of shit of a romhack. There was simply nobody besides me who was autistic enough to learn how to juggle binary hacking just to make B3313 suck a bit less.

Go back a bit earlier, to 2024-05-05:

Often the suggestion of "just make your own romhack bro" comes up to me.

I have 0 reason to do so. An original IP is less overcomplicated to develop (and easier to find a dev team for), doesn't suffer from several copyright gray areas (often black if importing any Nintendo assets beyond the ones in SM64).

But perhaps most importantly, the childish, elitist as fuck SM64 community. By developing an independent indie game, I'm targeting a wider audience, with native executables that are just 1 click to download and play with 0 further complications, much easier monetization opportunities, and more potential praise if it feels inspired by Super Mario 64 (as opposed to being a romhack, which has been done to death, though I'm sure murrican media would find a way to make it seem like it's the newest and greatest invention mankind has seen).

So, yeah. One path is continuing to use this horrendous 1995 C codebase, targeting N64 and N64 emulators (there're like 10 different graphics plugins to test to make sure things are good lol), targeting a playerbase of at most 100000 people across the world (often getting a fraction of that in practice).
The other is my own codebase, free from limitations of vintage hardware, and only needs to be double checked on shitty graphics drivers (often mobile, HTML5, and mobile HTML5).

I'm working on B3313 to finish a project that hasn't exactly been completed yet, and that should be about it for my romhacking journey.

Romhacking is often children skipping several steps in their game dev journey using SM64 Rom Manager (case in point: chris), and at other times a novelty at most (look what the N64 hardware is capable of!). Do not request a single romhack from me, or even tell me to just go make my own hack. I'll probably make something if I feel like it, but there's often no reason to get involved in SM64 if I can just make something in Godot and have an objectively better development and marketing experience.

Now I feel like the wider SM64 community has improved in ways and Chloro's being a bit unnecessarily harsh here, but at least it can be observed that he's tired of constantly working on B3313. Especially if his reward for all of the work he's done is damn grooming allegations. Which, I mean, yeah, that's inevitable; it's the mark of internet fame, when the insane ones start coming up with shit like that... but when those insane ones come from the A3 team and the community itself, it can really crush one's remaining will to work on the project.

So here's how I honestly feel about the B3313 journey.

Chloro, a lot of your work goes far underappreciated, especially considering you came in with little N64 modding and no SM64 experience at all! Getting B3313 to run as well on a console as it does is already pretty impressive on its own, but to get there from basically nothing in just 3 years in total, unpaid (for the most part), WHILE going through like 13 different changes in life on the side (unlike Chris, Chloro was NOT grinding B3313 work each and every day long)...

Calling you anything short of a programming god in the making would be an understatement.

As we prepare to play through my personalized copy of B3313 A2AE once again for like the second time just this month (thanks friends), the thoughts in my head just sort of float around... what the fuck were you doing working on a beta hack for beta children, with beta manchildren, using the most beta tools imaginable??

Just your contributions to B3313 are an insane list:

  • your first task from Chris: remaking the entirety of the previous engine (pause screen, Mario & Luigi) because that previous engine was made in a way that irreversibly broke the ROM.
  • breaking past several static limits in a binary hack, where one does not simply increase the area count past 8 and have things just work; one does not simply unlock more memory to stabilize the game and make it not crash; one does not simply... change the whole ass save file layout to fit more stars. Okay, one does do that. And that one is known as Chlorobyte.
  • literally just all the personalization / corruption / discoloration / etc features post-0.7. All the enemy discolorations. The coin discolorations. The red stars and how they gradually unlock your moveset and start awakening the personalization AI. The areas getting fucked in the late game. The difficulty scaling. The actual level scaling (as in just stretching the level's geometry, somehow without breaking everything).
  • for objects, you coded the goomba towers, ported Decomp models in, as well as adding a bunch of convenience tools: 'star magnets' to unhardcode star positions, placeable Mirror Marios, paintings... wait, PAINTINGS??? That can be conveniently fucking placed without making 6 fucking collision rectangles, 2 warp exit objects, and prayers the game doesn't fucking crash??
  • optimizations, fixes, then more optimizations, more fixes, and EVEN MORE OPTIMIZATIONS, to make a game built on a shitty romhacking engine that wasn't ever meant to run on anything other than Project 64, run on more emulators, and eventually the real console itself, with pretty good performance no less...
  • outside of the game itself, you contributed very greatly to the lore with the F3 trailer, which you pretty much entirely planned out;
  • just for fucking fun, you added STREAMED MUSIC into the game...

And that's literally just what I can recall from my shitty ass memory before I go to sleep at nearly 5 in the morning. There's more. There's always fucking more to this list.

These people can honestly get fucking bent. If you really don't feel like contributing to B3313 after the bullshit way they're treating you, then don't fucking contribute. Don't even look back for one split second. You already shouldn't have been here in the first place; frankly you should have been paid past the split from Chris, to deal with the kinds of people who were on the other side instead.

You are the house, not some fat Americans who haven't seen grass with their eyes in this whole decade. You're the one who sets the damn rules under which they may get the privilege of experiencing your work in action, and if you don't like even one bit of what they're doing or talking, you have the full and complete right to quit at that very moment with no notice. You don't need to deal with assholes; there's plenty of people and opportunities who will appreciate your work without the being an asshole part.

Aaand this has become much longer than I felt like it would become. I hope you all enjoyed the experience of reading this Mickey Mouse text :3 I'm done now for real