INTRO

What began as a promising Roblox kaiju game has spiraled into a deeper story of manipulation, intimidation, and questionable legal practices. Kaiju Revolution, led by Solaria Interactive and its owner “Ancient,” has been at the center of growing controversy involving the exploitation of minor developers, misuse of assets, and inconsistent claims surrounding its supposed endorsement by Toho.

This document dives into the full timeline, key players, and most recent developments, including the revoked Titan Genesis contract, the mishandling of legal boundaries with minors, and the contradictory statements about their ties to Toho. With testimonies, documentation, and legal insight, this case lays out the facts behind a game community caught in corporate overreach and control.

This isn’t just about a game, this is about protecting young creators and holding companies accountable.

Concord and Ancient, if you have found your way to this document, have fun trying to fight back these cases which are all evident and thoroughly explained here.

CASE 1 - KAIZAGIDORA

Case 1 – The KaizaGidora Dispute: Promises, Reimbursements, and Contradictions

One of the most revealing cracks in the foundation of Kaiju Revolution lies in the story of its former project manager, KaizaGidora, a content creator with over 50,000 subscribers. Kaiza was a central figure in the game’s early development, coordinating tasks, managing community expectations, and even paying developers out of his own pocket, demonstrating a clear personal and financial investment in the project. However, despite this commitment, Kaiza was abruptly removed from the team. Screenshots confirm that the owner of KR promised Kaiza reimbursement for his contributions, seemingly acknowledging the weight of his efforts. But this story takes a sharp turn when Kaiza later spoke with Concord Legacy, the co-owner of the game. In direct contradiction to the previous promise, Concord flatly denied that reimbursement was ever agreed upon. This inconsistency not only exposes dysfunction within the leadership team, but raises serious questions about how contributors, especially those who help carry the game in its early stages, are treated behind the scenes.

Following his removal from the Kaiju Revolution team, KaizaGidora received a written promise of compensation from the game's co-owner Concord: 170,000 Robux, acknowledged explicitly in a formal message signed as Chief Operating Officer of Solaria Interactive. While the statement may have seemed like closure, it quickly became clear that it was anything but.

In a conversation dated a month later, a mediator named Duke confirmed he had met with Ancient, the other owner of Kaiju Revolution. Duke relayed that Ancient still “intended to pay” Kaiza, but only when he was ready. What followed was a pattern all too common in amateur or disorganized development circles: silence. Over the course of several weeks, Kaiza respectfully followed up, asking if there were updates or any progress. The replies were either vague or nonexistent. By late May, Kaiza had waited two full months, still unpaid, still ignored.

The reimbursement promised on paper had effectively vanished, replaced by indefinite delays and corporate silence. For someone who had managed the project, paid developers himself, and promoted the game to his large audience, this wasn’t just unprofessional, it was disrespectful.

As Kaiza continued to wait for the compensation promised to him, the situation took another disturbing turn. After weeks of silence and delays, Concord backtracked, this time, not by avoiding the payment, but by changing the meaning of it altogether.

In direct messages, Concord would eventually claim that the 170,000 Robux initially promised wasn’t reimbursement at all, but merely “good faith money.” A token gesture, not a repayment. This stands in complete contradiction to the original written message, where Concord had stated plainly and boldly that Kaiza “will be compensated for your work” and even cited a specific amount.

This shift in language reveals more than just miscommunication; it shows a calculated attempt to redefine an obligation as a favor, to dodge accountability and minimize the contributions of someone they had already removed. When a developer who poured personal funds and time into a project is not only unpaid but also gaslit into believing that their compensation was never official, it raises serious ethical concerns about how Kaiju Revolution treats its collaborators behind closed doors.

After months of silence and delays, the situation took an even steeper turn. Instead of addressing the unpaid promise privately, Concord chose to attack Kaiza publicly, this time, in a completely unrelated Discord server for another development group, Prometeo Games.

In front of a public audience, Concord stated:

“You lied to the community, you lied to us. You bring drama to other servers. You have been told that it was going to be in good faith, but you went around spreading false information. We paid you for your completed work and are not obligated to anything else.”

This public outburst directly contradicts Concord’s original written statement, where he had said clearly:

“You will be compensated for your work – 170,000 Robux.”

