it doesnt work, it says it doesnt exist.

@Quince99 my latest mod, industry forecourts, is the one where I've been strictest in applying what I've learned about avoiding conflicts.

@Quince99 I feel the same about seeing the message icon! But I was tipped off about the conflict weirdness because of how my mods conflicted with each other!

SPQR - Thank you for this information - it is going to be extremely helpful as I look to reskin more models. The info about the CON files is very useful as I was loading and reloading saves for testing and yes, it took ages!

I've got some of your mods installed so will look at those for naming convention and structuring.

Having seen there were 3 comments on this thread I dreaded that people had found new errors or conflicts with this mod!

Also for info - and very useful if you haven't noticed it yet: .con files are loaded each time you click a menu item or option. This means you can experiment with the assembly and parameters of your mod without having to reload a save.

- I'm now wondering if there's somewhere more useful I could post this. Sorry to clog up your comment stream!

In the end, I have resorted to prefixing all my code libraries with the steam mod id number (since we can be sure that's unique) and creating a unique prefix for all files relating to the mod itself unless I'm certain the paths will protect it from conflicts, which it does in very few cases. This means I don't even have to try to discover why some paths cause conflicts and others don't.

@Quince99 I'm glad you resolved the conflict issues. If it's any help (to you or anyone else): different files are compiled and loaded by the game engine at different times. Those that are loaded when the game is first loaded are the least likely to conflict but this (as I think you've discovered) are path dependent. This is why it's possible to have a ton of mod.lua without a problem. .mdl and images (in mods, at least) are loaded when you load a save or start a new game. These are affected by load order and my extensive though not exhaustive testing suggests that even when the paths are obscure and explicit (e.g. you use a require statement with a relative path, rather than just a file name). Since the image in the textures/ui path are used to create menu items, they have to have unique names.

i mean quince not steve

brilliant steve

sorry for overreaction on the other one

Details are on the original mod's page in the link above; these are unchanged.

No Stats?