Troubleshooting busted mods

[ahondara]

I already have another thread going on a specific mod I am having trouble with, but would like to know in general: how do we go about finding out what areas are "broken" in a problem mod so we can go about fixing them? We get error messages, but I have no idea how to locate those things and do anything about it.

 

[gregathit]

This is the modders resources thread and not a troubleshooting one. Please stick to posting technical problems to the technical support thread so as not to clutter things up

[Guest Donkey]

If you are fixing your own mod it will be far easier then fixing someone elses, you build the structutre so it is easier for you to locate things.

 

Fixing someone else busted mod, is totally different. You will have to look around and familair how the mod works. Translators have this edge when translating mods, because it forces them to dive into the mod and start translating parts.

 

meaning when they finish they have a good idea how the mod works. scripts are totally different.

 

Usually an error message gives it away. like if it is in a script it will name the script in the crashlog. So you have a starting point on where to look for the error.

[ahondara]

Thanks. There are lots of error messages, even before I start working on something. The trick is how to find the things that the error message is pointing me to. I have no idea where "texture 247d78f" is found for example.

 

I'll do my best to keep my posts in the correct area from now on too.

[Guest Loogie]

This thread is fine here - it's borderline, but you're mostly asking about a modding mechanic than something like "post load order plz"

[ahondara]

You lost me there Loogie. Post load order?

[gregathit]

I think what he is getting at is if you are asking about general mechanics (programs, plugins or methods) then this area is fine. If you are trying to resolve a specific problem and wanting to post your load order to get help then not so much.

[Guest Loogie]

What Greg said.