Skip to content

Add RiftWii - #197

Closed
KakarottoCake wants to merge 1 commit into
OpenShopChannel:masterfrom
KakarottoCake:add-riftwii
Closed

KakarottoCake wants to merge 1 commit into
OpenShopChannel:masterfrom
KakarottoCake:add-riftwii

Conversation

@KakarottoCake

Copy link
Copy Markdown
  • Have you checked that there aren't other open pull requests for the same manifest update/change?
  • Have you verified that the manifest contains valid JSON?
  • Are you certain that this manifest is not designed to obtain copyrighted material or software, which you do not have permission to distribute?
  • Submitting malicious software is strictly forbidden, and potentially constitutes criminal activity, punishable by law. To the best of your knowledge, is this submission clear of any malicious intent?

RiftWii is a USB loader and mod pack loader for the Wii and vWii. It starts games from a USB drive, the SD card or the disc, and loads Riivolution-format mod packs into them. It is free software under the GPL, version 3 or later: https://github.com/KakarottoCake/Riftwii

About the manifest:

  • It takes the newest GitHub release (riftwii-v*.zip), so version is auto. We release often; the app also updates itself from GitHub once installed.
  • The release zip keeps the SD card's files in an sd-card/ folder. The treatments move apps/riftwii/ and the built-in themes (riftwii/themes/) to the card's root, and put the license, notice and source files next to the app.
  • The zip's usb-drive/ folder (empty placeholder folders for a USB drive) and the separate Wii Menu channel installer (apps/riftwii_channel/) are left out.
  • Checked against schemas/ValidationSchema.1.0.0.json, and the moves tried on the current release zip (2610-769).

@Awesome-guyy

Copy link
Copy Markdown

From my testing, RiftWii is pretty stable too so yeah definitely consider adding this. Also feature rich, even supporting Wii U pro controllers ingame, and the GameCube adapter

@Posifurg

Copy link
Copy Markdown

Submissions currently aren't being accepted.

In the meantime, was AI used here? I'm looking through the source and I'm seeing suspicious comments.

@KakarottoCake

Copy link
Copy Markdown
Author

Submissions currently aren't being accepted.

That's a shame my members were looking forward to it being added.

In the meantime, was AI used here? I'm looking through the source and I'm seeing suspicious comments.

Yeah there's AI assistance. It's not made exclusively by AI though, and there are several contributors and testers, every change gets reviewed and tested on real hardware.

@korbosoft

Copy link
Copy Markdown
Contributor

iirc a lot of the code's taken directly from usb loader gx

@KakarottoCake

Copy link
Copy Markdown
Author

iirc a lot of the code's taken directly from usb loader gx

nope, it's not. we did look at how gx handles some stuff (per game fixes, wiimmfi patches etc) and all of that is credited in NOTICE.md with the exact gx commits. We merge a lot of PRs so I can miss things so I ran a copy check against gx's current source and the only real matches are the wiimmfi patch data and a few patch values, which are credited too. the code itself is ours, period.

@korbosoft

Copy link
Copy Markdown
Contributor

i see

@Aeplet

Aeplet commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

For multiple reasons here, this application will not be approved at this moment.

For one, much of the code is taken directly from USB Loader GX.
Secondly, this stood out to our team: Literally having to ask the AI to dumb things down for you guys, since none are programmers.

KakarottoCake/Riftwii@65ca485
"messages written by agents were hard for the maintainers to follow."

Also, giving Claude complete control of your GitHub accounts: KakarottoCake/Riftwii#91? Detailed replies and code reviews within seconds to minutes of each other is definitely not human.
You guys even went out of your way to strip credit from USB Loader GX: KakarottoCake/Riftwii@1a3dc25
Removing attributions, despite the fact that it's a requirement to keep original licences in place verbatim
You failed to do that, but at least linked to the repo. Now you've removed that too (license violations)

You also don't really care about licenses.
You guys publicly they claim "every change gets reviewed and tested on real hardware", which is bullshit on 2 fronts, it's code reviewed by AI from multiple accounts, and you're mainly testing against a custom fork of Dolphin (Which Dolphin is not accurate enough for testing like this)
Here's another example too. And there's dozens of commits like this - KakarottoCake/Riftwii#298 (comment)

@Aeplet Aeplet closed this Nov 18, 2026
@KakarottoCake

Copy link
Copy Markdown
Author

Let's go through this, since you clearly didn't.

For one, much of the code is taken directly from USB Loader GX.

Name one file. You can't. You made the accusation, didn't link a single line of code, and hoped nobody would check. What actually came from GX is the Wiimmfi patch blob, the Kirby MetaFortress patch words, a handful of per-game patch values, and the Gecko code handler binary that literally every Wii loader ships. That's data, not code, and every file holding any of it carries GX's contributors in its copyright header (gxpatches.cpp, gxkirby.inc, wfcpatch.cpp) plus a NOTICE.md row with the exact GX commit it came from. That's more careful attribution than half the apps already sitting in this repo. You rejected a project for "stealing" while ignoring the file that lists every borrowed byte by commit hash.

