this post was submitted on 27 Aug 2023
234 points (86.1% liked)
Games
16457 readers
1288 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's crazy that they haven't used things like the unofficial patch to fix their own damn game. Like they could pretty much just copy paste that shit and be fine. But no. More than a decade later and that shit is still around and even propagated to things like FO4 and FO76.
Someone distributing it for free doesn't mean they can legally just put it in their code and sell it.
If it is licensed in a way they can use it, they'd still have to do a bunch of testing and validation to actually do it.
It's not that simple. Even using it as a base gets you into a legal gray area. Learning from a work and incorporating elements into your own work is legal, but copying someone else's legwork like this is legally murky even if you don't take the actual code.
If an employee writes code for a company, the employer* owns the copyright.
If an individual writes code on their own time, they own the copyright.
If someone publishes a free mod containing code, that mod could contain a combination of that person's code, code from other contributors, and even other copyrighted code that none of them had the right to in the first place but it either hasn't been noticed or isn't being pursued because there's not likely any money in it anyways.
It's that murky area that I'm guessing they'd want to avoid. They might be more likely to hire the modder to do that again from scratch for them than to use their work directly. Blizzard did that back in the day with two (that I know of) of the people writing modding tools for StarCraft. Their tools remained on the modding site and were never officially adopted by Blizzard but the authors worked on the WC3 map editor to add some of that functionality right into the official map editor that was going to be released with the game.
Edit: corrected a mistake where I said the opposite of what I intended to (that the employee owned the copyright rather than the employer)