@@elypse5800 There's a new mod for 1.7.10 called Angelica which adds most of Optifine's features but with Sodium's performance, effectively making it a better version of Optifine. The irony is rich.
i feel so old seeing someone not know what mcpatcher is. i remember the days of opening mcpatcher every time minecraft got an update to patch the latest version
i never used it, bc my pc was too slow to run stock minecraft. but i learned it was a texturepack mod and looked up how to use it with optifine and got sad when i couldn't use the really cool texturepacks (even though i probably could)
I started playing back in the days of 1.6, and even back then, optifine did't play nice with a lot of mods, so i mostly used MC patcher. those were the cowboy days of mods, core moding galore, and like 3 different mod loaders that could sometimes sort of be forced to run together
Optifine is infamous in the resource pack community for its buggy implementation of mcpatcher’s features, _especially_ with regards to modded content. Tho when you’re racing to reimplement features in only a few weeks I shouldn’t be surprised.
I didn't follow resource packs, but I distinctly remember how the modding community would operate in waves of either VEHEMENTLY warning users against using Optifine to just being ambivalent about it and back again, depending on the update. But iirc they were never positive about it, and you'd often see in giant bold letters at the top of a mod creator's thread demanding that you try removing Optifine before reporting any bugs.
@@z-beeblebrox ofc you'd have to remove optifine lmao. No one wants to fix someone else's bugs or bugs you caused by mixing mods. And yes, Optifine had other priorities (like performance), you can't expect them to shine at everything.
@@onyx5902 Code theft in modding is a comparatively non-issue though. If your stuff is open source and somebody steals the code, its only a problem if they make their stuff closed source On the otherhand, if your stuff is open source, people can use it for inspiration, guidence, and can make their stuff compatible without having to ask you to do it (See Tinkers Construct not being compatible with Optifine, because Optifine is closed source and the Optifine devs refuse to fix the issue themselves)
kinda sad that most of the comments ignore the meat of the video and are talking about how "optifine is dead now" ... I mean yah sure... but still people need to consider that someone just lined their pockets with money made by what is basically a step above asset flips...
I'd say a step below, honestly. Usually when people make asset flips they at least still arrange the assets in a way that works for their game. But as shown in the video this was just straight up a copy paste job without even restructuring.
1: It is not an "asset flip". OF went above and beyond and made a better mod, that is why people prefer it. That is normal for software development. You wouldn't want people to hold back just so your work retains more value, that is just dumb. 2: OF money was to cover the site's expenses (which MCPatcher didn't have due to being posted in a forum) AND the cape server (that had to be hosted and managed from somewhere). Yes, they made more than they needed, not the end of the world. 3: Taking code from an open source project and improving on it is not something bad. Have you never heard of git forks? It is an industry standard to provide an easy way to replicate and modify other's code. The main issue here is the limited credit and the fact that OF is closed source (which is just scummy overall, even if it didn't use someone's code)
It's funny how the only reason optifine won is its performance improvement but know it's losing because of its lack of performance improvements when compared to sodium
to be fair i've been in this community since back in release and i never even heard of mcpatcher. that's probably just because i was way more interested in the fun silly mods like clay soldiers and gullivers than anything else
going frame by frame I don't think the logo was gonna hit the corner in both of these moments, at least not perfectly, it's *really* close though, just not close enough
I switched to sodium about 6 months ago and have never looked back. Poor performance optimization and progressively breaking features really made me realize how lazy the optifine dev was, and since switching, I'm able to access better versions of all these pack add-ons that I can use to customize my game. I hope that someday people will realize that optifine isn't really necessary anymore.
I used to use it because it was the only option. Now there's a buffet of superior graphics & performance mods I have no reason to use that stinking pile of closed-source code that randomly breaks half my mods. Thank god for Sodium, Iris, and all the other open source projects for breaking us out of this strangle-hold.
Misa here. With the possible exception of Continuity, I can assure you this is largely untrue. Unfortunately Optifine still has a bunch of little features that don't have Sodium/Fabric equivalents yet, or are nearly always not as up to date (Notably CEM and CIT-related stuff). I would love an alternative to Optifine, but as it is, there's too many things that have been in my texture pack for nearly 14 years at this point that are not supported by current alternatives to Optifine. The better performance is also likely due to many of these missing supported features, and not as much to do with poor/lazy optimization. Without all the same features supported by the alternatives, it's not a fair comparison.
Sodium is an entirely different beast underneath Optifine only heavily tweaks mojang's rendering Sodium literally replaces it from the ground up and they plan on doing it again for even more performance This results in less compatibility for very old potato PCs since those don't support the modern techniques Sodium employs
@@user-random-1aka just putting an RV at the back of the F1 The RV you'll be buying is of course newer than the other guy and therefore better The RV is brand new though so you have to get ingredients to cook meth
@@user-random-1 OptiFine is like a tricked-out RV: packed with all the bells and whistles, and yeah, you can even cook meth in it. Sodium, on the other hand, is an F1 car-sleek, fast, and built purely for speed. Sure, you could strap that RV onto the back of the F1, giving yourself more room for the meth lab, but to keep it from crawling, you'd need to slap on some rocket boosters (or a few performance-enhancing ̶S̶t̶e̶r̶i̶o̶d̶s mods) to make sure it keeps down the track at its speed.
people did know about this back in the day, I remember playing on an smp plot server around the time - for pretty much all of 2012/2013... and anyone that tried to brag about their optifine cape were quick to be shat on by other active players for paying real money to support theft just for a cosmetic nobody else could even see lmao
This was quite well known back in the day, and its one of the reasons I've only downloaded optifine once and never again. Both MCPatcher and Optifine are from the days where modloaders weren't a thing. To install a mod you had to overwrite a piece of the files in the Minecraft.jar. mods only worked together if they didn't touch the same files. For more popular mods people made a special download for people using the other mod as well so they could work together. That is what was so great about MCPatcher, you knew it would work together. Modloaders like Forge, and later Fabric made it possible to avoid these types of conflicts because the modloaders creates hooks and makes sure everyone that wants to hook in the same thing will get it. By the birth of Forge, MCPatcher wasn't needed anymore.
Because there is no proof? You can copy the features and the file structure without copying any code. I've done it myself lots of times too, making something similar to an existing piece of software which can read the same config but has nothing else in common with it.
@@theairaccumulator7144 why keep the folder name if you are writing it yourself and why act like a dick abt it in your dev notes are you rly trying to defend this piece of shit of sp rn ?
aaaaaaand now nobody cares about OF cause of Sodium and Iris, great! i really couldn't care less if OF stopped being mantained at all since Sodium is made to run on most PCs, so everything's great either way! Would also love if forge was abandoned and completely replaced by fabric! That'd be awesome too!
honestly forge is getting abandoned in favor of neoforge and with connector mod we get fabric, imagine if we had fabric compatibility built in so we could have 1 solid loader
Yeah, but some mods are only on 1.12 and Sodium and Iris aren't on that version. Yet at least. Just a couple days ago I was on the hunt for alternatives to Optifine for that version and no luck yet.
@@davidddo no, it is still one of the biggest versions, like 1.7 it will likely take WAAAAAY longer if ever for that to happen. even more so when we take into acount modpacks like gregtecg newhorizons that gave a holy uniqe way to play
Man, can't believe I actually kind of knew about this. Stumbled across some MCPatcher files when doing some texture work for GT:NH (a 1.7.10 modpack) and it got me thinking a little. Never found out that the features were BLATANTLY stolen and implemented in Optifine instead of them being merged though, that's all new to me. Jesus christ, man.
It's funny how it kept itself as closed-source, now it makes complete sense. It's always unscrupulous rats who steal code the ones who always make sure their code is as secret as possible. Funniest thing is, the way its coded makes it far inferior to any other option; both in term of performance gain as well as overall compatibility, while most of said options are, in fact, open source.
Is it plagiarism when the original code was under a permissive license? You can put a NCS song into your video without getting copyright striked. It's the same with public domain and MIT licensed code which MCPatcher was. Anyone can take it and do whatever they want with it without crediting the original author.
It isn't plagiarism. 1. MCPatcher's code was in the public domain in 2011 (changed to MIT in 2013, and MIT does require crediting, but this was added in 2013... after all this had happened) 2. The OptiFine implementations were likely SP's own work, since it is missing a lot of features, has a lot of bugs, and has to work with OptiFine's custom renderer. 3. The documentation was copied, but it was credited, which is shitty, but not plagiarism.
@@m4rt_ Otherwise meaning "it is not plagarism, it is worse than plagarism. Because at least plagarized work is not actively worse compared to the original"
@@m4rt_ this is not how public domain works. unlicensed code is still protected under copyright a license serves as a "you're allowed to do X provided you do Y" without a license you're technically not allowed to do anything beyond reading/compiling/running the code
Is funny that you talk about the stolen MCPatcher feature at this particular time, because it sheds light on a problem that part of the Texture Pack community is currently experiencing: Many people are familiar with CTM (Connected Texture Mod), but there's also an 'equivalent' for items, CIT (Customizable Items Texture), which lets you modify item textures according to the NBT value associated with the item. However, since 1.20.5, items no longer have NBT values and use Components. This breaks the integrality of CIT features, and the most dramatic thing is that Components are namespaced names, which requires special attention in the revision of the format to support namespace. And therein lies the problem facing the Texture Pack community: Nobody knows what form this revision will take. Everyone's waiting for the release of Optifine 1.20.5 or 1.21, which will present to the world the new implementation decided unilaterally by one guy. And now you're telling me that CIT was _not_ developed by sp614x? Hmm, that explains some of this mess. CTM and CIT were created by other people, and sp614x has done nothing but maintain its features at arm's length. And with the arrival of Components, that mean he need to work one a code that he would have probably preferred never to modify to such an extent (in addition to all the other problems encountered by Optifine).
@@codenamec.a.t2480 Embeddium is the weird copied chinese car whose manufacturers tell you is the better option. Saying this because the things Embeddium added themselves (FRAPI support, Translucency sorting) are implemented terribly and Sodium 0.6, which is in public Beta now, implemented them in a way better way and provides NeoForge support.
@@timolino567 oh, so sodium is now taking the MCPatcher card play and *cooperating between authors to make the mod community better for players?* Almost like that's part of why someone like kahr was passionate about MCPatcher at a ll in the first place, wild. Seriously tho I've heard about Sodium's dev and this is very in-character for them, rad to hear they're still slamming along with new ideas and improving things. Good on em.
Optifine made money off of features other people implemented. In short Optifine is open to a lawsuit. Furthermore SP added features and performance improvements arent even his own, the only part of Optifine that is wholly original to him is the fog adjustrment, everything else was made by somebody else and he made money off their hard work. SP is estimated to have made hundreds of thousands of dollars off of optifine, maybe even millions.
If he stole the code, then yes, it's infringement. If he stole the ideas/format, then no, there's no infringement. I don't think he stole any code, personally.
@@skejeton Oh he had too, reverse engineer take much longer to do then making anything scratch especially when it comes to coding. MCpatcher was open source. To have the features he supposedly developed so quickly and match MCpatcher, he would have had to have taken the code straight from MCpatcher.
@@sonicmeerkat "Stealing" a format is a standard practice in modding communities and in the software industry as a whole, do you think Iris is wrong for "stealing" the shader format from OptiFine?
@@atomictem5725 Even if he took code from MCPatcher and related mods, it depends on which license MCPatcher and the related mods had. Under MIT license, for example, SP would be free to take the source code, even if proprietary, as long as he credited the original developer somewhere. If it was a GPL license, then SP would be in trouble, as he'd need to open source OptiFine as well.
I'm happy someone is talking about this again. Unfortunately, very little attention was ever given to the issue, and all of my own attempts to tell folks about it were fruitless. Although as nice as it is to see this, I'm too bitter and jaded to see things in a positive light, so I can't imagine this video will help too much. I hope I'm wrong. (Edited my comment to remove some 'oversharing'; I struggle with that too often.)
honestly "uses the same file structure" isn't bad. (or, wouldnt be, if the features were implemented correctly) having multiple competing implementations of the same system is generally a good thing, **IF they're honest about it!**
@@Notsalmon547 he didn't invent putting files inside of folders. If the optifine dev didn't copy any of his code directly there is nothing to credit. This is the whole premise behind clean room reverse engineering.
I'm honestly glad he replicated the file structure, as this made everyone's life easier. But copy-pasting documentation, giving zero credit, AND claiming it does everything when it actually doesn't is scummy as fuck. Jesus.
In the software circle, you can not copyright an api (see Google v Oracle). File formats can take a while to reverse engineer if no documentation exists. However, considering that mcpatcher likely had documentation on the file formats it used available to pack makers, a simple bit of reverse engineering is likely all it took to build code that'll read and interpret what is stored within those files. The hard part would have been getting optifine to support the same features mcpatcher had. Java is also absurdly easy to decompile. If SP copied MCPatcher's code, then one round with a java decompile tool is all it'll take to reveal that.
He wouldn't even have needed to decompile it. The MCPatcher source code is open source, and at the time (in 2011) it was in the public domain. Though I still suspect SP still had to re-implement a lot of stuff.
i will say as an optifine hater, the file formats being the same is not something to complain about. like even outside of minecraft modding, things will share the same implementations of things all the time. should we get angry at the fabric connected texture mods as well for copying mcpatcher? should we get angry at openssl for copying the same protocol as windows' ssl code? no lol, there's enough other things to get angry at optifine (like not mentioning mcpatcher as much as they should, or being closed source / for profit) that "tries to be compatible with an existing mod" shouldn't be one of them imo standards exist for a reason, if mcpatcher creates a standard i see no reason that other implementations of the same features shouldn't be able to use the same standard
@@m4rt_ that doesn't make it any less scummy to (seemingly) steal open source code to make a closed source competitor with, which you are putting adverts on
ah back in the day, the real olden days, MCPatcher was also how you installed any kind of mod. I remember when you'd add Modloader then use MCPatcher as basically a mod manager lite, it worked pretty well for what was effectively the wild west with no binding APIs to anything. I always held that mod in very high regard
Funnily enough a similar thing happened with Sodium and Embeddium, but Sodium actually fought back, and hard. You can read up on it on the github issue that led to them swapping licences to polyform shield to deter Embeddium from stealing their future innovations.
That's not at all what happened. Jellysquid got pissy over Embeddedt making a hypothetical about turning embeddium into a hard fork, and ironically made him and Nolij have to hard fork the mod by blocking them from contributing to Sodium's source code. The revenue arguments later on was due to Jelly getting desperate for money as a result of being jobless, trying to act as if Embeddedt owed them money, even though it was their own choice to not develop an official forge version. On another note, Sodium going closed-source is genuinely stupid, and it just makes me want to support Embeddium even more.
@@ambientNexus No, Embeddium tried to literally replace Sodium. They made a Fabric version specifically to be an asshole to Jelly. Jelly was fine with Embeddium existing but the creator was literally sending harassment campaigns and saying they're replaceable. It's also not closed source, you're just not allowed to create a blatant copy of it. A Forge port is still legal as it's not competing with Sodium. This does not mean it complies with OSI. I have no clue what revenue arguments you're talking about.
"For the many filthy casuals out there, Optifine might be the one and only Minecraft mod they can name" it's even worse, most people don't even think of it as a mod anymore!
Actually, no. 1. They didn't look into and point out the fact that at the time MCPatcher's code was in the public domain in 2011 2. They misunderstood the difference between copying and re-implementing, and don't clearly explaining this to the viewer 3. They misrepresented the documentation as plagiarized even though it literally credits MCPatcher. This has just lead to people misunderstanding the situation and blowing it way out of proportion, which you can see people do in the comments here.
@@m4rt_Stop defending SP for what he did. Sure it wasn't illegal, sure this video gets a few things wrong, but the point is, legal or not, what SP did was still scummy, saying that "MC Patcher is not needed anymore" in the forum posts doesn't help SP's case either.
SP does add a few features here and there from time to time (like new shader stuff and CEM model support), but it's nothing major. The last real improvement they did was when they vastly improved the Render Regions option, which they only did to better compete with Sodium (and it did help, but Sodium is still way better).
I'm glad OptiFine is getting replaced. Closed-source corporate trash should always be replaced by open-source passion projects. It happened with recording software, it happened with video editors, it happened with image manipulation tools, and more types of software than I can even begin to try to list. And no, I'm not just getting my opinion from this video. I've had a distaste for OptiFine for a long time due to it being closed-source and financially motivated. I first realized something was up when I learned of their policy that you can't redistribute OptiFine as part of a modpack, which is just scummy. Allegedly, this is because the creator doesn't want to be blamed for rendering issues that only arise due to other mods in the pack. But if the mod was open-source, then every mod under the sun could ensure that their mod is compatible. Outright banning the ability to even put it in a modpack, even if it's just a client-side quality of life pack, is ridiculous and has made me dislike OF for a long time. Allegedly (and I cannot stress enough that I can't find the source for this info so take it with a grain of salt), OptiFine was approached by Mojang to have their fixes and optimizations implemented into Minecraft itself, only for the creator of OF to demand Mojang, in return, add OptiFine capes to Minecraft, presumably so he could continue to make money. The official stance is that Mojang only wanted to implement "parts" of OF, but given that info is from OptiFine itself, it could just be them trying to tell a half-truth. Hard to say, and I don't wanna give them the benefit of the doubt after everything they've done.
To be fair, ensuring compatibility with MCPatcher is a pretty reasonable idea. Less work for you, lets everyone keep using their already existing assets without much hassle.
yknow funny thing is one thing with optifine is that you dont need to format things corretly (for CIT features specifically) so optifine CIT packs can become obsolete on CITresewn and mcpatcher and you have to reformat the entire thing to get custom models to work and stuff. yet if it works for MCpatcher and CITresewn it will ALWAYS work for Optifine except for a few slight mishaps that are from optifines shortcomings
It's such a shame that a good dev got treated like shit by everyone because someone decided to line their pockets. I would argue there can be a benefit from POLITELY challenging the owner of optifine. The man responsible for its fucking existence may finally be recognized and treated properly.. at the absolute minimum. At worst, however, it may destroy optifine. I think best case, of the optifine owner stands down and someone respectable takes the reigns through its death lol
Optifine wanted to be standalone, and did it's best to maintain full compatability with mcpatcher texture packs. Sp614x was always the type to want to implement things his own way, because he thought his implementation was better. and if he wanted $ he would have sold to mojang back in the day. he's just a control freak. there was constant drama about optifine breaking all sorts of mods, and optifine being closed sorce did no favors fixing those. Sp614x never wanted to help mods be compatable or anything. he just wants things to be his way.
MCPatcher had/has an MIT license. Perfectly legal for optifine to copy. This is just trying to start shit between people that don't understand licensing. Especially since MC patcher's development started slowing around the time of optifine's development.
So, im seeing situation as: 1. Creator of MCPatcher didn't wanted to make conflicts on the forum, and being toxic in general. Because he would be banned, and maybe he was young when making it. 2. When Optifine was out. MCPatcher dev stay silent, because even if he started to stay his ground because Optifine dev literaly copypasted every features. He still has a worth argument of (Optifine was an optimization mod at the first place). And even if he asked him to delete all features. Im pretty sure that person of optifine just stole them all when MCPatcher dev went offline completly. 3. Most likely MCPatcher dev wasn't acknowledge about the scammy behaviour of Optifine dev, and because he was really tilted by the fact that Optifine dev gonna steal all features again. And because he became aware of the bullsquid Optifine dev was pulling out like crazy ad monetization, making mod close-based code, literally force players to pay him so people would download it, not maintain features that was broken by Optifine updates because he didn't care about MCPatcher at first place. So, he just. Quit? 4. After this all situation, im still happy that people started to share free copy of optifine mode because this story really shows how Optifine dev killed developer of main visual fixes, because of his rotten and beyond scummy behaviour. Im feel really sorry about MCPatcher dev because, he probably could stop this. But he never did. Maybe in other scenario optifine would die because he didn't had anything from the visual features. Or Optifine could be a seperate mod, or MCPatcher would be a mod. Or maybe both. Anyways at end of the day, we lost an innovative guy.
I hate that Minecraft STILL doesn't have vanilla methods of doing the things you need MCPatcher for... And the easiest way to _use_ MCPatcher IS to use Optifine. Its very annoying. I wish useful resource pack functionality wasn't locked behind mods.
I don't think anyone should own a mod (idea) that is just a general and qol feature. Optifine thrived off of being a hotspot for qol visual optimization features, so of course they would add popular features from other mods in their niche for the best player experience. If theres 2 cool visual optimization mods and the one I don't own adds a feature, I might as well add it myself. Not to mention i'm pretty sure back then mods couldn't be stacked... so the users of optifine would locked out of those features that are quite relevant to optifines niche if they didn't add them. (don't quote me on that) IF they were directly copying the code then that's a whole different thing, but simply using the same file path id say that is actually better for resource pack developers rather than a controversial thing. And the fact that they copied the explanations of the features from mcpatcher word for word when they are designed to function exactly the same, its lazy but not immoral. Plagiarizing the tutorial wording on how to use a mod when your mod is intent to implement the features of said another mod is just goofy, but at the end of the day its not compatible with copying the code, and that's a very important distinction. This comment was made by the optifine apologetic community thank you for your time.
Optifine using the mcpatcher folder isn't absurd. Implementing a file structure from another mod is quite common. That's how compatibility works, it would be absurd to get all the artists to implement an optifine and an MC patcher version of their pack. That being said, it doesn't excuse the fact that optifine is closed source and overly protective of their code, not contributing to other projects and just taking their work. That's scummy practice, fuck them.
Funny how Optifine replaced Patcher because of the performance side of things, and now the only reason people still use optifine is the stuff they took from it.
19:05 "Most people outside of the community didn't really pay attention until it was too late" Oh my god it hits so close it hurts. And not just about OF, a good few things too.
wow. I had almost no idea what MCPatcher was until now. I play a lot of 1.8 pvp, so the old texture packs still have the folder named MCPatcher, but I didn’t know what that meant
I've learned about mcpatcher while making a resourcepack that made enchanted items have different textures. I watched the UncleJam video about it and he always had the "mcpatcher" folder and all the comments were just saying to rename it to optifine so I did and just ignored it. After some time I learned about how shady optifine is and then I learned that it just stole mcpatcher. I hope the original creator of mcpatcher will perhaps return
way way back i remember always using mcpatcher to play with my favorite texture packs, optifine was already a thing at the time but i didnt really know about it then, and when i learned about it, tried it, and finally i could get more than 20 fps in game and i saw that it had "all of mcpatchers features" i moved to using it instead back then. misa's texture pack was a favorite of mine back then, and even then i could feel it in my bones, it didnt look exactly the same, but i wasnt sure how or why.. plus my poor old intel IGP PC just really needed optifine anyways. i think that there is the saddest thing about this to me, back then i didnt have an option i simply needed optimizations for my game, even if optifine never got those mcpatcher features i prolly still wouldve moved to using optifine anyways because these two mods didnt work together (from what i recall), and between my game looking pretty or running smoothly i wouldve always chosen smooth.
Optifine being mostly replaced by a open source, better, and community made set of mods (iris, sodium ect.) and the game itself might be the best ending to this story that we could hope for. sp was beaten even though he could cheat.
The light flickering one fixed it because the light flicker is in the light map color palette, left to right The y level of sprites determine what the light is for, including global light for dimensions, with the overworld section gets day and night but also the torch section, which has a flickering row
Using "More Gun" at 8:50 when talking about Optifine copying the files from MCPatcher 1-1 is incredibly funny when you consider that 'More Gun' is almost a 1-1 copy of "Someone Else's Song" by Wilco. It's not even known if Valve ever got permission to do this, they just kinda did it.
Videos like these are severely underrated. Growing up on the internet has only made me realize more and more just how important documentation of this kind of stuff can be. Amazing video!
No, it is put together, and is edited well, but it leaves out a lot of small but important details. Like the fact that in 2011 the MCPatcher source code was in the public domain, and claiming that if you copy something, even if you credit it, it's plagiarism, which is not the case.
Ironically, I have more familiarity with MCPatcher than Optifine because I jumped from Bedrock, to modded versions of Java Beta 1.7.3- though I haven't played it much. Open formats are legitimately awesome, but "cornering the market" with your privatized weaker version helps no one. Just imagine if the PNG format was just taken by some individual who tried to take credit for it, then poorly implementing it- then extensions like APNG (animated PNG) and MNG (multiple image PNG) wouldn't exist.
you’re missing out on a HUGE point in this video. MCPatcher is licensed as MIT, which is a license that allows this kind of use of the code (copying it, modifying it and making profit on it by someone else)
The MIT license requires all redistributed code to also be under the MIT license to be protected, which Optifine is not Edit: nevermind, MIT just requires the license to appear in the redistribution, not that it has to be under the same license. Optifine doesn't do this either, though.
I think you're attributing a lot of malice when this entire story could also reasonably be viewed in a much different light; the community was much smaller than it is today, SP saw cool features that a lot of people liked and came up with a way to implement them in a way that has performance and ease of use benefits, no one complained at the time so he assumed it was fine. I would argue that this is basically what the developers of the fabric alternatives to OF features are doing today: Bringing these features into a newer and better modding ecosystem when the previous creator seems reluctant or uninterested in doing so. The part at 24:00 where you say that the changes imply that SP knows what he did was wrong seems like a huge leap to me, both of the graphics you showed, especially the skybox one are just better and more easily legible than before. I think it is important to note that SP didn't steal the code for these features, only the ideas - while copy-pasting the documentation is definitely a weird thing to do, I don't think a mod developer plagiarizing text that very few people read matters all that much. Nitpick: I think it's fair to say that SP solely developed and maintained Optifine for 10 years, I get that one could claim that ideas are also part of developing, but in practice no one would say that SP or Khar "developed" CIT Resewn. All that being said, I still really enjoyed this video as a documentation of a crucial and often overlooked part of Minecraft history and really liked the style of the video, and I hope this comment doesn't come off as mean or anything.
Don't take this as a mean thing, I respect your input and wanted to clear a few things up People definitely did complain at the time, I included that in the video (5:50) you can go to the source and see a lot of other people complaining too. This was directly after more features got stolen. Also I feel like, sure combining features into optifine is OK i guess, but actively telling people to not download the mod that you got it from (MCPatcher not needed) seems malicious to me. And I feel like if it was some kind of virtuous combining of features, somebody would have said that. The community was definitely smaller, but not tiny by any means. This wasn't baby's first mod, it was after 2 years of mods before it. And also also, you do make a good point that it would be weird to say that SP or Kahr "developed" CIT Resewn (and maybe that wasn't the right wording in the video), but I feel like ignoring their contributions is bizarre. CIT Resewn in particular mentions MCPatcher and Optifine explicitly as being where the features come from, you can't really miss it. The only way to find out about MCPatcher is to go into the optifine documentation, or i guess to read the single line that says that it isn't needed with no direction Also also also if SP wanted the images to be more legible, why didn't he just make his own? why did he copy them in the first place if he cared so much about legibility? That's why I think this was a reaction to criticism of copying images, rather than just changing them to be more legible. If he cared about that, he would have just made his own image.
@@DIMM4_ All good, I'm happy that we can earnestly discuss such a niche topic :) Saying that no one complained was worded wrongly, what I meant was that no one involved in the creation of the original mods complained (at least not from what is shown in the video, I haven't done any research into this), Khar even explicitly says that he is fine with mods implementing each other's features. For the images, I agree that he should've just made his own images in the first place, but I think it's very conceivable that he started caring about legibility sometime between 2011 when the features were added and 2016 when the textures were changed (unless there is some evidence I missed that a lot of people were complaining about the stolen images in the meantime). I personally don't interpret "MCPatcher not needed" as telling people not to download MCPatcher, it's just informing people about the fact that they don't need both MCPatcher and Optifine, CIT Resewn also says that Optifine or MCPatcher aren't required. Overall, the video paints the picture that SP had some kind of malicious intent and was trying to basically monopolize this space in Minecraft modding to make money. While his actions obviously did end up having negative effects on a good chunk of people, as you show in the video, and I think he MCPatcher should be clearly credited on the OF website, I just don't believe that SP actually had bad intentions when he took the MCPatcher features.
@@DIMM4_ "MCPatcher not needed" MEANS NOTHING... This is a stupid assumption and this entire video is a pile of shit. You should be ashamed of it. Do better.
@@SimplyMattis The road to hell is paved with good intentions. SP may not have intended to screw over Kahr, but the community lost a prominent Minecraft modder because of a lack of proper acknowledgment. Kahr almost certainly stopped developing MCPatcher because SP refused to credit his work and therefore his mod died and he was even insulted / criticized by Optifine users as a result, which is pretty awful and definitely at least partially SP’s fault. We don’t even know if Kahr is alive, and we may never know, because SP didn’t acknowledge where he got his source code. Just because it’s legal for him to take the code without credit doesn’t make it right.
I first learned of all the scum about OF when i heard rumors of Mojang reaching out to SP to get a few of his features into the base game, and perhaps a job there. But then he wanted an unreasonable compensation so the whole thing got scraped. Combined with the fact that it no longer plays nice with other mods, and the fact that the Sodium family of mods now is a thing, i dont see a reason to support Optifine.
The weirdest thing to me is that MCPatcher is open source under MIT. If SP was copying the features, why not implement the source code instead of shittily copying it?
In software development, there's a difference between stealing ideas and implementing API's. MCPatcher's file format is nothing more than an API; a way for a (texture pack) developer to specify what they want MCPatcher to do. Let's call this file format MFF, the MCPatcher File Format. Now there exists an implementation for this format, also called MCPatcher, by the same creator. This is the actual MCPatcher program that loads the texture pack (defined in MFF), and puts it into the game. OptiFine did not steal features. Nor did it "steal MCPatcher". It simply implemented MFF. It added support for texture packs that originally would only work with MCPatcher. Stealing what MCPatcher did would be copying the implementation, copying the code. If OptiFine had literally just copied the MCPatcher code into itself, that would be theft. But a implementing a format isn't theft. Just because someone made a new MP4 player, doesn't mean that they "stole" MP4 from the people who made the first MP4 player and who designed the format. They wrote their own implementation. Was it handled well by OptiFine by saying "MCPatcher Not Needed", pushing people to not use it anymore? Absolutely not. Not cool. But it still wasn't theft, it just guaranteed good interoperability between the two no matter what OptiFine would add in the future. It eliminated the need for an external program, allowing you to tune these settings in-game. And it guaranteed backwards compatibility with any packs that had already been made. Believe me, if OptiFine wanted to "steal" features from MCPatcher, it would've defined its own format, and would've forced pack developers to use that new format instead. This would ensure that any new packs made for OptiFine would *not* work with MCPatcher, which is something you see big companies do all the time to undercut their competitors.
I feel like its different because the company that makes MP4 (ISO) makes money from shareholders and donations, not directly from people using it, while MCPatcher *does* rely on people downloading the MCPatcher Mod to make money. While the formats are similar, you still had to convert MFF packs to OFF packs. It seems like Optifine cut MCPatcher's life support, by using their big features and influence to sway people to one side. It's kinda like what apple does a lot with things like spotlight search replacing apps like Sherlock. I feel like you can't separate MCPatcher the file format from MCPatcher the mod, since they rely on each other to exist, that's why they have the same name.
@@DIMM4_ The reason OptiFine had to port the mods from MCPatcher is because of the custom renderer, making the original mods incompatible with OptiFine. Even outside modding communities, proprietary formats can and often are used by competitor companies if these formats become the standard.
I certainly don't think asking for permission would have hurt. But the MCPatcher mod seems to be licensed under the MIT license and I think it was also open source so it technically would have been find to take all of the code... if you provided attribution
An API or File Format can be copyrighted. It's like how you can't just implement HDMI without any license from the HDMI consortium. If you could do it, AMD wouldn't need to ask the consortium for license permission to implement HDMI 2.1 support for their cards on Linux.
It has. And it sucks, it is still playing catchup. To be entirely fair, the replacement mods are not perfect either, Sodium is still cleaning up transparency sorting issues. But the goofy part being that Optifine 1.21 preview versions launched with a wack issue that swaps around colorvalues. The game having wrong colors is something one sees literally right away. 😂
I understand what you're trying to say here, but the way mcpatcher was licensed makes what optifine did completely legal. In mcpatcher's license all of the things sp614x did (even if they directly took the code from mcpatcher, without asking, and redistributed it, is allowed. Even making money off mcpatcher's it is specifically allowed by the MIT license mcpatcher used. This is how open source software works. I develop minecraft mods too and I license my mods using the same license mcpatcher does and I have zero issues with this. It's how open source software works, mcpatcher could have just used a less permissive license if they didn't want this to happen. The only potential issue is that optifine might not include the copywrite notice or liability disclaimer that the MIT license also requires, but overall not many people care. Claiming this is plagiarism is ignorant about how open source code works.
I don't know man, this doesn't really seem like stealing. It just seems like any ordinary product competition. Like Apple implementing screen recording after Android did it first. Also, making Optifine compatible with MCPatcher packs doesn't seem like an issue to me. Its like making your new car compatible with standard gasoline. Would you say that the new car is stealing the idea of gasoline? Its similar to how Iris basically killed Optifine in terms of being the de facto shader mod. One of the main appealing features of Iris was that it was compatible with existing Optifine shaders. The text copying you mentioned is pretty blatant and bad though.
iPhones and Androids each run a different, mutually-exclusive operating system, so you can't just develop a "screen recording mod" that runs on both operating systems. OptiFine, however, could have (and for a while did) run alongside MCPatcher just fine, so that immediately puts into question any attempts to recreate features from another actively developed project (you can just run both mods!), but there can still be good reasons for it. One reason, as discussed in the video, would be if the other project was abandoned and the author released their code to the public, but that's not applicable here. Another common one is to develop ports to other mod loaders, which you could argue is relevant here as OptiFine was quicker to accept Forge than MCPatcher, but from the timeline of events I don't really believe this to be relevant. Instead the main reason I want to focus on would be if you disliked how the other project implemented it, and wanted to do it your own way, or at least improve and develop upon the others' idea. One example of this would be how Mojang has implemented shaders such as the lightmap shader or general internal shaders completely differently from any community project and vice versa. The issue is that OptiFine didn't do much of this? For some features yes, OF did provide addons, but for others it provided merely matching (if not incomplete) implementations. And all that of course is not to mention the fact that OptiFine then proceeded to monetize its product through ads and EULA-breaking donations (though quite frankly who cares about the EULA's thoughts on money), essentially capitalizing off someone else's work. Regarding your comparison to Iris, yes, the mod reimplements a feature from OptiFine, but there's some key differences. The first is that the mod is highly focused, revamping essentially just one of OptiFine's features (which itself was not entirely original, AFAIK, but that's a story for someone else to research another time). The second is that it is committed to developing new functionality that is increasingly being used by artists to create better and better shaders not possible under OptiFine's system. And yes, it too is monetized, but much less egregiously, and to an extent I think most (including Mojang's EULA) would consider reasonable. Hell, if you really hate ads, you can totally compile Iris from source without ever seeing an ad (except for maybe a Patreon link).
An argument could be made for Optifine that keeping the mcpatcher file structure initially started for ease of compatibility even if it wasn't explicitly discussed or agreed upon, but as it goes further down the line it's clear there was a change in motive. I only ever used Optifine for about a year but it was always clunky so I guess I lucked out by being made to switching to Fabric/Iris systems.
From what i understand, MCPatcher was completely open source. That means that copying code is allowed. No one would make their stuff open source and object to an upgrade by someone else, not that they would have any grounds to do so anyway. Also, adding support for other existing software is just a nice bonus. There's 0 wrong with that, it is just the norm. The copied documentation is also normal. There's no reason to re-invent the wheel just to look like you did more effort where it wasn't even necessary. I think people just don't understand how software development works and think this is just plagiarism like stealing someone's art. Making a replacement that is superior to existing software is never something bad. You'd have to be an a-hole to object to someone doing it better when it is a free thing for everyone. The only issue here is that they made OF closed source. Which is pretty scummy.
@@timohara7717 again, it is scummy, not illegal nor unheard of. Maybe he had a good reason (safety concerns, for example), altho he probably didn't. But the entire video harps on stuff that is normal for software development, the closed source part is mentioned at a glance and barely.
@@timohara7717 Yes, it being closed source is bad, but the other claims in this video are unsubstantiated. Making a closed source minecraft mod doesn't make you some sort of cartoon villain that needs a minecraft youtubers community harassing you
It'd honestly be nice to have a single mod that reimplements MCPatcher's features, as they're meant to work, for modern Minecraft, with proper credits to kahr and the other developers. We likely won't get another MCPatcher, the modding community has evolved past those days, but a single mod for Quilt (and maybe NeoForge) that implements resource pack features would be nice
I'm so glad over the past few years people are finally ditching optifine, it's such a nightmare to work with as a modder due to it being closed source and still patching the game directly, which NOBODY else does anymore in modern mc I've always wondered why so refuses to open source optifine given how much it could help out with its development and making modders more willing to work with it, and im wondering if mcpatcher is related to why
Wow, this video is incredible well done, amazing job :D Can't believe the channel is so small, this could easily be some 500k youtube channel in terms of quality. Good shit youtube for this recommendation :D
Something ETF/EMF is doing is adding a lot of features that werent a thing in optifine, expanding upon it more for resource pack creators to do more cool stuff
It’s ironic how Optifine, the “better option”, managed to become completely irrelevant due to there being better options.
(Optifine not needed)
me a 1.7/1.8 player still only being able to use optifine :
@@elypse5800There is a mod called "Angelica" which is backport of Sodium+Embedium for 1710
@@elypse5800 There's a new mod for 1.7.10 called Angelica which adds most of Optifine's features but with Sodium's performance, effectively making it a better version of Optifine. The irony is rich.
@@elypse5800 optifine is good for old versions but bad for new versions
i feel so old seeing someone not know what mcpatcher is. i remember the days of opening mcpatcher every time minecraft got an update to patch the latest version
i never used it, bc my pc was too slow to run stock minecraft. but i learned it was a texturepack mod and looked up how to use it with optifine and got sad when i couldn't use the really cool texturepacks (even though i probably could)
I started playing back in the days of 1.6, and even back then, optifine did't play nice with a lot of mods, so i mostly used MC patcher. those were the cowboy days of mods, core moding galore, and like 3 different mod loaders that could sometimes sort of be forced to run together
I don't remember it because I was very young and didn't understand mods
IKR SAME HERE
Ive been playing since alpha and if I used it at any point I forgot.
Optifine is infamous in the resource pack community for its buggy implementation of mcpatcher’s features, _especially_ with regards to modded content. Tho when you’re racing to reimplement features in only a few weeks I shouldn’t be surprised.
I didn't follow resource packs, but I distinctly remember how the modding community would operate in waves of either VEHEMENTLY warning users against using Optifine to just being ambivalent about it and back again, depending on the update. But iirc they were never positive about it, and you'd often see in giant bold letters at the top of a mod creator's thread demanding that you try removing Optifine before reporting any bugs.
@@z-beeblebrox ofc you'd have to remove optifine lmao. No one wants to fix someone else's bugs or bugs you caused by mixing mods.
And yes, Optifine had other priorities (like performance), you can't expect them to shine at everything.
OF being closed source makes this even more scummy
Remember everyone, if the creator doesn’t want you digging around in the code, *theres probably a not good reason.*
You shouldn't say OF bro 😭
@@Marklikesminecraft
ONLYFANS!1?!?!!!!!
Of course it is. You wouldn't want someone stealing the code...
@@onyx5902 Code theft in modding is a comparatively non-issue though. If your stuff is open source and somebody steals the code, its only a problem if they make their stuff closed source
On the otherhand, if your stuff is open source, people can use it for inspiration, guidence, and can make their stuff compatible without having to ask you to do it (See Tinkers Construct not being compatible with Optifine, because Optifine is closed source and the Optifine devs refuse to fix the issue themselves)
kinda sad that most of the comments ignore the meat of the video and are talking about how "optifine is dead now" ... I mean yah sure... but still people need to consider that someone just lined their pockets with money made by what is basically a step above asset flips...
I'd say a step below, honestly. Usually when people make asset flips they at least still arrange the assets in a way that works for their game. But as shown in the video this was just straight up a copy paste job without even restructuring.
1: It is not an "asset flip". OF went above and beyond and made a better mod, that is why people prefer it. That is normal for software development. You wouldn't want people to hold back just so your work retains more value, that is just dumb.
2: OF money was to cover the site's expenses (which MCPatcher didn't have due to being posted in a forum) AND the cape server (that had to be hosted and managed from somewhere). Yes, they made more than they needed, not the end of the world.
3: Taking code from an open source project and improving on it is not something bad. Have you never heard of git forks? It is an industry standard to provide an easy way to replicate and modify other's code.
The main issue here is the limited credit and the fact that OF is closed source (which is just scummy overall, even if it didn't use someone's code)
You had to pay to use optifine??
@@kamdenmcleanmovies No, they had donations to fund the mod, host site and the cape server.
@@rompevuevitos222 so it’s not like they were rolling in it from this lmfao
It's funny how the only reason optifine won is its performance improvement but know it's losing because of its lack of performance improvements when compared to sodium
I'm not sure what to think. I use sodium, though, so I hope this kind of issue never happens again.
Or compared to vanilla lol
sodiom only works with like 3 of the thing mcpacker did
@@beaconJr64 sodium is for performance ONLY, if you want the shaders like Optifine, you get iris. if you want the zoom, you get zoomify.
Dous sodium also have the zoom
God, hearing someone not knowing what MCPatcher was makes me feel old and kind of melancholy
Uhhhhh I just head about this mod 👀
to be fair i've been in this community since back in release and i never even heard of mcpatcher. that's probably just because i was way more interested in the fun silly mods like clay soldiers and gullivers than anything else
Sodium knocked the crown off the king, and Iris slayed it.
could've said tyrant
@@BossKnight the two aren't mutually exclusive
The crown was made with paper and crayons
@@V972 oh also hi :D
Sodium and Iris are totally different mods, sodium is to improve performance while Iris is to allow shaders
i guess you can say that optifine isn't doing so opti-fine after all
read the description of the video... lol
27:56 DID YOU JUST DO THAT? Did you just cut away the MOMENT that was going to hit the corner? HOW DARE YOU!
Also at 15:40 😭
peak editing
going frame by frame I don't think the logo was gonna hit the corner in both of these moments, at least not perfectly, it's *really* close though, just not close enough
I switched to sodium about 6 months ago and have never looked back. Poor performance optimization and progressively breaking features really made me realize how lazy the optifine dev was, and since switching, I'm able to access better versions of all these pack add-ons that I can use to customize my game. I hope that someday people will realize that optifine isn't really necessary anymore.
I used to use it because it was the only option. Now there's a buffet of superior graphics & performance mods I have no reason to use that stinking pile of closed-source code that randomly breaks half my mods. Thank god for Sodium, Iris, and all the other open source projects for breaking us out of this strangle-hold.
"Optifine not needed."
Misa here. With the possible exception of Continuity, I can assure you this is largely untrue. Unfortunately Optifine still has a bunch of little features that don't have Sodium/Fabric equivalents yet, or are nearly always not as up to date (Notably CEM and CIT-related stuff). I would love an alternative to Optifine, but as it is, there's too many things that have been in my texture pack for nearly 14 years at this point that are not supported by current alternatives to Optifine.
The better performance is also likely due to many of these missing supported features, and not as much to do with poor/lazy optimization. Without all the same features supported by the alternatives, it's not a fair comparison.
Sodium is an entirely different beast underneath
Optifine only heavily tweaks mojang's rendering
Sodium literally replaces it from the ground up and they plan on doing it again for even more performance
This results in less compatibility for very old potato PCs since those don't support the modern techniques Sodium employs
@@codbughave faith in sodium. Sp won't get away with it twice
"Optifine is like an RV, while a mod like Sodium is an F1 car. It's really fast, but you can cook meth inside of Optifine"
my day has been made
This is one of the best quotes ever imo
But you can install additional mods (which implements other features of optifine), to expand the car, but keep the same speed and mobility
SAME, SUCH A LEGENDARY QUOTE
@@user-random-1aka just putting an RV at the back of the F1
The RV you'll be buying is of course newer than the other guy and therefore better
The RV is brand new though so you have to get ingredients to cook meth
@@user-random-1
OptiFine is like a tricked-out RV: packed with all the bells and whistles, and yeah, you can even cook meth in it. Sodium, on the other hand, is an F1 car-sleek, fast, and built purely for speed.
Sure, you could strap that RV onto the back of the F1, giving yourself more room for the meth lab, but to keep it from crawling, you'd need to slap on some rocket boosters (or a few performance-enhancing ̶S̶t̶e̶r̶i̶o̶d̶s mods) to make sure it keeps down the track at its speed.
This once again shows that cloased source makes basically zero sense for game mods
Close enough, welcome back Hbomberguy
except hbomberguy showcased examples of actual plagiarism and this guy just described common development practices and attributed them to "plagiarism"
@@utopiandystopia1383The documentation was literally plagiarised
this is seriously crazy I can't believe no one knew about this
Nobody cared about this
people did know about this back in the day, I remember playing on an smp plot server around the time - for pretty much all of 2012/2013... and anyone that tried to brag about their optifine cape were quick to be shat on by other active players for paying real money to support theft just for a cosmetic nobody else could even see lmao
This was quite well known back in the day, and its one of the reasons I've only downloaded optifine once and never again.
Both MCPatcher and Optifine are from the days where modloaders weren't a thing. To install a mod you had to overwrite a piece of the files in the Minecraft.jar. mods only worked together if they didn't touch the same files. For more popular mods people made a special download for people using the other mod as well so they could work together.
That is what was so great about MCPatcher, you knew it would work together.
Modloaders like Forge, and later Fabric made it possible to avoid these types of conflicts because the modloaders creates hooks and makes sure everyone that wants to hook in the same thing will get it.
By the birth of Forge, MCPatcher wasn't needed anymore.
Because there is no proof? You can copy the features and the file structure without copying any code. I've done it myself lots of times too, making something similar to an existing piece of software which can read the same config but has nothing else in common with it.
@@theairaccumulator7144 why keep the folder name if you are writing it yourself
and why act like a dick abt it in your dev notes
are you rly trying to defend this piece of shit of sp rn ?
The Optifine situation is insane
the The Optifine situation is insane situation is insane
Optifine is FINISHED/exposed
*Picture of Optifine icon with a black bar*
I hate Charlie's videos so much
@@TheSilly6403charlie’s videos are crazy
Yea Optifine’s entire timeline feels like some Greek comedy.
Meanwhile, MCPatcher’s timeline is a Greek tragedy.
aaaaaaand now nobody cares about OF cause of Sodium and Iris, great!
i really couldn't care less if OF stopped being mantained at all since Sodium is made to run on most PCs, so everything's great either way! Would also love if forge was abandoned and completely replaced by fabric! That'd be awesome too!
honestly forge is getting abandoned in favor of neoforge
and with connector mod we get fabric, imagine if we had fabric compatibility built in so we could have 1 solid loader
Yeah, but some mods are only on 1.12 and Sodium and Iris aren't on that version. Yet at least. Just a couple days ago I was on the hunt for alternatives to Optifine for that version and no luck yet.
Soy launcher
@@TheRavenofSin1.12 is definitely going to be dead in a couple years
@@davidddo no, it is still one of the biggest versions, like 1.7 it will likely take WAAAAAY longer if ever for that to happen.
even more so when we take into acount modpacks like gregtecg newhorizons that gave a holy uniqe way to play
I wouldn't be surprised if Mojang is fully aware of all this and that's why the negotiations to work with sp broke down a while back.
Man, can't believe I actually kind of knew about this. Stumbled across some MCPatcher files when doing some texture work for GT:NH (a 1.7.10 modpack) and it got me thinking a little. Never found out that the features were BLATANTLY stolen and implemented in Optifine instead of them being merged though, that's all new to me. Jesus christ, man.
It's funny how it kept itself as closed-source, now it makes complete sense. It's always unscrupulous rats who steal code the ones who always make sure their code is as secret as possible.
Funniest thing is, the way its coded makes it far inferior to any other option; both in term of performance gain as well as overall compatibility, while most of said options are, in fact, open source.
TLDR: another thing to add do the pile of "Why optifine is a trashheap" but this time it's plaguerism instead of just being bad at it's job
Is it plagiarism when the original code was under a permissive license? You can put a NCS song into your video without getting copyright striked. It's the same with public domain and MIT licensed code which MCPatcher was. Anyone can take it and do whatever they want with it without crediting the original author.
It isn't plagiarism.
1. MCPatcher's code was in the public domain in 2011 (changed to MIT in 2013, and MIT does require crediting, but this was added in 2013... after all this had happened)
2. The OptiFine implementations were likely SP's own work, since it is missing a lot of features, has a lot of bugs, and has to work with OptiFine's custom renderer.
3. The documentation was copied, but it was credited, which is shitty, but not plagiarism.
@@m4rt_ Otherwise meaning "it is not plagarism, it is worse than plagarism. Because at least plagarized work is not actively worse compared to the original"
@@m4rt_ this is not how public domain works. unlicensed code is still protected under copyright
a license serves as a "you're allowed to do X provided you do Y"
without a license you're technically not allowed to do anything beyond reading/compiling/running the code
@@m4rt_Stealing != plagiarism. It was literally plagiarism.
Good information to know, but I’m absolutely pissed that the block never hit the corner of the screen. You’ve just lost yourself a subscriber, buddy.
i know i disliked it
we should begin a formal protest
it did right before the wii sports
It did a few times but they kept on cutting off before it actually happened
@@liminalityy_ sounds evil NGL
Is funny that you talk about the stolen MCPatcher feature at this particular time, because it sheds light on a problem that part of the Texture Pack community is currently experiencing:
Many people are familiar with CTM (Connected Texture Mod), but there's also an 'equivalent' for items, CIT (Customizable Items Texture), which lets you modify item textures according to the NBT value associated with the item. However, since 1.20.5, items no longer have NBT values and use Components. This breaks the integrality of CIT features, and the most dramatic thing is that Components are namespaced names, which requires special attention in the revision of the format to support namespace.
And therein lies the problem facing the Texture Pack community: Nobody knows what form this revision will take. Everyone's waiting for the release of Optifine 1.20.5 or 1.21, which will present to the world the new implementation decided unilaterally by one guy.
And now you're telling me that CIT was _not_ developed by sp614x? Hmm, that explains some of this mess. CTM and CIT were created by other people, and sp614x has done nothing but maintain its features at arm's length. And with the arrival of Components, that mean he need to work one a code that he would have probably preferred never to modify to such an extent (in addition to all the other problems encountered by Optifine).
while yes Sodium is an F1 and Optifine is like an RV you can just add iris to get shaders and alot of the features
Iris turns sodium into a lambo, you can do much more things compared to the F1 but still can't cook meth
@@Lucaweeso what does that make Embeddium
@@codenamec.a.t2480 paint job on sodium
@@codenamec.a.t2480 Embeddium is the weird copied chinese car whose manufacturers tell you is the better option.
Saying this because the things Embeddium added themselves (FRAPI support, Translucency sorting) are implemented terribly and Sodium 0.6, which is in public Beta now, implemented them in a way better way and provides NeoForge support.
@@timolino567 oh, so sodium is now taking the MCPatcher card play and *cooperating between authors to make the mod community better for players?* Almost like that's part of why someone like kahr was passionate about MCPatcher at a ll in the first place, wild.
Seriously tho I've heard about Sodium's dev and this is very in-character for them, rad to hear they're still slamming along with new ideas and improving things. Good on em.
Optifine made money off of features other people implemented. In short Optifine is open to a lawsuit.
Furthermore SP added features and performance improvements arent even his own, the only part of Optifine that is wholly original to him is the fog adjustrment, everything else was made by somebody else and he made money off their hard work. SP is estimated to have made hundreds of thousands of dollars off of optifine, maybe even millions.
If he stole the code, then yes, it's infringement. If he stole the ideas/format, then no, there's no infringement. I don't think he stole any code, personally.
@@skejeton he did steal the format, the folder in the older versions literally had a mcpatcher folder lol
@@skejeton Oh he had too, reverse engineer take much longer to do then making anything scratch especially when it comes to coding. MCpatcher was open source. To have the features he supposedly developed so quickly and match MCpatcher, he would have had to have taken the code straight from MCpatcher.
@@sonicmeerkat "Stealing" a format is a standard practice in modding communities and in the software industry as a whole, do you think Iris is wrong for "stealing" the shader format from OptiFine?
@@atomictem5725 Even if he took code from MCPatcher and related mods, it depends on which license MCPatcher and the related mods had. Under MIT license, for example, SP would be free to take the source code, even if proprietary, as long as he credited the original developer somewhere. If it was a GPL license, then SP would be in trouble, as he'd need to open source OptiFine as well.
I'm happy someone is talking about this again. Unfortunately, very little attention was ever given to the issue, and all of my own attempts to tell folks about it were fruitless. Although as nice as it is to see this, I'm too bitter and jaded to see things in a positive light, so I can't imagine this video will help too much. I hope I'm wrong.
(Edited my comment to remove some 'oversharing'; I struggle with that too often.)
my friend sent this to me and it’s so weird that no one knows this happened
I hate optifine even more now, fuck sp
@@Treasuryholder6 then why comment?
@@SomeoneCalledAdrian
to boost the video's engagement is a good enough reason
@@cromfrein5834fair enough
Fuck star platinum?!?
honestly "uses the same file structure" isn't bad. (or, wouldnt be, if the features were implemented correctly)
having multiple competing implementations of the same system is generally a good thing, **IF they're honest about it!**
Basically yeah. If sp had credited kahr, **most** things would be fine, butttt…. *that didn’t happen.*
yeah i mean plenty of mods right now do that to optifine, it's just scummy the way they went about it
@@Notsalmon547 he didn't invent putting files inside of folders. If the optifine dev didn't copy any of his code directly there is nothing to credit. This is the whole premise behind clean room reverse engineering.
and if it isnt just a copy and paste of a feature ..
he didnt bother to change the name of the folder .
I'm honestly glad he replicated the file structure, as this made everyone's life easier. But copy-pasting documentation, giving zero credit, AND claiming it does everything when it actually doesn't is scummy as fuck. Jesus.
In the software circle, you can not copyright an api (see Google v Oracle).
File formats can take a while to reverse engineer if no documentation exists. However, considering that mcpatcher likely had documentation on the file formats it used available to pack makers, a simple bit of reverse engineering is likely all it took to build code that'll read and interpret what is stored within those files. The hard part would have been getting optifine to support the same features mcpatcher had.
Java is also absurdly easy to decompile. If SP copied MCPatcher's code, then one round with a java decompile tool is all it'll take to reveal that.
He wouldn't even have needed to decompile it.
The MCPatcher source code is open source, and at the time (in 2011) it was in the public domain.
Though I still suspect SP still had to re-implement a lot of stuff.
@m4rt_ my point is we can decompile optifine to check if sp stole code.
@@hanro50 you should do that if you know how, it'd be interesting to see
@@hanro50 OptiFine is obfuscated so I doubt you'd be able to recover any evidence of the original code
@@Creepus_Explodus Oh boy, time to spend the next year of my life blindly guessing obfuscated function names!
i will say as an optifine hater, the file formats being the same is not something to complain about. like even outside of minecraft modding, things will share the same implementations of things all the time. should we get angry at the fabric connected texture mods as well for copying mcpatcher? should we get angry at openssl for copying the same protocol as windows' ssl code? no lol, there's enough other things to get angry at optifine (like not mentioning mcpatcher as much as they should, or being closed source / for profit) that "tries to be compatible with an existing mod" shouldn't be one of them imo
standards exist for a reason, if mcpatcher creates a standard i see no reason that other implementations of the same features shouldn't be able to use the same standard
Dear god, this is way too much like the Sonic Omens controversy. But with more plagiarism.
I really can't escape the bad omens...
the mod used an mit license, its technically okay except for the lack of credit, its just scummy
Yeah I saw noticed that too...
Edit: MCPatcher was originally under the public domain and was later changed to MIT
and that my friends is why you use the GPL
@@namelessalias0007 It's also important to note that it was changed to MIT in 2013
In 2011 when this was happening, it was in the public domain.
@@m4rt_ that doesn't make it any less scummy to (seemingly) steal open source code to make a closed source competitor with, which you are putting adverts on
@@m4rt_ I imagine it was just unlicensed back then, which defaults to full copyright.
MCPatcher's dev probably realized this later and fixed it.
ah back in the day, the real olden days, MCPatcher was also how you installed any kind of mod. I remember when you'd add Modloader then use MCPatcher as basically a mod manager lite, it worked pretty well for what was effectively the wild west with no binding APIs to anything. I always held that mod in very high regard
Funnily enough a similar thing happened with Sodium and Embeddium, but Sodium actually fought back, and hard. You can read up on it on the github issue that led to them swapping licences to polyform shield to deter Embeddium from stealing their future innovations.
That's not at all what happened. Jellysquid got pissy over Embeddedt making a hypothetical about turning embeddium into a hard fork, and ironically made him and Nolij have to hard fork the mod by blocking them from contributing to Sodium's source code.
The revenue arguments later on was due to Jelly getting desperate for money as a result of being jobless, trying to act as if Embeddedt owed them money, even though it was their own choice to not develop an official forge version.
On another note, Sodium going closed-source is genuinely stupid, and it just makes me want to support Embeddium even more.
@@ambientNexus No, Embeddium tried to literally replace Sodium. They made a Fabric version specifically to be an asshole to Jelly.
Jelly was fine with Embeddium existing but the creator was literally sending harassment campaigns and saying they're replaceable.
It's also not closed source, you're just not allowed to create a blatant copy of it. A Forge port is still legal as it's not competing with Sodium. This does not mean it complies with OSI.
I have no clue what revenue arguments you're talking about.
"For the many filthy casuals out there, Optifine might be the one and only Minecraft mod they can name" it's even worse, most people don't even think of it as a mod anymore!
Well said, Well sourced, Well researched, music timestamped, 10/10. Lets hope the youtube gods spread this like a wildfire
Actually, no.
1. They didn't look into and point out the fact that at the time MCPatcher's code was in the public domain in 2011
2. They misunderstood the difference between copying and re-implementing, and don't clearly explaining this to the viewer
3. They misrepresented the documentation as plagiarized even though it literally credits MCPatcher.
This has just lead to people misunderstanding the situation and blowing it way out of proportion, which you can see people do in the comments here.
this man @@m4rt_ really gonna give sp614x that hawk tuah for completely free with no monetary compensation
@@m4rt_Stop defending SP for what he did. Sure it wasn't illegal, sure this video gets a few things wrong, but the point is, legal or not, what SP did was still scummy, saying that "MC Patcher is not needed anymore" in the forum posts doesn't help SP's case either.
Kids these days will never look into their fireplace and be told "install mcpatcher noob"
I like thinking that optifine started getting slower updates because mcpatcher died
When all it did was copy features and it's source of features died, yeah it's gonna update slower lmao
Optifine (from my knowledge) is not even actively worked on anymore. I heard it was consistently just being ported to the newest version.
To my knowledge, the author just doesn't have time due to some life issues
Yeah I don't think if I can trust his word on that
SP does add a few features here and there from time to time (like new shader stuff and CEM model support), but it's nothing major. The last real improvement they did was when they vastly improved the Render Regions option, which they only did to better compete with Sodium (and it did help, but Sodium is still way better).
AND I WILLINGLY GAVE THEM MONEY AS A TWEEN? GOD.
Didn't like Optifine already now I don't like it even more. Scumtifine
I'm glad OptiFine is getting replaced. Closed-source corporate trash should always be replaced by open-source passion projects. It happened with recording software, it happened with video editors, it happened with image manipulation tools, and more types of software than I can even begin to try to list.
And no, I'm not just getting my opinion from this video. I've had a distaste for OptiFine for a long time due to it being closed-source and financially motivated. I first realized something was up when I learned of their policy that you can't redistribute OptiFine as part of a modpack, which is just scummy. Allegedly, this is because the creator doesn't want to be blamed for rendering issues that only arise due to other mods in the pack. But if the mod was open-source, then every mod under the sun could ensure that their mod is compatible. Outright banning the ability to even put it in a modpack, even if it's just a client-side quality of life pack, is ridiculous and has made me dislike OF for a long time.
Allegedly (and I cannot stress enough that I can't find the source for this info so take it with a grain of salt), OptiFine was approached by Mojang to have their fixes and optimizations implemented into Minecraft itself, only for the creator of OF to demand Mojang, in return, add OptiFine capes to Minecraft, presumably so he could continue to make money. The official stance is that Mojang only wanted to implement "parts" of OF, but given that info is from OptiFine itself, it could just be them trying to tell a half-truth. Hard to say, and I don't wanna give them the benefit of the doubt after everything they've done.
To be fair, ensuring compatibility with MCPatcher is a pretty reasonable idea. Less work for you, lets everyone keep using their already existing assets without much hassle.
yknow funny thing is one thing with optifine is that you dont need to format things corretly (for CIT features specifically)
so optifine CIT packs can become obsolete on CITresewn and mcpatcher and you have to reformat the entire thing to get custom models to work and stuff.
yet if it works for MCpatcher and CITresewn it will ALWAYS work for Optifine except for a few slight mishaps that are from optifines shortcomings
It's such a shame that a good dev got treated like shit by everyone because someone decided to line their pockets.
I would argue there can be a benefit from POLITELY challenging the owner of optifine. The man responsible for its fucking existence may finally be recognized and treated properly.. at the absolute minimum. At worst, however, it may destroy optifine. I think best case, of the optifine owner stands down and someone respectable takes the reigns through its death lol
the fact that optifine is dying and being forgotten brings me joy
Even if we ignore the ethical and legal dumpster fire, optifine being closed-source made it a mess to get working with other mods.
Optifine wanted to be standalone, and did it's best to maintain full compatability with mcpatcher texture packs.
Sp614x was always the type to want to implement things his own way, because he thought his implementation was better. and if he wanted $ he would have sold to mojang back in the day. he's just a control freak. there was constant drama about optifine breaking all sorts of mods, and optifine being closed sorce did no favors fixing those. Sp614x never wanted to help mods be compatable or anything. he just wants things to be his way.
MCPatcher had/has an MIT license. Perfectly legal for optifine to copy. This is just trying to start shit between people that don't understand licensing. Especially since MC patcher's development started slowing around the time of optifine's development.
21:05 homestuck pfp detected
Undertale yellow pfp detected
@@DialindenialITS DALV UNDERTALE YELLOW!??!?!??!?!??!
So, im seeing situation as:
1. Creator of MCPatcher didn't wanted to make conflicts on the forum, and being toxic in general. Because he would be banned, and maybe he was young when making it.
2. When Optifine was out. MCPatcher dev stay silent, because even if he started to stay his ground because Optifine dev literaly copypasted every features. He still has a worth argument of (Optifine was an optimization mod at the first place). And even if he asked him to delete all features. Im pretty sure that person of optifine just stole them all when MCPatcher dev went offline completly.
3. Most likely MCPatcher dev wasn't acknowledge about the scammy behaviour of Optifine dev, and because he was really tilted by the fact that Optifine dev gonna steal all features again. And because he became aware of the bullsquid Optifine dev was pulling out like crazy ad monetization, making mod close-based code, literally force players to pay him so people would download it, not maintain features that was broken by Optifine updates because he didn't care about MCPatcher at first place. So, he just. Quit?
4. After this all situation, im still happy that people started to share free copy of optifine mode because this story really shows how Optifine dev killed developer of main visual fixes, because of his rotten and beyond scummy behaviour.
Im feel really sorry about MCPatcher dev because, he probably could stop this. But he never did. Maybe in other scenario optifine would die because he didn't had anything from the visual features. Or Optifine could be a seperate mod, or MCPatcher would be a mod. Or maybe both. Anyways at end of the day, we lost an innovative guy.
I hate that Minecraft STILL doesn't have vanilla methods of doing the things you need MCPatcher for... And the easiest way to _use_ MCPatcher IS to use Optifine. Its very annoying. I wish useful resource pack functionality wasn't locked behind mods.
I don't think anyone should own a mod (idea) that is just a general and qol feature.
Optifine thrived off of being a hotspot for qol visual optimization features, so of course they would add popular features from other mods in their niche for the best player experience.
If theres 2 cool visual optimization mods and the one I don't own adds a feature, I might as well add it myself.
Not to mention i'm pretty sure back then mods couldn't be stacked... so the users of optifine would locked out of those features that are quite relevant to optifines niche if they didn't add them.
(don't quote me on that)
IF they were directly copying the code then that's a whole different thing, but simply using the same file path id say that is actually better for resource pack developers rather than a controversial thing.
And the fact that they copied the explanations of the features from mcpatcher word for word when they are designed to function exactly the same, its lazy but not immoral.
Plagiarizing the tutorial wording on how to use a mod when your mod is intent to implement the features of said another mod is just goofy, but at the end of the day its not compatible with copying the code, and that's a very important distinction.
This comment was made by the optifine apologetic community thank you for your time.
Optifine being shady and destructive to the moddine community? Never ~
Optifine using the mcpatcher folder isn't absurd. Implementing a file structure from another mod is quite common. That's how compatibility works, it would be absurd to get all the artists to implement an optifine and an MC patcher version of their pack. That being said, it doesn't excuse the fact that optifine is closed source and overly protective of their code, not contributing to other projects and just taking their work. That's scummy practice, fuck them.
Funny how Optifine replaced Patcher because of the performance side of things, and now the only reason people still use optifine is the stuff they took from it.
19:05
"Most people outside of the community didn't really pay attention until it was too late"
Oh my god it hits so close it hurts.
And not just about OF, a good few things too.
wow. I had almost no idea what MCPatcher was until now. I play a lot of 1.8 pvp, so the old texture packs still have the folder named MCPatcher, but I didn’t know what that meant
I've learned about mcpatcher while making a resourcepack that made enchanted items have different textures. I watched the UncleJam video about it and he always had the "mcpatcher" folder and all the comments were just saying to rename it to optifine so I did and just ignored it. After some time I learned about how shady optifine is and then I learned that it just stole mcpatcher. I hope the original creator of mcpatcher will perhaps return
omg a new reason to the pile of reasons to not use optifine
way way back i remember always using mcpatcher to play with my favorite texture packs, optifine was already a thing at the time but i didnt really know about it then, and when i learned about it, tried it, and finally i could get more than 20 fps in game and i saw that it had "all of mcpatchers features" i moved to using it instead back then. misa's texture pack was a favorite of mine back then, and even then i could feel it in my bones, it didnt look exactly the same, but i wasnt sure how or why.. plus my poor old intel IGP PC just really needed optifine anyways. i think that there is the saddest thing about this to me, back then i didnt have an option i simply needed optimizations for my game, even if optifine never got those mcpatcher features i prolly still wouldve moved to using optifine anyways because these two mods didnt work together (from what i recall), and between my game looking pretty or running smoothly i wouldve always chosen smooth.
15:41 you cut away just mere frames away from the logo hitting the corner, you sicko. ^^
Optifine being mostly replaced by a open source, better, and community made set of mods (iris, sodium ect.) and the game itself might be the best ending to this story that we could hope for. sp was beaten even though he could cheat.
The light flickering one fixed it because the light flicker is in the light map color palette, left to right
The y level of sprites determine what the light is for, including global light for dimensions, with the overworld section gets day and night but also the torch section, which has a flickering row
What I Liked what OptiFine have are Render Resolutions , Shadow Resolutions Anti Aliasing, Anisotropic Filtering features
Using "More Gun" at 8:50 when talking about Optifine copying the files from MCPatcher 1-1 is incredibly funny when you consider that 'More Gun' is almost a 1-1 copy of "Someone Else's Song" by Wilco. It's not even known if Valve ever got permission to do this, they just kinda did it.
The irony is so thick you could use it to make steel.
Kinda crazy I always thought Optifine WAS the newer version of MCpatcher. Poor Kahr.
Videos like these are severely underrated. Growing up on the internet has only made me realize more and more just how important documentation of this kind of stuff can be. Amazing video!
learning how to get and use MCpatcher back in 2011 was how I learned to use computers
Plagiarism and Mine(Craft)
21:03 no matter what i do it follows me
i can no longer escape homestuck
27:57 why did you cut before it hit the corner
"Good artists create. Great artists steal."
OF's worst problem isn't copying other mods, but being straight-up incompatible with other mods.
the hbomberguy references absolutely whacked me in the face
This is one of the best put together MC documentaries I have ever seen
No, it is put together, and is edited well, but it leaves out a lot of small but important details.
Like the fact that in 2011 the MCPatcher source code was in the public domain, and claiming that if you copy something, even if you credit it, it's plagiarism, which is not the case.
Ironically, I have more familiarity with MCPatcher than Optifine because I jumped from Bedrock, to modded versions of Java Beta 1.7.3- though I haven't played it much. Open formats are legitimately awesome, but "cornering the market" with your privatized weaker version helps no one. Just imagine if the PNG format was just taken by some individual who tried to take credit for it, then poorly implementing it- then extensions like APNG (animated PNG) and MNG (multiple image PNG) wouldn't exist.
you’re missing out on a HUGE point in this video. MCPatcher is licensed as MIT, which is a license that allows this kind of use of the code (copying it, modifying it and making profit on it by someone else)
The MIT license requires all redistributed code to also be under the MIT license to be protected, which Optifine is not
Edit: nevermind, MIT just requires the license to appear in the redistribution, not that it has to be under the same license. Optifine doesn't do this either, though.
this drama aged like fine wine
I think you're attributing a lot of malice when this entire story could also reasonably be viewed in a much different light; the community was much smaller than it is today, SP saw cool features that a lot of people liked and came up with a way to implement them in a way that has performance and ease of use benefits, no one complained at the time so he assumed it was fine.
I would argue that this is basically what the developers of the fabric alternatives to OF features are doing today: Bringing these features into a newer and better modding ecosystem when the previous creator seems reluctant or uninterested in doing so.
The part at 24:00 where you say that the changes imply that SP knows what he did was wrong seems like a huge leap to me, both of the graphics you showed, especially the skybox one are just better and more easily legible than before.
I think it is important to note that SP didn't steal the code for these features, only the ideas - while copy-pasting the documentation is definitely a weird thing to do, I don't think a mod developer plagiarizing text that very few people read matters all that much.
Nitpick: I think it's fair to say that SP solely developed and maintained Optifine for 10 years, I get that one could claim that ideas are also part of developing, but in practice no one would say that SP or Khar "developed" CIT Resewn.
All that being said, I still really enjoyed this video as a documentation of a crucial and often overlooked part of Minecraft history and really liked the style of the video, and I hope this comment doesn't come off as mean or anything.
Don't take this as a mean thing, I respect your input and wanted to clear a few things up
People definitely did complain at the time, I included that in the video (5:50) you can go to the source and see a lot of other people complaining too. This was directly after more features got stolen.
Also I feel like, sure combining features into optifine is OK i guess, but actively telling people to not download the mod that you got it from (MCPatcher not needed) seems malicious to me. And I feel like if it was some kind of virtuous combining of features, somebody would have said that. The community was definitely smaller, but not tiny by any means. This wasn't baby's first mod, it was after 2 years of mods before it.
And also also, you do make a good point that it would be weird to say that SP or Kahr "developed" CIT Resewn (and maybe that wasn't the right wording in the video), but I feel like ignoring their contributions is bizarre. CIT Resewn in particular mentions MCPatcher and Optifine explicitly as being where the features come from, you can't really miss it. The only way to find out about MCPatcher is to go into the optifine documentation, or i guess to read the single line that says that it isn't needed with no direction
Also also also if SP wanted the images to be more legible, why didn't he just make his own? why did he copy them in the first place if he cared so much about legibility? That's why I think this was a reaction to criticism of copying images, rather than just changing them to be more legible. If he cared about that, he would have just made his own image.
@@DIMM4_ All good, I'm happy that we can earnestly discuss such a niche topic :)
Saying that no one complained was worded wrongly, what I meant was that no one involved in the creation of the original mods complained (at least not from what is shown in the video, I haven't done any research into this), Khar even explicitly says that he is fine with mods implementing each other's features.
For the images, I agree that he should've just made his own images in the first place, but I think it's very conceivable that he started caring about legibility sometime between 2011 when the features were added and 2016 when the textures were changed (unless there is some evidence I missed that a lot of people were complaining about the stolen images in the meantime).
I personally don't interpret "MCPatcher not needed" as telling people not to download MCPatcher, it's just informing people about the fact that they don't need both MCPatcher and Optifine, CIT Resewn also says that Optifine or MCPatcher aren't required.
Overall, the video paints the picture that SP had some kind of malicious intent and was trying to basically monopolize this space in Minecraft modding to make money.
While his actions obviously did end up having negative effects on a good chunk of people, as you show in the video, and I think he MCPatcher should be clearly credited on the OF website, I just don't believe that SP actually had bad intentions when he took the MCPatcher features.
@@DIMM4_ "MCPatcher not needed" MEANS NOTHING... This is a stupid assumption and this entire video is a pile of shit. You should be ashamed of it. Do better.
@@SimplyMattis The road to hell is paved with good intentions.
SP may not have intended to screw over Kahr, but the community lost a prominent Minecraft modder because of a lack of proper acknowledgment. Kahr almost certainly stopped developing MCPatcher because SP refused to credit his work and therefore his mod died and he was even insulted / criticized by Optifine users as a result, which is pretty awful and definitely at least partially SP’s fault.
We don’t even know if Kahr is alive, and we may never know, because SP didn’t acknowledge where he got his source code. Just because it’s legal for him to take the code without credit doesn’t make it right.
I first learned of all the scum about OF when i heard rumors of Mojang reaching out to SP to get a few of his features into the base game, and perhaps a job there. But then he wanted an unreasonable compensation so the whole thing got scraped.
Combined with the fact that it no longer plays nice with other mods, and the fact that the Sodium family of mods now is a thing, i dont see a reason to support Optifine.
The weirdest thing to me is that MCPatcher is open source under MIT. If SP was copying the features, why not implement the source code instead of shittily copying it?
OptiFine is now becoming outdated because of vanilla Minecraft.
I love this.
In software development, there's a difference between stealing ideas and implementing API's. MCPatcher's file format is nothing more than an API; a way for a (texture pack) developer to specify what they want MCPatcher to do. Let's call this file format MFF, the MCPatcher File Format. Now there exists an implementation for this format, also called MCPatcher, by the same creator. This is the actual MCPatcher program that loads the texture pack (defined in MFF), and puts it into the game.
OptiFine did not steal features. Nor did it "steal MCPatcher". It simply implemented MFF. It added support for texture packs that originally would only work with MCPatcher. Stealing what MCPatcher did would be copying the implementation, copying the code. If OptiFine had literally just copied the MCPatcher code into itself, that would be theft. But a implementing a format isn't theft. Just because someone made a new MP4 player, doesn't mean that they "stole" MP4 from the people who made the first MP4 player and who designed the format. They wrote their own implementation.
Was it handled well by OptiFine by saying "MCPatcher Not Needed", pushing people to not use it anymore? Absolutely not. Not cool. But it still wasn't theft, it just guaranteed good interoperability between the two no matter what OptiFine would add in the future. It eliminated the need for an external program, allowing you to tune these settings in-game. And it guaranteed backwards compatibility with any packs that had already been made. Believe me, if OptiFine wanted to "steal" features from MCPatcher, it would've defined its own format, and would've forced pack developers to use that new format instead. This would ensure that any new packs made for OptiFine would *not* work with MCPatcher, which is something you see big companies do all the time to undercut their competitors.
This was the comment I was looking for.
I feel like its different because the company that makes MP4 (ISO) makes money from shareholders and donations, not directly from people using it, while MCPatcher *does* rely on people downloading the MCPatcher Mod to make money. While the formats are similar, you still had to convert MFF packs to OFF packs. It seems like Optifine cut MCPatcher's life support, by using their big features and influence to sway people to one side. It's kinda like what apple does a lot with things like spotlight search replacing apps like Sherlock.
I feel like you can't separate MCPatcher the file format from MCPatcher the mod, since they rely on each other to exist, that's why they have the same name.
@@DIMM4_ The reason OptiFine had to port the mods from MCPatcher is because of the custom renderer, making the original mods incompatible with OptiFine. Even outside modding communities, proprietary formats can and often are used by competitor companies if these formats become the standard.
I certainly don't think asking for permission would have hurt. But the MCPatcher mod seems to be licensed under the MIT license and I think it was also open source so it technically would have been find to take all of the code... if you provided attribution
An API or File Format can be copyrighted. It's like how you can't just implement HDMI without any license from the HDMI consortium. If you could do it, AMD wouldn't need to ask the consortium for license permission to implement HDMI 2.1 support for their cards on Linux.
The funniest part is that optifine STILL hasn’t updated for 1.21
It has. And it sucks, it is still playing catchup. To be entirely fair, the replacement mods are not perfect either, Sodium is still cleaning up transparency sorting issues.
But the goofy part being that Optifine 1.21 preview versions launched with a wack issue that swaps around colorvalues. The game having wrong colors is something one sees literally right away. 😂
I understand what you're trying to say here, but the way mcpatcher was licensed makes what optifine did completely legal. In mcpatcher's license all of the things sp614x did (even if they directly took the code from mcpatcher, without asking, and redistributed it, is allowed. Even making money off mcpatcher's it is specifically allowed by the MIT license mcpatcher used. This is how open source software works. I develop minecraft mods too and I license my mods using the same license mcpatcher does and I have zero issues with this. It's how open source software works, mcpatcher could have just used a less permissive license if they didn't want this to happen. The only potential issue is that optifine might not include the copywrite notice or liability disclaimer that the MIT license also requires, but overall not many people care. Claiming this is plagiarism is ignorant about how open source code works.
I loved that you called us "fucking hooligans"
Since, you are right.
i was kinda sad when i switched to sodium cuz i held optifine in such high regard but I realise now that i shouldn't have, glad i switched now
"Can I copy your homework?"
"Sure, but don't make it too obvious that you copied it."
I don't know man, this doesn't really seem like stealing. It just seems like any ordinary product competition. Like Apple implementing screen recording after Android did it first.
Also, making Optifine compatible with MCPatcher packs doesn't seem like an issue to me. Its like making your new car compatible with standard gasoline. Would you say that the new car is stealing the idea of gasoline? Its similar to how Iris basically killed Optifine in terms of being the de facto shader mod. One of the main appealing features of Iris was that it was compatible with existing Optifine shaders.
The text copying you mentioned is pretty blatant and bad though.
iPhones and Androids each run a different, mutually-exclusive operating system, so you can't just develop a "screen recording mod" that runs on both operating systems. OptiFine, however, could have (and for a while did) run alongside MCPatcher just fine, so that immediately puts into question any attempts to recreate features from another actively developed project (you can just run both mods!), but there can still be good reasons for it. One reason, as discussed in the video, would be if the other project was abandoned and the author released their code to the public, but that's not applicable here. Another common one is to develop ports to other mod loaders, which you could argue is relevant here as OptiFine was quicker to accept Forge than MCPatcher, but from the timeline of events I don't really believe this to be relevant.
Instead the main reason I want to focus on would be if you disliked how the other project implemented it, and wanted to do it your own way, or at least improve and develop upon the others' idea. One example of this would be how Mojang has implemented shaders such as the lightmap shader or general internal shaders completely differently from any community project and vice versa. The issue is that OptiFine didn't do much of this? For some features yes, OF did provide addons, but for others it provided merely matching (if not incomplete) implementations. And all that of course is not to mention the fact that OptiFine then proceeded to monetize its product through ads and EULA-breaking donations (though quite frankly who cares about the EULA's thoughts on money), essentially capitalizing off someone else's work.
Regarding your comparison to Iris, yes, the mod reimplements a feature from OptiFine, but there's some key differences. The first is that the mod is highly focused, revamping essentially just one of OptiFine's features (which itself was not entirely original, AFAIK, but that's a story for someone else to research another time). The second is that it is committed to developing new functionality that is increasingly being used by artists to create better and better shaders not possible under OptiFine's system. And yes, it too is monetized, but much less egregiously, and to an extent I think most (including Mojang's EULA) would consider reasonable. Hell, if you really hate ads, you can totally compile Iris from source without ever seeing an ad (except for maybe a Patreon link).
An argument could be made for Optifine that keeping the mcpatcher file structure initially started for ease of compatibility even if it wasn't explicitly discussed or agreed upon, but as it goes further down the line it's clear there was a change in motive. I only ever used Optifine for about a year but it was always clunky so I guess I lucked out by being made to switching to Fabric/Iris systems.
From what i understand, MCPatcher was completely open source. That means that copying code is allowed. No one would make their stuff open source and object to an upgrade by someone else, not that they would have any grounds to do so anyway.
Also, adding support for other existing software is just a nice bonus. There's 0 wrong with that, it is just the norm.
The copied documentation is also normal. There's no reason to re-invent the wheel just to look like you did more effort where it wasn't even necessary.
I think people just don't understand how software development works and think this is just plagiarism like stealing someone's art. Making a replacement that is superior to existing software is never something bad. You'd have to be an a-hole to object to someone doing it better when it is a free thing for everyone.
The only issue here is that they made OF closed source. Which is pretty scummy.
The closed source only fans is litterally the entire reason why this is bad
But that explains why he was reluctant
@@timohara7717 again, it is scummy, not illegal nor unheard of.
Maybe he had a good reason (safety concerns, for example), altho he probably didn't.
But the entire video harps on stuff that is normal for software development, the closed source part is mentioned at a glance and barely.
@@timohara7717 Yes, it being closed source is bad, but the other claims in this video are unsubstantiated. Making a closed source minecraft mod doesn't make you some sort of cartoon villain that needs a minecraft youtubers community harassing you
@@AsadAbbasi-ss4bh look it up elsewhere then, it was already said years ago
It'd honestly be nice to have a single mod that reimplements MCPatcher's features, as they're meant to work, for modern Minecraft, with proper credits to kahr and the other developers.
We likely won't get another MCPatcher, the modding community has evolved past those days, but a single mod for Quilt (and maybe NeoForge) that implements resource pack features would be nice
I'm so glad over the past few years people are finally ditching optifine, it's such a nightmare to work with as a modder due to it being closed source and still patching the game directly, which NOBODY else does anymore in modern mc
I've always wondered why so refuses to open source optifine given how much it could help out with its development and making modders more willing to work with it, and im wondering if mcpatcher is related to why
24:04 Angry bird sound effects
Always a good day when i see a new upload. The vibes really are Hbomberguy but minecraft
To be fair, it wouldn't make any sense to break compatibility with already existing texture packs
Wow, this video is incredible well done, amazing job :D
Can't believe the channel is so small, this could easily be some 500k youtube channel in terms of quality.
Good shit youtube for this recommendation :D
Something ETF/EMF is doing is adding a lot of features that werent a thing in optifine, expanding upon it more for resource pack creators to do more cool stuff