He is openly against putting in config options, calling them "ticking bug time bombs".
Lets say there is a block that is quite powerful and requires energy to function. There most likely exists people who then complain about the block being too powerful and easy to obtain/craft and doesn't draw near enough power for what it does. There are a couple of options here:
-The author gives them an option to not play with that block anymore. Go ahead and disable that feature.
-The author asks for input on alternative means of crafting said block and considers community feedback, makes the power use configurable, and allows for configurable nature of what the block actually does. We now have options for recipes, power drain, usage, and likely can still disable the block.
-The author posts rants on twitter/reddit about people not being happy with his or her mod.
When the mod that you make boils down to being a shiny, uber-powerful, mod made completely for convenience and making aspects of the game easier it most certainly will appeal to the kind of audience that posts dumb bug reports. This is even more apparent when you have one of the most popular mods out there. I don't want any aspect of a mod I play with to be "ridiculous".
If you don't throw every single feature you can think of in one gigantic mod, stupid inter-feature problems are less likely to pop up.
Also - opensource solves some of these problems. (gotaa get that open-source plug in somewhere
)