Comments - LunarTM

New version of LMDL is available. The WPO files are now optional, so there shouldn't be any issues with Larger Parts Condition Text when using LMDL without WPO.

Alright, I figured it out. Larger Parts Condition Text has a file named "zzz_parts_in_tooltip_Larger_text.script" under gamedata/scripts. On line 13, the script checks to see if WPO is installed by looking for a specific file, "zzzz_arti_jamming_repairs.script". Unfortunately, that's the same script I have in my mod for the Full version in order for the Gauss gun parts to work with WPO. What I imagine is happening is that the script is calling on the arti_jamming_repairs script, which in itself calls upon arti_jamming which then calls upon a_wpo_parts, and because none of those other items are there, the call for arti_jamming_repairs fails and causes the crash.

So, there's a few ways we can fix this. The easiest would be to just play with WPO enabled, since then the script will have access to all the other scripts it needs to run.

The second easiest would be to change the file it's trying to verify. To do this, open zzz_parts_in_tooltip_Larger_text.script and change line 13 from:

if not zzzz_arti_jamming_repairs then return "" end

to this:

if not arti_jamming then return "" end

That way it'll look for a file that's only in WPO and not in LMDL.

The last way would be for me to break down the LMDL Full version to separate the WPO items and make it an optional patch. This one would probably be the best option overall, but for the time being so you can keep playing, I'd recommend changing the file in the larger text script. Then, once I get the new version of LMDL sorted out, you can just reinstall the larger parts mod to restore it back to how it is by default.

Weird. I checked out that BaS version of Parts in Tooltip you linked, and the code isn't very different, but looking at what it was claiming to fix, I didn't really see any reason to have a BaS patch. It said it was for the modified weapons, but I checked all the weapons and their modded versions and I didn't see anything wrong. Maybe try playing it with the original mod? The BaS patch was done by someone else, so who knows? I haven't had any issues on my end with the original version with both lmdl full and wpo. Moddb.com
I have my load order for these laid out as WPO, LMDL, Parts in Tooltip

I'm having trouble recreating the issue, as I'm not having a problem on my end. Could be because you're playing in Russian, I'm not sure. Do you know what you moused over that made you crash?

I've looked at the code and done my own testing, and nothing seems too out of the ordinary, and I'm able to get it to work on my end with the custom parts. It could have something to do with your game being in Russian, but I'm not sure.

I'll upload the patched version with the correct encoding on the RUS files and maybe that indirectly fixes it? If not, let me know with some details about what you were doing right before the crash and I'll look into it some more.

Ah, wasn't aware of the encoding problem. I'll get that patched up.

Might have to do with the custom parts. I'll look into adding compatibility for it.

Sounds like you might have another mod that's overwriting BaS's parts.ltx file. Not sure if having another parts.ltx after my mod will affect it or not, but i know that mine doesn't directly overwrite parts.ltx and uses DLTX to inject my changes into the file regardless of what's on the file.

In MO2, use the file browser on the side to go through your game files (using my memory since I'm at work rn) config/item/settings and see which mod name is listed beside parts.ltx; that'll tell you who won the conflict, if any. You can open the file from there to peek at it and see if BaS's parts are listed there or not; they have their own section under the main list of weapons.

Which weapons from BaS are you having issue with? Also, which version of BaS are you running?

Ahh, that makes sense. I'm glad he was able to help you! I'll push out a patch for it today. Thank you and mrdemonized for your help!

It's funny though, when I was making the addon, I wasn't sure if it was worth my time adding the Russian version, I don't even know it myself, but I'm glad someone is able to make use of it.

I used Deep L for the translation of everything to Russian, so if you have any recommendations on fixing any of the Russian text, please let me know! It would be most appreciated.

It should work without WPO.

The only things that really interact with that would be the DXML files. Best I can say is update WPO and Modded EXEs.
Not really sure if there's much I can do in regards to my own addon. I'm running it on 1.5.2 with the newest versions of WPO and Modded EXEs with no problem on my end.

That's from the Modded EXEs mod. Could be out of date. It looks like you're running Anomaly 1.5.1.2 still, if your filepath is to be trusted. Current version is 1.5.2, which is what my mod is built around. Make sure your modded exes are updated (new version came out yesterday) and consider upgrading to Anomaly 1.5.2

For real? I'm still out of the loop with all the modding resources. They got something for .script Lua files too?

The 2.0 version is a lot less hard-coded, relying on using DLTX to supplement the .ltx files instead of the old way of completely overwriting them. Basically, if BaS releases a new update with a new weapon and parts, or you add another addon that has its own weapon/outfit with parts (Trader Overhaul outfits for example), my DLTX files won't overwrite them so they all work together.

Would be nice if I could do the same with .script and .xml files too, but that's just a pipe dream.

Try the new version :)

New update is out. There shouldn't be any more weird compatibility problems for a good while now, and the addon can be used with or without BaS and/or WPO now.

Unironically thank you for this post. It really helped me get WPO compatible again when I rebuild the addon, and saved me a ton of time from pouring through more Lua and XML! ^^

Hi, sorry for everything being out of date. I'll look into getting this mod updated sometime this November.

I'm aware of the issues with it not being compatible with the newer versions of WPO, and I had a fix halfway completed before I took my leave. I also see some concerns regarding the gauss rifle and using the default version instead of the BaS version. I'll see what I can do to accommodate those who don't use BaS as well.

Thank you all for your feedback with the issues my mod has. It does help me pinpoint areas that I need to fix.

For real. The amount of times I'd be at home camp and get a random mission fail was frustrating.

Yeah, MO2 is required due to the fomod installer. Doing it manually is honestly nowhere near as safe and easy as using MO2; you should give it a try.

Thanks! I'll give it a look over and see if there's anything I need to update for my own addon.

Version 1.6.0 is out now! There's two new parts, and snipers finally get some love for their barrels. I've also swapped the Gauss Gun's default parts to the best calibre barrel, as I felt like using the basic 7.62mm sniper barrel was too cheap for a gun of its power. The Icon Override plugin should also make any new parts compatible with any mod since it no longer uses the ui_icon_equipment.dds texture file.

Personally, I'd love the ability to make it so that whenever you rechamber a sniper from one calibre to another, the barrel part for the gun would also change to match the new calibre, but I don't know if that would even be possible on a technical level. Maybe it is possible and I just don't have the knowledge to pull it off yet.

Also, please let me know if there are any missing items or bugs as a result of my addon. I'll do my best to keep things all patched up and good to go.

P.S. I removed the 1.5.1 bit at the end of the file name. It was a little confusing to look at, and it seemed kinda unnecessary since there are no more planned version updates for the base mod.

Ayo, this is fantastic! Got myself Raven ascendant's Icon Override, and that thing's such a fantastic tool. I do have a few fixes and a couple new parts to add for the next update, but this should make things so much smoother, and it should be universally compatible with any mods that use a custom ui_icon_equipment.dds file. Thanks for the tip!

I'll look into it. I thought it had to be in the ui_icon_equipment.dds file, but if I can just make my own version, that'd be grand

Looks pretty neat. I can finally truly fulfill my dreams of being a UNISG undercover agent without being merced by my comrades.

Version 1.5.0 has been released, and it's got the most amount of work put in it yet! More options for installation, a more streamlined installer, brand new weapon parts, and my most favorite part, giving the gauss guns the ability to be properly repaired! I've learned a lot along the way for this update, and I'm hoping to fix up a few more things and pretty up the installer in the future.

I actually have custom parts created for the gauss rifle, and I would've released it already, but there's a compatibility issue with WPO that causes an errorless crash when right clicking the gauss rifle. Since this doesn't happen to other guns with custom parts, I know the parts themselves aren't an issue. I imagine the script that handles the field strip function has some kind of error when trying to assess whether or not the gauss gun has parts.

ATM, I have no idea how to solve this. I don't know Lua, so I've been trying to learn as much as I can in my free time after work so that I can go through the scripts and hopefully pinpoint the issue and fix it.

This please. I love the mod, but once I reach endgame, I have to turn it off due to every pseudoguant I find crashing my game when I rocket them.

Managed to get DLTX figured out, which should greatly improve the addon's ability to mesh with other addons, unless there's something outright missing that needs to be added. Turned out to be much easier than expected thanks to the DLTXify addon.

Is this compatible with the newest version of WPO?