Zamiel

How to Report a Bug

Oct 16th, 2022 (edited)
295
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.15 KB | None | 0 0
  1. + --------------------+
  2. | How to Report a Bug |
  3. +---------------------+
  4.  
  5. Did you find a bug in Racing+ or another Binding of Isaac mod? This guide is for you.
  6.  
  7. First off, thank you for reporting the bug. By taking the time to investigate and report bugs, you make the mod better for everybody.
  8.  
  9. Before reporting a bug, it's essential that you do some investigation first in order to narrow down the problem. Perform the following steps.
  10.  
  11.  
  12.  
  13. Step 1 - Save the Log
  14.  
  15. - When you play the game, Isaac writes information to a file called "log.txt". By default, it is located at:
  16. C:\Users\[username]\Documents\My Games\Binding of Isaac Repentance\log.txt
  17. - As soon as the bug happens, back up the log.txt file. This is because as soon as you reopen the game, the log.txt will be deleted.
  18. - The log.txt file can contain useful information to identify what the actual bug was, like a specific error message or a reference to the line number of the code that the error happened on.
  19. - When you report the bug, provide the log.txt to the developer.
  20.  
  21. Step 2 - Reproduce the Bug
  22.  
  23. - In the log file, you can find the seed of the run that you were playing when the bug happened. The corresponding line will look something like this:
  24. [INFO] - RNG Start Seed: H7YQ 8ZRB (814190760) [New, 1]
  25. - Start a new run from scratch and replay the seed. Perform all of the same steps that you did again EXACTLY.
  26. - Does the bug happen again?
  27. - If yes, then move on to step 3.
  28. - If no, then it will be difficult for the developer to fix the problem. Try to perform some more investigation and experimentation, using the debug console as needed, to try and replicate the bug in a different way. You can also check the log.txt file to see if there are any errors in it. (Do a Ctrl + f for "error".) If there are no errors in the log and you cannot replicate the bug whatsoever, there you can still report the error to the developer, but there's probably nothing at that they can do.
  29.  
  30. Step 3 - Reproduce the Bug Again Minimally
  31.  
  32. - Isaac comes with a debug console so that you can easily give yourself any item, warp to any room, warp to any floor, and so on. See the wiki for more details on how to use the debug console.
  33. - Using the debug console, reproduce the bug again, but now instead of following the EXACT steps from your original run, just warp directly there and try to reproduce the bug.
  34. - Does the bug happen again?
  35. - If yes, then try to remove one part of the setup to see if that part is actually necessary for the bug to happen.
  36. - If no, then try to add one part of the setup from before to see if that part is actually necessary for the bug to happen.
  37. - This goal is to find the ABSOLUTE MINIMUM amount of steps that is necessary to reproduce the bug.
  38. - If you are using the console, compile all of the console commands together so that the mod developer can copy paste those commands into their own console.
  39.  
  40. Step 4 - Provide the Minimal Steps to Reproduce
  41.  
  42. - Provide the minimal steps to reproduce to the mod developer, along with the copy of the log.txt.
  43. - If you are reporting a bug for Racing+, then do it in the #bugs channel on the Isaac speedrunning discord: https://discord.gg/JzbhWQb
Advertisement
Add Comment
Please, Sign In to add comment