the fangame runs on nintendo licensed hardware using nintendo licensed SDKs.
Legally shouldn’t have ever been their problem. If I, without any permission, ported Mario 64 to the Xbox, it would make zero sense for Microsoft to raise issue with Nintendo over it.
A lot of fangames that mod valve games don’t use any steam tools and Valve is still completely fine with the mods.
Statement’s a little incongruous: I would take a fangame that mods Valve games to mean something like a Sonic game built on the Source engine. Regardless, I’m pretty sure I get your intended meaning, and the fact is, there really aren’t that many to reference. I can only think of two notable ones off the top of my head, both of which are flash games, and both of which Valve ultimately did profit off of. After digging for a short while, I came up with two others, one being a short celebration of the series made for it’s 25th anniversary by a very well-known fan site, and the other being an obscure Unreal Engine project. The only other thing I can think of that might apply is Xash, which they definitely aren’t fine with, they just don’t have the legal standing to get rid of it without legally endangering every third-party tool made for their games.
You’re completely misunderstanding both the port tool, and the situation.
Valve has no issue with this at all. They don’t care about the IP aspect, and they don’t care about the tooling. But they are required by law to enforce copyright policing on their store. That’s just how it works.
Nintendo is the litigious one in the mix. They are known to go so far as to copyright strike a video for showing some of a game in the shot.
The linked project isn’t a port, it’s tooling to facilitate a port. There’s nothing Nintendo can do about it, because none of the provided data is owned by Nintendo. And it isn’t an issue with Steam/Valve, simply because it isn’t being sold on Steam. The moment someone tried to distribute the final game files, Nintendo would be down their throat. And the moment such a tool was added to Steam, it would likely face the same fate of Portal 64.
Legally shouldn’t have ever been their problem. If I, without any permission, ported Mario 64 to the Xbox, it would make zero sense for Microsoft to raise issue with Nintendo over it.
Statement’s a little incongruous: I would take a fangame that mods Valve games to mean something like a Sonic game built on the Source engine. Regardless, I’m pretty sure I get your intended meaning, and the fact is, there really aren’t that many to reference. I can only think of two notable ones off the top of my head, both of which are flash games, and both of which Valve ultimately did profit off of. After digging for a short while, I came up with two others, one being a short celebration of the series made for it’s 25th anniversary by a very well-known fan site, and the other being an obscure Unreal Engine project. The only other thing I can think of that might apply is Xash, which they definitely aren’t fine with, they just don’t have the legal standing to get rid of it without legally endangering every third-party tool made for their games.
You’re completely misunderstanding both the port tool, and the situation.
Valve has no issue with this at all. They don’t care about the IP aspect, and they don’t care about the tooling. But they are required by law to enforce copyright policing on their store. That’s just how it works.
Nintendo is the litigious one in the mix. They are known to go so far as to copyright strike a video for showing some of a game in the shot.
The linked project isn’t a port, it’s tooling to facilitate a port. There’s nothing Nintendo can do about it, because none of the provided data is owned by Nintendo. And it isn’t an issue with Steam/Valve, simply because it isn’t being sold on Steam. The moment someone tried to distribute the final game files, Nintendo would be down their throat. And the moment such a tool was added to Steam, it would likely face the same fate of Portal 64.