You guys even went out of your way to strip credit from USB Loader GX
[...]
You failed to do that, but at least linked to the repo. Now you've removed that too (license violations)

You read a commit title and stopped. NOTICE.md still has over ten rows naming GX, each with the repo link and commit hash. The README credits it. The credits screen in the app credits it. What that commit did was stop stamping GX's copyright on files that never contained a line of GX code. That isn't removing credit, it's not falsely claiming someone wrote code they didn't. The GPL's notice rules cover copied code, and every file with copied code kept its notices. If you're going to accuse people of license violations in public, at least learn what the license says first.

Also, giving Claude complete control of your GitHub accounts [...] Detailed replies and code reviews within seconds to minutes of each other is definitely not human.

Incredible detective work. I told you we use AI myself, in this thread, weeks ago. The comment you dug up as "proof" has "Posted by Claude Code" printed right on it. You exposed a label. And your big gotcha about us "dumbing things down" is a rule that makes the bot write in plain English. Readable docs for actual humans. Truly damning.

you're mainly testing against a custom fork of Dolphin (Which Dolphin is not accurate enough for testing like this)

No kidding. That's why the things Dolphin can't do (USB and SD loading, cIOS, real controllers) go to testers on real Wiis and vWiis every release. Dolphin catches the logic bugs before they ever reach a console. That's called a testing pipeline.

So to sum up: a copying claim with zero evidence, a credit claim the NOTICE file disproves, an AI "exposé" of something we announced ourselves, and a testing complaint that describes how everyone tests.

Keep us off the shop if you want, it's your shop. Just don't dress up "we don't like AI" as a license audit, because this one fell apart the second anyone checked.

@Aeplet

Aeplet commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

@Aeplet 🖕

Jeez I'm sorry larsen 😭

@Aeplet

Aeplet commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Let's go through this, since you clearly didn't.

For one, much of the code is taken directly from USB Loader GX.

Name one file. You can't. You made the accusation, didn't link a single line of code, and hoped nobody would check. What actually came from GX is the Wiimmfi patch blob, the Kirby MetaFortress patch words, a handful of per-game patch values, and the Gecko code handler binary that literally every Wii loader ships. That's data, not code, and every file holding any of it carries GX's contributors in its copyright header (gxpatches.cpp, gxkirby.inc, wfcpatch.cpp) plus a NOTICE.md row with the exact GX commit it came from. That's more careful attribution than half the apps already sitting in this repo. You rejected a project for "stealing" while ignoring the file that lists every borrowed byte by commit hash.

You guys even went out of your way to strip credit from USB Loader GX
[...]
You failed to do that, but at least linked to the repo. Now you've removed that too (license violations)

You read a commit title and stopped. NOTICE.md still has over ten rows naming GX, each with the repo link and commit hash. The README credits it. The credits screen in the app credits it. What that commit did was stop stamping GX's copyright on files that never contained a line of GX code. That isn't removing credit, it's not falsely claiming someone wrote code they didn't. The GPL's notice rules cover copied code, and every file with copied code kept its notices. If you're going to accuse people of license violations in public, at least learn what the license says first.

Also, giving Claude complete control of your GitHub accounts [...] Detailed replies and code reviews within seconds to minutes of each other is definitely not human.

Incredible detective work. I told you we use AI myself, in this thread, weeks ago. The comment you dug up as "proof" has "Posted by Claude Code" printed right on it. You exposed a label. And your big gotcha about us "dumbing things down" is a rule that makes the bot write in plain English. Readable docs for actual humans. Truly damning.

you're mainly testing against a custom fork of Dolphin (Which Dolphin is not accurate enough for testing like this)

No kidding. That's why the things Dolphin can't do (USB and SD loading, cIOS, real controllers) go to testers on real Wiis and vWiis every release. Dolphin catches the logic bugs before they ever reach a console. That's called a testing pipeline.

So to sum up: a copying claim with zero evidence, a credit claim the NOTICE file disproves, an AI "exposé" of something we announced ourselves, and a testing complaint that describes how everyone tests.

Keep us off the shop if you want, it's your shop. Just don't dress up "we don't like AI" as a license audit, because this one fell apart the second anyone checked.

Thanks for the comments, we will reconsider this internally now. (I mean it, I'm not saying this sarcastically)

https://docs.oscwii.org/guidelines-and-processes
However, this app does not seem to be compliant with the AI policy in regards to the fact that it appears to be almost fully vibecoded.

@KakarottoCake

Copy link
Copy Markdown
Author

Thanks for the comments, we will reconsider this internally now.

Appreciated. We read through the AI usage rules: RiftWii is AI-led, and we'll declare that in the manifest with the flag and an explanation. For stability, there are about 100 automated test suites running on every change, and our Discord has 1k members who check every release, so anything we can't test directly goes to them on real Wiis and vWiis. NOTICE.md credits every outside project by commit, and if there's anything else you'd want to see, just ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants