forked from Vazkii/br101
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
95 lines (92 loc) · 8.79 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
<html>
<head>
<title>Bug Reporting 101</title>
<link rel="stylesheet" href="page.css"></link>
</head>
<body>
<div id="left">
<div class="title">Write your Bug Report here:</div>
<textarea type="text" id="bug-report-area"></textarea>
<div id="footer">Bug Reporting 101 by Vazkii - Fork it on <a href="https://github.com/Vazkii/br101">Github</a></div>
</div>
<div id="right">
<div id="step">Step <span id="step-counter">0</span></div>
<br><hr>
<div id="inst-container">
<div id="inst0" class="instructions inst-default">
Hey there. If you're here, that means you want to report a bug in a mod! Well, you're in the right place. Before we get started, though, let's look at some important things (click on any to see why it's important):<br><br>
<div id="why0" class="why">Are you in the latest version of the mod?</div>
<div id="why-expl0" class="why-expl">
Reporting bugs in old versions of mods is a bad idea, these bugs might have been fixed in newer versions of the mod and you might just be wasting the modder's time. If you're using a modpack, try updating the mod manually, and if it works, ask the modpack's creator(s) to update the mod.
</div>
<div id="why1" class="why">Are you in the latest version of Forge?</div>
<div id="why-expl1" class="why-expl">
Having the latest version of Forge is crucial to pointing out bugs. If you can reproduce an issue with an old version of Forge, but not with the latest version then it works fine. Old versions of Forge should not be supported, as the new ones, more often than not, contain major bugfixes.
</div>
<div id="why2" class="why">Are you using vanilla Forge (not MCPC+)?</div>
<div id="why-expl2" class="why-expl">
MCPC+ is a bridge between Spigot (a fork of Bukkit, providing better optimization and some other features) and MinecraftForge. In sum, it allows you to use Bukkit Plugins and Forge Mods in the same server.<br><br>
Due to the ways it uses to create this bridge, it's to expect some mods to be incompatible with it. Mods are not meant to be built for MCPC+ by default, if some functionality is not working with MCPC+ installed but works fine without it, report the issue to the MCPC+ team instead.
</div>
<div id="why3" class="why">Are you using Optifine?</div>
<div id="why-expl3" class="why-expl">
Optifine, as implied by it's function, changes the basic way things are drawn on the screen. Some mods depend on complex rendering sequences to get the desired visual effect for their blocks/items/entities/whatever. If something looks out of place with optifine installed, try it without optifine and see if it looks right, and if it does, the issue has to do with the interaction between the mod and optifine.<br><br>
As Optifine is a closed source mod, workarounds are not possible without technically violating the license. That's the main reason why most mods do not support optifine.
</div><br><hr><br>
After you've checked all of these out and are confident the issue doesn't lie in any of the problems above stated, by all means, carry on!
</div>
<div id="inst1" class="instructions">
Start by briefly describing what the issue is, try to be as concise as possible. Make sure you highlight details, any cross mod interactions should be explained, the more you leave out, the harder it is to find the issue and fix it.<br><br>
If you're struggling to put an explanation of the issue in words, take a screenshot or a video. Minecraft has screenshots built in with the F2 key. After you took a screenshot, upload it to <a href="http://imgur.com/">imgur</a> or any other image hosting website.<br><br>
<div class="examples">Examples:</div>
<div class="example-box">
<b>Bad: </b><i>i tried to create the blocky thingymajig and my game crashed help please</i><br><br>
<b>Good: </b><i>I was trying to create the Blocky Thingymajig, I gathered all the crafting components, when I pulled the item out of a Super Crafting Table from the SuperCrafting mod, my game crashed.</i>
</div>
</div>
<div id="inst2" class="instructions">
Make sure to include the FML log, regardless of your game having crashed or not. The log contains all sorts of important information such as which mods are loaded, alongside which versions. Make sure to check out the following points (click on them for more info):<br><br>
<div id="why4" class="why">How do I get the log?</div>
<div id="why-expl4" class="why-expl">
Start off by going to your .minecraft folder, as you normally do to install a mod. You should have a "logs" folder. Inside it, look for "fml-client-1.log", open it with Notepad or your text editor of choice (Notepad++ is pretty good!) and there you go, there's the log.
</div>
<div id="why5" class="why">Where do I put the log?</div>
<div id="why-expl5" class="why-expl">
Absolutely <b>never</b> paste the log next to the report, doing so causes an incredible amount of clutter and is really hard to look at. Instead of that, put the log in a paste hosting website and attach a link to it, here's a few examples:<br><br>
<a href="http://pastebin.com/">pastebin</a> <a href="http://hastebin.com/">hastebin</a> <a href="https://gist.github.com/">gist</a> <a href="http://www.pastie.org/">pastie</a> <a href="http://puush.me/">puush</a>
</div><br><br>
<div class="examples">Examples:</div>
<div class="example-box">
<b>Bad: </b><i>crash log: (crash log here)</i><br><br>
<b>Good: </b><i>FML Log: <a href="http://puu.sh/8BDKc.log">http://puu.sh/8BDKc.log</a></i>
</div>
</div>
<div id="inst3" class="instructions">
Review your issue. Make sure it's well structured, try to look at it from the point of view from someone who is trying to follow the steps you give them to reproduce what happened.<br><br>If the modder can't read what you did and reproduce the issue themselves, more likely than not, you left a step out. Try to follow it yourself and see if you can have it happen again with the information you gave only.<br><br>
<div class="examples">Example:</div>
<div class="example-box">
My game crashes when I try to create a Blocky Thingymajig from your mod using a Super Crafting Table from the SuperCrafting mod. I can get it to happen every time by simply placing the materials in the table and pulling the Blocky Thingymajig out (both via shift-click and just a normal click).<br><br>
This does not happen with any other item from any other mod (at least from the ones I've tried). The crafting works fine with a normal vanilla Crafting Table.
<br><br>
FML Log: <a href="http://puu.sh/8BDKc.log">http://puu.sh/8BDKc.log</a>
</div>
</div>
<div id="inst4" class="instructions">
Your issue is done, time to report it. The best place to do it varies from mod to mod. The best places to do it generally are on the mod's issue tracker (if one exists) or the mod's forum thread. Do <b>not</b> report a bug over IRC, Twitter or private messaging of any way, this makes your issue easy to forget, or disallow other people than the modder to help you with it.<br><br>
The best way to do it is to look for "<b>issue tracker</b>" or "<b>github repo</b>" on the mod's thread or website. That is the preferred way for most modders to track their issues (duh), as it lets them label the issue, edit it case something needs to be set, and of course, have all the issues categorized in a specific area.<br><br>
Before you pull the trigger and submit the issue, though, <b>make sure nobody else reported it</b>. Look around in the last few pages of the thread, or the issues page in the issue tracker, if somebody already reported the issue, reporting it again is a simple waste of time, both for you and for the modder. If you're looking on the issue tracker, make sure to check the both the open and closed issues, as the issue might have been fixed already.<br><br>
</div>
<div id="inst5" class="instructions">
And there you go, you have successfully reported your issue!<br><br>
If you're interested on learning more about bug reporting, Simon Tatham wrote <a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">an essay</a> about that very matter, if you're committed to be an awesome bug reporter, it's definitely worth a read.<br><br>
<a href="https://twitter.com/intent/tweet?text=I%20just%20used%20@Vazkii%27s%20%22Bug%20Reporting%20101%22%20to%20report%20an%20issue%20in%20a%20mod!%20Check%20it%20out:%20http://vazkii.us/br101">Tweet about this!</a>
</div>
</div>
<div id="inst-footer">
<div id="btn-back" class="btn">Back</div> <div id="btn-next" class="btn">Next</div>
</div>
</div>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"></script>
<script src="br101.js"></script>
</body>
</html>