Rather than resolving the issue professionally or privately, Concord chose to recast Kaiza as dishonest, labeling his calls for reimbursement as “spreading false information.” Not only is this unethical, it's retaliatory. It’s an effort to undermine Kaiza’s credibility, shift blame, and rewrite the narrative in front of others, despite existing proof that supports Kaiza’s claims.

When developers resort to public shaming to silence former team members who ask for what they’re owed, it tells the community more about the leadership than it does about the person being targeted.

CASE 2 - MAYURA

Case 2 – Weaponizing Out-of-Context Accusations: The Firing of Mayura

Another staff member wasn’t just fired from Kaiju Revolution’s Discord server, he was publicly shamed using a series of extreme accusations, many of which were either wildly exaggerated or outright misrepresented. The individual in question? Mayura, a young contributor who was only 14 at the time of many of the so-called “incidents.”

The allegations used to justify his removal included:

  • Use of a racial slur in a private setting with friends
  • Making a comment interpreted as promoting zoophilia
  • And jokes mischaracterized as referencing human trafficking

But Mayura provided context that tells a very different story. Regarding the slur, it was used in a non-hostile, friend-only space, and not with malice. On the zoophilia claim, the accusation stemmed from a joke about a Minecraft horse-breeding facility created by a friend, something clearly satirical. And as for the trafficking comment, Mayura admitted he had no idea where the claim even started, noting that it may have stemmed from a joke misread as a reference to Andrew Tate, again, within a private server meant for jokes among friends.

When game leadership and affiliated developers take satire and inside jokes from friend servers and weaponize them as grounds for removal, without providing proper context, they aren’t enforcing standards, they’re creating a tool for character assassination. This is especially damaging when the individual being punished is a teenager, and when the evidence is later proven to be flimsy or manipulated.

The case of Mayura reflects a larger pattern: one where Kaiju Revolution’s leadership appears more focused on erasing dissent and silencing controversy, than on transparency or fairness.

In perhaps the most reckless twist, the Kaiju Revolution staff  team or its affiliated staff accused Mayura of supporting or joking about incest and pedophilia. These are charges that can permanently damage someone’s name  especially in digital spaces.

But once again, the facts paint a very different picture. Mayura states clearly:

“I had expressed my own condemnation of lolicon culture some time ago in the server. Even though I was firmly against it, they somehow took a message of mine and interpreted it as joking about it.”

This wasn’t a case of edgy humor or careless language , this was a blatant twisting of a serious stance against exploitative content. The mere fact that an anti-lolicon message could be reframed as support for that content shows a dangerous level of narrative control by the people who fired him.

Weaponizing an accusation like this especially toward a minor with no clear proof, and in the opposite context of what was intended, is more than just irresponsible. It’s defamatory. It shows how far the team was willing to go to justify an unjust removal even if it meant falsely branding someone with one of the most serious labels imaginable.

CASE 3 - ALLISTER

Case 3 – Manufactured Accusations: The Targeting of AllisterTheWendigo

The Kaiju Revolution staff purge continued with another wrongful dismissal, this time targeting AllisterTheWendigo, a contributing team member accused of “stalking” a fellow moderator’s social media account. But once again, the facts show a narrative built not on truth, but on grudges and distortion.

Allister describes the situation:

“I was accused of stalking the social media account of another mod. Who exactly made these accusations? It was more or less likely a person who goes by Ace. They basically hated me, I would say. Reason being that I overdid some jokes in a private server with a group of friends, you [???] were in there for a bit, if you recall.”

That alone points to a personal grudge rather than objective misconduct. But the situation escalated further when a suspicious Instagram account, one that appeared to be a renamed alternate account, followed the user “Ace.” The implication was clear: Allister was still watching or harassing from a hidden profile.

But here’s where the smear falls apart:
Allister recorded and submitted video evidence proving that he has no Instagram alts, only his main account. The footage clearly shows no secondary profiles, no alternate logins, and no link to the suspicious account. Despite this, the rumor was used to isolate and damage his reputation inside the community.

This wasn’t a misunderstanding, it was an intentional association, meant to imply predatory behavior from a false lead. When the accused provides concrete evidence debunking a claim, and the leadership still moves forward with exclusion or punishment, it shows that the goal was never truth, it was removal.

Allister’s experience reveals how easily social weaponization can replace due process in amateur development spaces. With no investigation, no effort to verify, and no protection against personal vendettas, contributors can be publicly labeled and discarded with ease.

Mid Doc Highlight - Obie and his lies

