Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Look not trying to start a flame war. We really appreciate you adding the license.

Just one correction on section 6. The "deliver on request" route is 6(b), and it only applies when the program is shipped on a physical product. For downloads like itch, section 6(d) applies: the source has to be available from the same place as the builds, to anyone who downloads them, at no extra charge. So the easiest fix is to put a source zip or a repo link next to the builds on the itch page to comply with GPL. That's all I was asking for.

On whether the code is derived: thanks for confirming the asset extraction tool comes from our project. That alone means the GPL applies. For the rest, what caught my eye was the Boom Box VU row clock. It's our own fix, not original cart behavior, as we already have the correct cart behavior for this. Your builds match ours exactly as it was taken from Pezz who's port is based on ours: the 1001257 constant with its /100000 carry, 26 voices, the 0xE0 at 0x1B98, and the 0xFA tempo check with &0x0F defaulting to 8. The 0x88 handler's 0x80 fill over 0x1802–0x19FF matches too. If you wrote those independently and somehow came to the same patch, no problem. Once the source is up, I'm happy to compare and drop it if I'm wrong.

On WaterMelon, 100% get why people are angry they have every right to be myself included. its why Pezz, hpman project little man and us have been working so hard for the last several years on this. My worry is just practical, shipping the decompiled game publicly gives them a reason to go after every Paprium project, including the ones that only run on a cart people own. That's all I meant.

Well no, the unpacker isn't part of the shipped product so that alone wouldn't force a GPLv3 license on my codebase. Otherwise the Paprium assets themselves would have to be GPLv3 licensed, going by that logic.

I'm gonna put up the source tarball later today when I'm hopefully no longer bedbound (I'm posting from my phone and the computer is in another room). I haven't gotten around to writing a README yet. Hope that's ok.

(+1)

Force and honor for you @Neoprium Don’t let people like that discourage you.

(1 edit) (+2)

TLDR: but the gist of it is "me me me me I want to be the center of attention on anything and everything Paprium" and "no one is as capable as we are". So arrogant of you Koa, and so damn lame.

Yea. He sure loves to focus on Paprium and act like he owns it, while his customers (like Fonzie's) wait for stuff he never delivers.

Dude claims credit for a generic for-loop that calls directly into the Paprium VM (which is technically Fonzie's code) and thinks me using asset extraction code from another project means the other project's license is being infringed upon even though the extraction code never ends up in the linked binary (only the assets themselves do which are, again, Fonzie's).

Imagine how desperate for attention somebody has to be to file a DMCA for code for an essentially pirated project. He's no better than Fonzie and his customer's agree.

(+1)(-1)

Exactly

(-1)

Bla bla bla bla