Bug Report Guideline.

[dree74]

I see so many new users simply saying "I JUST INSTALLED YOUR MOD AND MY GAME CRASH1!1!!!"

 

This is not helpful nor clear at all (honestly, when someone does this, I really don't want to help).

If you are trying to get help from modders, be serious with your bug report.

 

I will write down steps that I expect from mod users.

 

Bug Report Format:

 

- Describe the bug. Do you get glitched out of map? Do you get constant CTD at certain location or certain event? Something disappeared or look awkward? red triangle with exclamation mark? write it down.

 

- What methods did you use to confirm that the bug was coming from this particular mod?

(I believe this is something that most of modders want from mod users. I've seen more than dozens of people accused my mods for making bugs, but later on they come back tell me that other mods were causing the conflict.)

 

If your answer is, "I disabled this mod, and crash disappears." This does point it out, but it is still vague.

 

Let me show you how you can help the modder to understand what steps you went through.

(In this example, let's call this mod "X": X is a simple plug-in that has mesh/texture/sound and .esp file without dependency to other .esm files).

 

I. Load only FalloutNV.esm and X.esp. (If mod contained .esm file, start a new game with FalloutNV.esm and X.esm).

- Does the problem persist? If yes, load FalloutNV.esm only and load the save file.

- Does the problem still persist? If yes, this bug is coming from FalloutNV.esm.

 

II. Learn to use tools like FNVEdit.

- FNVEdit can detect errors (some are harmless, but it still show up.)

- Conflict detection is the best part. If some parts of your game are awkwardly overriden, use FNVEdit-> Apply filter to see which mod override the data.

 

- It will show you which mods are sharing a same data. Below is a screenshot after applying the filter.

http://img811.imageshack.us/img811/7904/fnveditfilter.png

 

When you nail down the problem with FNVEdit, make a screenshot and show it to the modder.

 

III. Report everything. This is mandatory.

- What official version of Fallout New Vegas are you using?

- Are you using NVSE? If so, what version are you using?

- What version of this mod X are you using?

- Of above 3, did you try using the latest version?

 

- How did you install this mod?

- Did you install as described from Mod Description Page or ReadMe File?

- Did you merge multiple mods including this mod? or created different format of this mod on your own?

 

- How is your hardware? If the bug is graphic related, post your graphic card and other issues related to it.

 

and mostly importantly, post your load order.

 

Here is the fact: even if you do all those above, the modder still won't be able to help, but with information you provided, the modder may be able to help other users in the future based on what you provided.

This is least you can do to contribute toward to this mod and the entire community.

 

If you are saying "That will take 15-20 minutes, and I don't want to waste my time!".

Many modders spend weeks and even months to provide mods to the community. If spending 15-20 minutes to create a bug report is too much for you, I believe you don't deserve to be helped.

Edited July 30, 2011 by dree74

[quicksilverva]

amen reverend

 

 

or the thumb it down marking "user could not get file to work", and dont post anything else.......ever