At a key point in the project’s history, another piece of evidence emerged that brings the Toho licensing controversy into sharper focus. In a private Discord DM exchange with Kaizagidora, former Kaiju Revolution owner Obie made a bold and direct claim:

“We have a license and have been talking with Toho since 2021.”

This wasn’t vague, theoretical, or hedged. Obie presented the existence of a Toho license as an established fact.

But when Kaiza reasonably asked for proof, even something as simple as a redacted confirmation or a summary of terms, Obie responded:

“The game release will be proof.”

That’s not proof. That’s deflection. A game’s launch says nothing about the legal permissions behind it, and in fact, launching a game without a license can be grounds for legal takedown. If a license truly existed, a formal agreement or even acknowledgment would’ve been easy to present, especially to a core staff member.

This moment is telling: rather than provide documentation, Obie pushed the goalpost forward. And even after release of testing, no public proof of licensing ever followed.

CASE ??? - Toho Co. Ltd and Brands.

Case 4 – The Licensing Lie: False Claims of Toho Approval

Perhaps the most dangerous claim made by Kaiju Revolution leadership was also the one that brought it the most attention: a supposed official license from Toho, the legendary Japanese company behind Godzilla and other kaiju. In early conversations, Ancient — the owner of KR, told project manager Kaizagidora directly:

“Yes [I’ve seen the license] and I speak to Toho regularly. Obie isn’t the one that does that.”

This was not framed as speculation or hope, it was stated as fact. But no license document was ever shown, even to senior staff. And more importantly, Toho has never publicly confirmed such a deal, which is highly unusual for a company known for publishing and promoting every legitimate licensing partnership it enters, even under NDA.

Over time, the story shifted. The once boldly-claimed “Toho license” was gradually reframed as just an “endorsement”, then even less. No paperwork, no public announcement, and no legal acknowledgment of Solaria Interactive, the supposed holding company behind KR.

Meanwhile, these licensing claims were actively used to gain player trust and promote the game’s pre-release testing, during which millions of Robux were generated. If no official license exists, then these actions amount to more than just exaggeration, they represent a clear-cut case of misleading marketing, false representation, and potentially fraud.

To this day, no documentation or credible third-party confirmation has been presented. Just a cycle of bold statements, walking them back, and hoping no one asks again.

 Background – How Toho Actually Handles Licenses and Endorsements

Toho Co., Ltd. is not just the owner of the Godzilla franchise, it's one of the most strict and formal licensors in the global entertainment industry. The company has a long history of licensing deals with international brands, game developers, studios, and merchandise creators. And nearly every one of these deals is publicly confirmed.

When Toho enters into licensing or endorsement agreements, whether for mobile games, console titles, figures, clothing, or film collaborations, they do not operate in silence. Partners like Netflix (Godzilla Singular Point), Legendary (Godzilla x Kong), and gaming companies like Byking (Godzilla Battle Line) or WayForward (Dawn of the Monsters) all had Toho’s name prominently shown in:

  • Official trailers
  • Press releases
  • Partner websites
  • Licensing announcements posted on Toho’s official social media or news pages

Even in cases where NDAs may delay asset reveals, Toho never silently licenses a major IP to unknown or unaffiliated indie teams without corporate visibility or disclosure. To date, no public-facing Toho platform, Japanese or English, has ever mentioned Kaiju Revolution, Solaria Interactive, or any affiliated developer.

In short: if Toho was truly involved, we would know. Their licensing and brand protection processes are visible, documented, and legal. The complete absence of public confirmation from Toho speaks louder than anything KR leadership has said.

CASE 4 - VOID AND TG

 Case 5 – The False Partnership: How Kaiju Revolution Bought Titan Genesis, Then Rebranded It for Profit

In 12/31/24, Kaiju Revolution’s leadership claimed it had formed a partnership with another kaiju-themed Roblox game: Titan Genesis. The announcement framed it as a friendly collaboration, sparking excitement in both communities. But that narrative was entirely false.

Behind the scenes, no partnership existed. A contract obtained from the original developers of Titan Genesis, Void and his co-owner, reveals the truth:

“??? and [REDACTED] are giving full rights of Titan Genesis to Kervin Sincere in return for 300,000 Robux, as said in 3.1 of the contract, this includes all code, models, animations, scripts and any and all assets associated with Titan Genesis.”

