3 ms·
In practice this makes little difference: Nintendo's gonna C&D and sue you anyway, and you're not going to have the money to fight it. So might as well make it
by rcxdude 3y ago
In practice this makes little difference: Nintendo's gonna C&D and sue you anyway, and you're not going to have the money to fight it. So might as well make it more convenient.
- charcircuit 3y agoIt's actually the inverse. In practice Nintendo has allowed all of these projects to exist, some have speculated that it's because Nintendo cares more about the assets or that Nintendo focus more on taking away more direct routes of piracy. It's true that it makes little difference right now, but I don't think publishing decompiled code is good practice or a good habit for the game decompilation scene to get into.
- ProllyInfamous 3y agoDidn't Nintendo just DMCA the Portal64 project via Valve/Steam? >publishing decompiled code is [not] good practice I remember specifically that Portal64's developer required you to have the Portal.steam.app in order to build your own N64 version (using his tools/code).
- charcircuit 3y ago>Didn't Nintendo just DMCA the Portal64 project via Valve/Steam? No, Valve's legal team reached out to the creator and became worried when they learned that the project uses libultra from the leaked n64 sdk from Nintendo. To avoid any potential legal problems Valve asked the creator of Portal 64 to shut it down. >using his tools/code It required pirating Nintendo's N64 SDK in order to build. These decompilation projects don't require the SDK, but as my my original comment suggests they do contain code that is a derivative work of libraries from the SDK.
- ProllyInfamous 3y agoThank you for the clarifications. I just purchased an N64 Console to re-visit a childhood I never really explored (didn't have Nintendo as a kid). All this modern history was mind-blowing... a way-underpriced local CL listing for an N64 (with ALL the old games) has taken me way too far into this reverse-engineered rabbit-hole.