Skip to main content
Arqade

Return to Answer

replaced http://gaming.stackexchange.com/ with https://gaming.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

This is a tricky subject. Minecraft has sort of forced us to change our perspective on a lot of things. And while I've often held that technical issues questions get shot down without anyone bothering to at least attempt to figure it out... Where we are at now is not a good place.

I've thought about this over the past couple of days. I really have. I cannot, in good faith, justify keeping modded crashes of any sort for any game (obviously Minecraft is the most common). There are a few reasons for this, but first, let's get one thing out of the way...

Vanilla crashes

Let's get this out of the way: I can justify Vanilla crash reports, though it might be helpful to point users to Mojang support as well. The problem scope is much, much narrower here, and we already have a canonical questioncanonical question that covers a lot of these cases. (org.lwjgl.LWJGLException: Pixel format not accelerated has been reported 1755066 times in Minecraft 1.8.3).

Modded Crashes

Now that that's clear, let's look into the world of Minecraft modding.

Minecraft has a lot of mods. There are over 2000 mods hosted by Curse alone. This includes different versions of the same mod made for different versions of Minecraft, so the actual number of distinct mods is probably around half of that, but even still, there are a lot.

Modded crashes are vastly more common than vanilla. This isn't the problem, though. The problem isn't even that mod conflicts are extremely common. These days, with Minecraft Forge working how it does, mod conflicts are actually pretty rare (though OptiFine is one notable exception that most modmakers do not support, but I digress). The problem is that the crashes have such variety that the questions become, themselves, too localized.

Not even localized to system details or Java version (that is rarely the case these days), but localized to one's particular world and mod setup. Anybody can put together a mod pack these days, and, as such, everyone's mod setup is slightly different, which makes troubleshooting tricky.

To recap, I can justify allowing Vanilla crashes. I cannot justify allowing modded crashes. It is a gaming topic, to be sure, however, modded environments are so unique, which makes their crashes extremely localized.

This is a tricky subject. Minecraft has sort of forced us to change our perspective on a lot of things. And while I've often held that technical issues questions get shot down without anyone bothering to at least attempt to figure it out... Where we are at now is not a good place.

I've thought about this over the past couple of days. I really have. I cannot, in good faith, justify keeping modded crashes of any sort for any game (obviously Minecraft is the most common). There are a few reasons for this, but first, let's get one thing out of the way...

Vanilla crashes

Let's get this out of the way: I can justify Vanilla crash reports, though it might be helpful to point users to Mojang support as well. The problem scope is much, much narrower here, and we already have a canonical question that covers a lot of these cases. (org.lwjgl.LWJGLException: Pixel format not accelerated has been reported 1755066 times in Minecraft 1.8.3).

Modded Crashes

Now that that's clear, let's look into the world of Minecraft modding.

Minecraft has a lot of mods. There are over 2000 mods hosted by Curse alone. This includes different versions of the same mod made for different versions of Minecraft, so the actual number of distinct mods is probably around half of that, but even still, there are a lot.

Modded crashes are vastly more common than vanilla. This isn't the problem, though. The problem isn't even that mod conflicts are extremely common. These days, with Minecraft Forge working how it does, mod conflicts are actually pretty rare (though OptiFine is one notable exception that most modmakers do not support, but I digress). The problem is that the crashes have such variety that the questions become, themselves, too localized.

Not even localized to system details or Java version (that is rarely the case these days), but localized to one's particular world and mod setup. Anybody can put together a mod pack these days, and, as such, everyone's mod setup is slightly different, which makes troubleshooting tricky.

To recap, I can justify allowing Vanilla crashes. I cannot justify allowing modded crashes. It is a gaming topic, to be sure, however, modded environments are so unique, which makes their crashes extremely localized.

This is a tricky subject. Minecraft has sort of forced us to change our perspective on a lot of things. And while I've often held that technical issues questions get shot down without anyone bothering to at least attempt to figure it out... Where we are at now is not a good place.

I've thought about this over the past couple of days. I really have. I cannot, in good faith, justify keeping modded crashes of any sort for any game (obviously Minecraft is the most common). There are a few reasons for this, but first, let's get one thing out of the way...

Vanilla crashes

Let's get this out of the way: I can justify Vanilla crash reports, though it might be helpful to point users to Mojang support as well. The problem scope is much, much narrower here, and we already have a canonical question that covers a lot of these cases. (org.lwjgl.LWJGLException: Pixel format not accelerated has been reported 1755066 times in Minecraft 1.8.3).

Modded Crashes

Now that that's clear, let's look into the world of Minecraft modding.

Minecraft has a lot of mods. There are over 2000 mods hosted by Curse alone. This includes different versions of the same mod made for different versions of Minecraft, so the actual number of distinct mods is probably around half of that, but even still, there are a lot.

Modded crashes are vastly more common than vanilla. This isn't the problem, though. The problem isn't even that mod conflicts are extremely common. These days, with Minecraft Forge working how it does, mod conflicts are actually pretty rare (though OptiFine is one notable exception that most modmakers do not support, but I digress). The problem is that the crashes have such variety that the questions become, themselves, too localized.

Not even localized to system details or Java version (that is rarely the case these days), but localized to one's particular world and mod setup. Anybody can put together a mod pack these days, and, as such, everyone's mod setup is slightly different, which makes troubleshooting tricky.

To recap, I can justify allowing Vanilla crashes. I cannot justify allowing modded crashes. It is a gaming topic, to be sure, however, modded environments are so unique, which makes their crashes extremely localized.

Source Link
Unionhawk Mod
Unionhawk Mod
  • 34.1k
  • 31
  • 79

This is a tricky subject. Minecraft has sort of forced us to change our perspective on a lot of things. And while I've often held that technical issues questions get shot down without anyone bothering to at least attempt to figure it out... Where we are at now is not a good place.

I've thought about this over the past couple of days. I really have. I cannot, in good faith, justify keeping modded crashes of any sort for any game (obviously Minecraft is the most common). There are a few reasons for this, but first, let's get one thing out of the way...

Vanilla crashes

Let's get this out of the way: I can justify Vanilla crash reports, though it might be helpful to point users to Mojang support as well. The problem scope is much, much narrower here, and we already have a canonical question that covers a lot of these cases. (org.lwjgl.LWJGLException: Pixel format not accelerated has been reported 1755066 times in Minecraft 1.8.3).

Modded Crashes

Now that that's clear, let's look into the world of Minecraft modding.

Minecraft has a lot of mods. There are over 2000 mods hosted by Curse alone. This includes different versions of the same mod made for different versions of Minecraft, so the actual number of distinct mods is probably around half of that, but even still, there are a lot.

Modded crashes are vastly more common than vanilla. This isn't the problem, though. The problem isn't even that mod conflicts are extremely common. These days, with Minecraft Forge working how it does, mod conflicts are actually pretty rare (though OptiFine is one notable exception that most modmakers do not support, but I digress). The problem is that the crashes have such variety that the questions become, themselves, too localized.

Not even localized to system details or Java version (that is rarely the case these days), but localized to one's particular world and mod setup. Anybody can put together a mod pack these days, and, as such, everyone's mod setup is slightly different, which makes troubleshooting tricky.

To recap, I can justify allowing Vanilla crashes. I cannot justify allowing modded crashes. It is a gaming topic, to be sure, however, modded environments are so unique, which makes their crashes extremely localized.