This was a complete asset buyout. Every aspect of the game, the codebase, animations, scripts, models, was sold outright to Kevin Sincere, the acting lead of Kaiju Revolution at the time. There was no shared ownership, no ongoing collaboration, and no joint creative control.

And what happened next was even more telling.

Shortly after the purchase, Kaiju Revolution launched “KR Testing” a paid-access version of the game that used:

  • Most of Titan Genesis’s original assets
  • Slightly modified KR branding
  • A few new models and animations

This was not a new game. It was a re-skinned version of Titan Genesis, repackaged and sold under the KR name. Yet KR’s leadership publicly claimed it was a new phase in development, failing to credit the original creators and misleading the public for monetary gain.

KR Testing went on to generate a significant amount of Robux, much of it earned from reused content that had been bought cheaply and sold at a markup.

This raises key issues:

  • Deceptive marketing to fans and supporters
  • Exploitation of small dev teams with lowball offers
  • Repackaging old content as new, original work

The Titan Genesis buyout is a clear example of how Kaiju Revolution operated — not with transparency or integrity, but through quiet acquisitions, misleading statements, and a relentless push to monetize others’ labor with as little credit or cost as possible.

Case: Titan Genesis vs Solaria Interactive – Exploiting Minors through Invalid Contracts

In a recent development, Titan Genesis (TG), a game project started by two minors known as Void and Cabinet, officially voided its contract with Kaiju Revolution and revoked Solaria Interactive’s permission to use TG’s assets in any form, including in their public testing experience. Despite this clear withdrawal, Ancient, the owner of Solaria Interactive, retaliated with false legal intimidation.

Ancient claimed that the contract was "unvoidable" due to being co-signed by a parent or guardian, asserting it to be legally binding. However, this is a misrepresentation of contract law involving minors. In most jurisdictions, contracts with minors are only considered binding if they involve necessities (e.g., food, housing). Creative work, such as game assets, does not fall into that category. Therefore, even with a co-signature, Void and Cabinet retain the legal right to void the agreement.

After being formally notified by both Void and Cabinet that the contract was terminated, Ancient escalated the situation by suggesting he would take the matter to court. When pressed, he ultimately declared that he would continue to use Titan Genesis’ assets regardless of the revocation.

This situation raises serious ethical and legal concerns:

  • Unauthorized asset use after clear revocation by the rightful creators.
  • Misleading legal threats made against minors.
  • Dismissal of legal protections afforded to underage creators.

This isn't just a contractual dispute, it’s a clear example of power being wielded against young developers to silence them and continue profiting off their work. Solaria Interactive's refusal to respect the withdrawal of asset permissions not only undermines trust but may also constitute a violation of intellectual property rights and grounds for a DMCA takedown. Who knows what Ancient could have told the two inexperienced in-law minors, who knew little about law, to scare them into not closing the contract. If they hadn’t been guided by third parties, it could have been a lot worse.

NOTE: Void did not LEAVE KR, he was terminated in a recent confirmation by Void himself, Void was terminated after Concord saw a comment letting a Content Creator know about the state of TG (The Creator seemed to be unaware) Concord saw the Comment and used it as a reason to terminate Void, even though Void demanded it is not valid reason for termination. Comment below

CASE 5 - REHIREMENT OF OBIE (NECROCHEM, ETC)

TAB UNDER CONSTRUCTION Case 6 – Rehiring Obie: Solaria Brings Back a Disgraced Owner Despite Enormous Scandal

After all the controversies surrounding Obie, the former owner of Kaiju Revolution, many believed his departure would mark a clean break, a chance for the project to rebuild under new leadership and higher standards. But that illusion shattered when Solaria Interactive quietly rehired Obie as a map developer for KR’s “Legacy Map.”

