How to report bugs - RobertSkalko/Mine-and-Slash GitHub Wiki

The most important thing in bug reporting is to make sure you know WHOSE FAULT IT IS!

Or in the very least to narrow down the list of suspects. Nobody likes to be given a bug report that turns out wasn't their problem in the first place.

FIRST THING TO DO is to open the latest log and check if the error has a mod name near it. For example:

java.lang.ClassCastException: net.minecraft.entity.monster.ZombieEntity cannot be cast to net.minecraft.entity.player.PlayerEntity at com.robertx22.mine_and_slash.dimensions.blocks.DungeonPortalBlock.onEntityCollision(DungeonPortalBlock.java:67) ~[?:?] {re:classloading}

You can see the first thing in the error is "mine_and_slash" code. So it's fine to report it to the dev. If you see more than 1 mod name then it's possible it could be any of them, but it's usually the fault of the mod closest to the error.

If you can't see any mod name near the error log then it's more complicated. In that case do the following.

  1. Backup your save.

  2. Remove all of the following mods: (you can just move them to another folder away, it's important they don't load)

  • Optifine
  • random "tweak/fix/performance" mods, I don't care how much you trust them, they are usually invasive and are a probable cause of issues. Stuff like: fastcraft, phosphor etc.
  • mods like "faster workbench" that seem like they do very little
  • any mods you recently updated or installed
  • start removing all coremods or mods that use mixins

If the problem is gone, start adding the mods back 1 by 1. Report the bug to the mod that causes the bug again after it's added.

If it's not any of the random mods, then it's more complicated. You can then try the nuclear option:

Option 1) Remove all mods except the one you think is causing the issue (and that mod's libraries), and see if the problem is still there. If the problem is gone, then that probably means you're right

Option 2) Remove only that mod which you think is causing an issue. If the issue is gone, it's probably that mod.

Both of these options separately just make it likely you found out the culprit, but you can only be sure if you use both and they are both right.

If only 1 is true, that means the issue results from a mod combination, meaning you likely won't know whose fault it is.

Things to note:

  • just because a problem happens after X mod is added, does not make it 100% sure that X mod is the issue. It could just be using a feature that Y mod corrupted.
  • most of the time the culprit is found in the log, and there's no need to go nuclear in testing
  • every false bug report wastes time of mod devs and makes them less trusting of the bug reporters.