Gamabunta00

So from my end the main technicpack.net site is down/showing a cached page from there web service, also i was looking at the console and for a minute i thought it was a legitimate bug that the launcher showed the error "minecraft.net is down" when technicpack.net was down.

Well for the Microsoft vs Elorram example, i would have to say its the whole idea of Microsoft being a "big bully" company that makes people feel it is justified to do such things, whereas Elorram is just a developer who is doing this of there own free will, and that makes it right to protect them (though i the case of FlowerChild the community kinda screwed him over, so of course as many of us would, he screwed them over lol) As for the diffrence in wanting a mod to be a part of a modpack, i think its a 2 pronged problem. 1. The mod developer (while credited in some way) isnt the one that get praise for the modpack, the modpack dev's do. Now you have to think, who is the one that put the work in to make theese things that make the modpack possible, of course with the convenience of a modpack with an installer such as tekkit, its easy to just assume they did all the work. When to be completely honest, they just created a launcher, not even from scratch (not to discredit them) its a fork of spout, who also probably get little credit as well. The technic pack team may try to credit them, but there is only so much you can do to make a obviously lazy person do anything. 2. The 2nd part is more negative. Modpacks are inherently buggy, there are 3 diffrent types of people who cause the issues and can solve them. Stupid/oblivious Users, Modpack Developers, and Mod Developers. Generally speaking Mod Developers tend to take flack from people who run into any of theese issues. Now how is Mod Developer A supposed to make sure his stuff is compatible with Mod Developer, B, C, and D, if Modpack Developer, E is changing things to make them compatible. The answer is they cant, and trying to leads to real problems with the mod being sunk under hundreds of clashing block id's "bugs". People tend to say, "Hey, i placed a buildcraft enginge in tekkit and it crashed, it didnt crash before, so it must be buildcrafts fault." Now this is an understandable assumption, it is justified within reason and probably within most users understanding of modding minecraft. So now the bug is being reported to the wrong person, the mod developer is trying to fix a bug that isnt there problem, and the user is generally oblivous to all of this as they just dont know any better. Its no-ones fault in particular, its just a simple misunderstanding. But it led to all of that trouble for the mod developer, who will eventually figure out its not there bug and report it to the modpack team in place of the user, while recieving spam on there thread like, "WHY UR MOD NO WORK!!!" Thats the way i see theese issue's. The other part is that some mod developers have a vision of how they want minecraft to be played with there mod( Better Than Wolves by FlowerChild for example). Better Than wolves is a very VERY well thought out mod, the point of it is to slowly extend vanilla minecraft play and provide Endgame rewards, whereas redpower, buildcraft, and industrial craft, all tend to push you in an all out sprint to the finish line using automation as the way to get to the endgame vs the endgame being where automation begins. Also they may just want proper credit for there work and they may want to keep it distributed by them because they want credit where credit is due. The big difference between the xp patch and the 1.4.5 update, and why some Minecraft Mod authors dont want their work distributed is that its not an injustice to force people to take some time and install a mod for free, especially when they are kind enough to make it for free and only want proper accreditation, whereas it is to make people but a 100$ operating system to play a 60$ Game that they already own.