This decision stunned much of the community, because Obie wasn’t just controversial, he was exposed in a 4-hour-long documentary that revealed a history of toxic behavior, and manipulation. Despite this, Solaria brought him back. (https://docs.google.com/document/d/1iOGK0kbo3xN2oWuWNMJEBsbGenDJG_6D8QwzNgkO1Sw/edit?usp=drivesdk )

No apology.

No explanation.

No public statement.

Just quiet reentry, working behind the scenes on a major in-game feature, a decision that deeply contradicts any claims of “professional reform” made after Obie’s original departure.

This move:

  • Undermines Solaria’s credibility as a professional or ethical developer team
  • Endorses insensitivity by showing reputation is irrelevant to hiring decisions, as long as that person
  • Sends a message to Roblox kaiju fans that even those with the worst reputation can still work in the shadows and make money, no matter what they’ve done.

Obie’s return is more than a misstep, it’s a moral failure, and it exposes just how little KR’s new management changed after the old guard supposedly left.

REFERENCE

MID WAY SCREENSHOTS AND EVIDENCE

Some Text May Be Redacted for Privacy Reasons.

https://cdn.discordapp.com/attachments/1370619917094879273/1370812430912852069/ScreenRecording_05-10-2025_12-18-02_1.mov?ex=6850520f&is=684f008f&hm=04e7d5e521785444621c884f35278180a366e1c149f028657597270239c0db1a& 

https://cdn.discordapp.com/attachments/1370619917094879273/1373645626352603146/05251.mp4?ex=684f6bee&is=684e1a6e&hm=d31b0db80ba8ec341f61c8cf940497045339b9f3c7126e98884dbdb9bb73e86a& https://cdn.discordapp.com/attachments/1370619917094879273/1373645627543650384/05253.mp4?ex=684f6bee&is=684e1a6e&hm=06e6275ddae7c0c73c684dea97ca9973c09eba0b3e0d39ecfa7e71557aaa9379& 

https://cdn.discordapp.com/attachments/1370619917094879273/1373645626922897428/05252.mp4?ex=684f6bee&is=684e1a6e&hm=5f728f5d36f828bfda080a85b8ea70c572b10e555e80460333d6312835945371& 

https://cdn.discordapp.com/attachments/1370619917094879273/1373645628709802104/0525.mp4?ex=684f6bee&is=684e1a6e&hm=2d5a1f92f558ee12876494ed0ae68c484229df43e4f40265fc7cde152a369643& 

Truth Behind Kaiju Revolution: Obie Exposed - YouTube 

https://cdn.discordapp.com/attachments/1370619917094879273/1370812430912852069/ScreenRecording_05-10-2025_12-18-02_1.mov?ex=684f008f&is=684daf0f&hm=d462dbfec7df74d189eaa6d681ca5790dcf19c49f55921f2093a4d0c89e6dd9f& 

https://docs.google.com/document/d/16AZmMFQnA2C5G51IWTb-gFf8jRltHX9H98AtgLFap1c/mobilebasic 

LINKS MAY NEED TO BE COPY + PASTED INTO DISCORD TO VIEW

CASE 6 - TERMINATION LETTERS

 Case 7 – The Termination Template: Mass Firings with a Copy-Paste Excuse

Before the rebrand and PR sweep that transformed Kaiju Revolution’s dev team into the new “Solaria” or “Obsidian Games,” a sweeping purge of staff quietly took place. Several developers, including myself, were abruptly let go.

No warning.

No individualized feedback.

Just a cookie-cutter termination letter that read:

“We regret to inform you that your contract with Obsidian Games Development is hereby terminated, effective immediately.
Reason for Termination: Unfortunately, there are currently no active projects available that align with your position.
We appreciate the contributions you made during your time with us and wish you the best in your future endeavors.
If you have any questions, please do not hesitate to reach out to Human Resources.”

This same exact message, word for word, was sent to every developer who was fired during this wave. No effort was made to personalize the reason, acknowledge the developer’s role, or even properly justify the decision.

It wasn’t professionalism.

It was corporate theater, using the veneer of HR-speak to cover what looked like:

  • A purge of people tied to old conflicts or criticisms
  • A way to clear space without having to face backlash
  • A move toward rehiring only close friends or “yes-men”

And despite claiming there were “no active projects” for these devs to work on, Solaria continued pushing out KR Testing, new map work, and other features immediately afterward, possibly even using concepts from those very same developers who had been let go.

CASE 7 - USING PERSONAL CONNECTIONS TO GET CHECK

Case 8 – Fired for Friendship: Destorn and the Loyalty Ultimatum

Some of the hardest betrayals in this story weren’t professional, they were personal.

Destorn, a close friend of (ren) and a developer for Obsidian Games, was removed from his position not because of poor performance, unprofessional behavior, or any kind of wrongdoing. In fact, he was told explicitly that he’d done nothing wrong.

But that didn’t matter.

On January 11, 2025, Destorn received a message from Concord, a project lead at OG. It read:

“I am sorry to let you know, but we cannot continue working with you due to the actions of Ren and his group of people attempting to slander the company.
You have not done anything wrong, but at the moment we cannot work with anyone associated.”

Destorn asked the obvious question:

“ym fired for now?”
Concord responded:
“For now. Once the situation resolves itself or Ren fixes his actions, we can speak again.”

This wasn’t a professional decision. It was social blackmail.

They didn’t just punish Destorn, they used him to try to control Ren who was apparently attempting to “slander” KR. They hoped that by punishing people around users who are against them, they could make friends back away, or pressure them into silence. It was a manipulative, deeply unfair move that turned loyalty and friendship into a liability.

And the context? Ren had previously created a mock exposé document to test Obie’s trustworthiness, and he failed that test by leaking everything I shared. That document was never published, never made public. But instead of confronting Obie’s breach of trust, they turned on the people closest to Ren. People like Destorn.

This case hits harder than most, because it showed how far they were willing to go not just to avoid criticism, but to isolate critics.
To turn community into compliance.
To turn friends into pawns.

And all of it for nothing more than being connected to someone they didn’t like.

CASE 8 - CONCORDS CHILDISH ACTS

 Case 9 – Banned for Criticism: When Feedback Gets You Silenced

In any healthy game development space, constructive feedback is vital. People will have opinions, especially about major model releases. But for Solaria Interactive, even respectful criticism seems to be too much.

Not long ago, several users in the community gave calm and fair critiques of the new Heisei and Godzilla Minus One models. They pointed out things like low-resolution textures, an oddly thick neck on Minus One, and dorsal plates that looked copy-pasted rather than properly modeled. No insults, no attacks, just honest feedback.

Concord, one of the lead figures at Solaria, didn’t take it well. He responded bluntly with,
“There were over 100 photos taken and used to model. It's modeled how the movie is. Cry about it.”

Instead of taking the feedback seriously, or even just acknowledging it, he brushed it off with mockery. When users continued explaining their concerns, Concord escalated the situation further by saying,
“If you can do better, we have applications open.”

Then came the guilt trip.
“Y’all don’t get to see DMs. Y’all don’t have to deal with the constant hate.”

What followed was worse: some of the users were banned from the server altogether. Their only “offense” was voicing opinions thoughtfully, and without hostility.

This isn’t how professional developers should treat their community. When feedback is dismissed like this, when people are punished simply for caring enough to speak, it stops being a space for collaboration. It becomes a one-sided echo chamber, where only praise is welcome.

And when someone in a position of power tries to guilt the community for voicing criticism, saying “you don’t know what I go through,” while silencing those with no ill intent, it stops being leadership. It becomes manipulation.

At the end of the day, these weren’t trolls or hate mobs. These were players who wanted to see improvement. And they were met with mockery, bans, and emotional blame they didn’t deserve.

REFERENCE 2

LINKS MAY NEED TO BE COPY + PASTED INTO DISCORD TO VIEW

Final Case - Suspected Culprit..

Final Case – The Shadow Takedown: When “Toho” Might Not Have Been Toho

This last case is harder to confirm, but it’s the one that leaves the deepest discomfort. Not because it’s the loudest or most public scandal, but because if it’s true, it reveals a level of manipulation that goes far beyond personal drama or bad leadership. It touches on deception at a legal level.

There’s been growing speculation that some of the Roblox kaiju game takedowns the ones everyone believed were from Toho might not have come from Toho at all. Instead, evidence points to someone inside Kaiju Revolution, possibly Ancient (also known as Dalinar), orchestrating these removals under the false identity of Toho itself.

This theory isn’t based on vague feelings or community gossip. It’s rooted in two chilling pieces of information.

First, a private DM from Ancient to Kaizagidora, who was the project manager of KR at the time, contains a direct and serious statement:

“I got those games taken down Kaiza, keep it to yourself.”

This wasn’t said in a joking or sarcastic context. It came during a serious discussion about competing kaiju projects, and Kaiza, who had no reason to invent or exaggerate this, has held onto that message as a quiet red flag ever since.

Second, in one of the official Roblox DMCA emails sent to a removed kaiju game, the request is credited to “Toho Real Studio” a name Toho has never used. That phrasing alone raises serious doubts. A company like Toho doesn’t make up throwaway aliases. They file takedowns professionally, with legal teams, proper documentation, and exact corporate names. They follow procedure, not improvisation.

If this had truly been Toho acting against IP violations, we would have seen their real company name, their proper licensing department, and follow-ups via official legal routes, not inconsistently named “studios” using suspicious aliases.

And that’s what makes this case so disturbing. If someone at KR truly impersonated Toho to remove competing games, it means they didn't just bend ethical boundaries, they shattered them. It’s not just manipulation. It’s fraud. It’s playing god with other people’s livelihoods and projects, pretending to be a multi-billion dollar IP holder to destroy competition from behind a mask.

Even if this turns out to be partially wrong, even if it was some other form of influence or pressure, the mere possibility… backed by that message and that suspicious DMCA sender, is enough to make people pause.

Because if KR leadership was willing to do that in silence, what else were they willing to do, just because they thought no one would notice?

Extra info...

Case ??? – The Pattern of Buyouts: From “Partnership” to Power Grab

Titan Genesis wasn’t the first kaiju project quietly absorbed by Solaria Interactive. Before that, Kaiju Antiverse faced a nearly identical fate. The game’s creator was approached with what appeared to be a collaborative offer, and in return, was given a high-ranking title within the Kaiju Revolution team, Project Manager. At first glance, this looked like recognition and a chance to work together on something bigger.

But that promise didn’t last. After some time, without public explanation or any clear wrongdoing, that same creator was demoted from Project Manager to Project Advisor, a much smaller role with significantly less say in development decisions. The power they once held over their own project was quietly taken away.

This isn’t an isolated case, it’s a pattern,,, one where Solaria Interactive, Obsidian Games, or whoever happens to be behind the scenes, seeks out rising kaiju games, offers what looks like a generous buyout or “partnership”, then slowly sidelines the original creators and absorbs the assets and influence into their own structure. What starts as a collaboration ends with the original teams pushed aside, their names barely attached to the product they helped build.

It shows a monopolistic behavior, not just in controlling assets, but in controlling people, taking their creative power, their community standing, and their voice. It’s not about shared passion for kaiju games, it’s about quiet consolidation, and it leaves behind a growing list of devs who were promised partnership, but ended up watching their work be used without their leadership.

it should also be mentioned……..

The legitimate corporate name is:

Toho Co., Ltd.
(In Japanese: 東宝株式会社,
Tōhō Kabushiki Gaisha)

Toho never uses names like "Toho Real Studio" in their legal, licensing, or takedown operations. All formal actions, especially DMCA notices or copyright enforcement, would be filed under Toho Co., Ltd. and typically routed through official legal representatives or agencies they contract (e.g., agencies like Shueisha, Kadokawa, or international firms like Sony Music Japan if there’s a distributor involved).

A DMCA from something labeled "Toho Real Studio" is highly suspicious, and almost certainly not from the real company. That name doesn’t appear in any public registry of Toho subsidiaries or affiliates.

This adds more credibility to the theory that the takedowns were orchestrated internally by someone falsely posing as Toho, possibly to eliminate competition. If Toho truly filed the DMCA, it would bear their proper legal name, contact information from a trusted IP agent, and usually be verifiable with a notice on their official site or a partner outlet.

More proof of the Endorsement Lie

Toho’s Real Roblox Game Is in the Works, and It’s Not Kaiju Revolution

If Kaiju Revolution truly had an official license from Toho, that fact alone would make it one of the most important and publicized kaiju games on Roblox. But there’s something even more revealing:

In early 2025, leaks surfaced on Twitter suggesting that Toho themselves are working on their own official Roblox project quietly developed behind the scenes, unrelated to Solaria Interactive or Kaiju Revolution.

The leaks didn’t mention KR, didn’t list Solaria, and had no overlap with anything the KR team had ever produced or shown. This aligns with how Toho typically handles their IP: when they do work with Roblox or digital platforms, they work directly or through vetted studios, and they never double-license the same character set to competing games.

This alone disproves the idea that KR was ever officially licensed. Toho wouldn’t secretly approve two Godzilla-related games at the same time  especially not while one is quietly in development under their own supervision.

And yet, KR continued to claim for years that they had some form of license or endorsement. That lie crumbles completely when you realize that Toho is making its own game, and KR is nowhere in sight.

https://fxtwitter.com/jdooo_x3/status/1931023149241716902 

https://fxtwitter.com/jdooo_x3/status/1931023036440051779 

More proof of TOHO announcing partnerships or affiliated games below;

Kaiju Brawler GigaBash Unveils Collaboration with Godzilla – The Tokusatsu Network 

https://www.scifijapan.com/godzilla-toho/toho-games-announces-godzilla-battle-line-mobile-game-collaboration-event-with-godzilla-vs-kong-blockbuster-film?utm_source 
https://www.scifijapan.com/godzilla-toho/castle-dragon?utm_source 

Contradictory Claims About Toho Deal

Kaiju Revolution has publicly stated that they only have an endorsement from Toho. However, they also claim to be under a Non-Disclosure Agreement (NDA) with Toho—which directly contradicts the nature of an endorsement.

 Fact Check:
Endorsements are public-facing deals. If KR was merely endorsed, there would be no need for secrecy or an NDA. NDAs are typically used in licensing, private negotiations, or development deals, not in simple public endorsements.

This inconsistency raises red flags about the legitimacy and transparency of their relationship with Toho.

Further Expansion on Endorsement Lie

The Xilien Dispute

One of the more disheartening cases involves a former KR modeler, Xilien, who had contributed 14 fully baked kaiju models to Kaiju Revolution. These models were completed and already imported into Roblox Studio, ready for implementation. Xilien, trusting the project and the leadership, never demanded upfront proof of licensing or any formal contract. Instead, he simply expected fair compensation, a flat payment of $5,000, which by industry standards is modest for the amount and quality of work provided.

When it came time to discuss the payment, Xilien approached Ancient (Dalinar), one of the key figures at the time. But instead of compensation, he was met with a concerning response: Ancient claimed that Obie (the former owner and president of the OG Company) had never informed him that Xilien was expecting any money. Ancient stated that not only could he not pay Xilien, but that he also would not be accepting the models at all.

Naturally, this left Xilien confused and frustrated. After investing significant time and skill into a project that had already implemented his work, he was being brushed aside without payment, and without a clear answer on where the communication had broken down.

Finally, Xilien posed the question that many others have begun to ask:

"If Kaiju Revolution is truly endorsed and licensed by Toho... then why can’t they afford to pay $5,000 for completed, in-game assets? Wouldn’t Toho, a massive international company, easily be able to cover that kind of cost for a legitimate, ongoing project?"

If they have endorsement from Toho, therefore a hypothetical "license" that is for usage of the intellectual property of Toho itself, doesn't it mean they should also support it via their own money? Meaning Toho should be funding them, because after all, Ancient said that Toho does check ups on the game, meaning they should care about it and thus give material support.

It’s a question that lingers not just for Xilien, but for anyone watching this story unfold... One that highlights how murky and potentially exploitative the behind-the-scenes operations at KR may have become.

Developer Mistreatment - Ren.


Case: Underpaid, Overworked, and Publicly Dismissed

Another personal and painful experience comes from a developer who was underpaid, overworked, and publicly humiliated by Kaiju Revolution leadership.

For all the rigging work provided, including multiple re-rigs of GMK at the team’s direct request, they were only paid 3,000 Robux. Despite being ordered to re-rig the model several times to “test things out,” they were only paid for one of those versions, even though none of the outcomes were their fault. The failed results were due to KR’s own unclear direction, not negligence on the rigger’s part. This work was done during a period of family-related personal struggles, which made the lack of understanding and fair pay even more disheartening.

But it didn’t end there. During another situation, things became even more humiliating. In the tester chat, the developer and a friend, Display, were being harassed by another user, who threw around insults and gay jokes toward them both. When Ancient eventually joined the chat, the harasser suddenly toned things down and began acting respectful. Rather than acknowledging the harassment or stepping in to moderate, Ancient sided with the harasser, even going as far as complimenting him.

Then, seemingly out of nowhere, Ancient turned the attention onto the developer, publicly criticizing them over a past rigging mistake, specifically their first attempt at rigging Gojira Minus One. At the time of that first task, the developer didn’t even know what they had done wrong, they were still learning. It wasn’t until another rigger, Cleric, kindly stepped in that they were shown the correct workflow and began improving.

This moment wasn’t just a critique. It was a form of public embarrassment, executed in front of others while the actual harasser was praised. It sent a clear message about where Ancient’s loyalties lay, not with the people doing the work or enduring harassment, but with those who were willing to flatter or side with him.

For the developer, this wasn’t just about Robux or rigs. It was about being used, disrespected, and then discarded, even while putting in honest work and trying to learn in the process.

FINAL REFERENCE

LINKS MAY NEED TO BE COPY+PASTED INTO DISCORD