Comments - d1sasterpiece

Added support for this in latest version

Yep so what you see in that screenshot is the expected *default* behavior. I see the same when I haven't renamed the script file.

Just to confirm you should *only* have [03 MagRedux Compatibility] from the zip installed as well. Installing more than one would cause conflicts.

If you were to now rename the script file from "/gamedata/scripts/d1sp_keep_ammo_highlighted_mcm.script" to "/gamedata/scripts/zzzzzzzzzz_d1sp_keep_ammo_highlighted_mcm.script" it should highlight mags in your loadout as well. This is what I've tested on my end and it works. (Note that this will work without having mcm installed)

If this still doesn't work I'm sorry but I don't see what else I can suggest.

Hi,

I've done some testing and those items appear highlighted for a clean install of this addon with only mags-redux installed.

To confirm I'm testing the right thing, by pouches you mean right clicking the magazine and selecting "add to loadout" right?. I don't use mags-redux so I'm not aware of the various features it has.

Could you try a fresh install of each with no script modifications (except the zzzzzzzzz_ renaming if you want) to see if it works for you?

Latest version should highlight the other mags as well now.

For making the highlights here take precedence over other addons/mods this is only doable by changing the load order of scripts. You could try renaming the main script of this mod to start with zzzzzzzzzz_ so it gets pushed to the end of the load list. The script for this mod would need to load after mags redux.

I've added the ability for mags to be highlighted now. Hopefully it does what you need.

Let me know if you have any issues.

It might be possible but I haven't used any mag mods so I can't say for sure.

Please could you post a link to the mod you want me to add compatibility with so I can have a look.

Good to hear its working

And thanks for the localization files - I've added them to the latest release

Added to latest release

Hi again

Could you try the latest version of this addon and see if it fixes your issue.

I was able to replicate your issue by installing both of those addons + this one. While this addon doesn't actually change anything around armour/guns for some reason using a certain internal function caused that crash. No idea why.

No problem - happy to help.

Hi

I can't see any reference to this addon in those logs. Looking at the source code from that github link you provided, it appears the issue you are seeing is caused by the 'Outfit Repair Overhaul' addon when it tries to call "to_infobox", passing a potentially <nil> value into 'pairs'

To confirm which addon is causing this issue you could disable all addons other than this one (if you are using MO2) and then try to replicate that issue by hovering over the Proto-Exo.

Just to be safe I've added a <nil> check in a similar line within this mod when it calls to get compatible repair kits.

Thanks for this - added to the latest release

I think there might be some conflict here caused by installing both versions of the addon.

In the addon zip file there are two root folders

- 01 Basic
Contains 'd1sp_track_compatible_items.script'
This is used if you don't want to configure highlight colours

- 02 Basic with MCM support
Contains 'd1sp_track_compatible_items_mcm.script'
This is used if you want to use MCM for configuration

Each root folder above then also contains the localization files

'01 Basic' and '02 Basic with MCM support' are mutually exclusive (install only one)

The error in your log file is being raised in the script 'd1sp_track_compatible_items.script' while the notepad++ diff you provided is of d1sp_track_compatible_items_mcm.script.

Could you please look in your anomaly installs gamedata/scripts folder and confirm that you only have **one** of the following

- d1sp_track_compatible_items.script
- d1sp_track_compatible_items_mcm.script

I'm assuming you want to use MCM to configure the highlight colours so you'll want to be using '02 Basic with MCM support' which would be the script 'd1sp_track_compatible_items_mcm.script'

If you are using mod organizer 2, you could open the 'data' tab in the launcher, and navigate to gamedata/scripts to confirm you only have one of these scripts.

Again if using MO2, it may also be useful, if you haven't already, to disable all other addons except this one, and see if the crash still occurs.

Hi, I've been unable to replicate this crash on my end.

To help me diagnose this could you do the following:

Firstly, could you try a fresh install of the addon. If using MO2 just right click and remove it. If you manually installed it, could you delete any files under your anomaly installs /gamedata/scripts folder that contain the words 'd1sp_track_compatible'

Once uninstalled, try installing version 0.0.5 again.

If you still get this crash could you provide me the following:

(1) The name of the item causing the crash
(2) The last 10-15 lines of your games log file. This is located under /{your anomaly install folder}/appdata/logs and will be called 'xray_{windows username}.log'
(3) The lines in your script file causing the issue. Open '/gamedata/scripts/d1sp_track_compatible_items_mcm.script' (or d1sp_track_compatible_items.script if using the non-configurable version) and either screenshot or copy the code around line 186.

Hi, and thanks for providing this.

I've include those localization strings in the latest release.

I've also added localization support for the right-click menu item text, and added some (crude) google translate localization for them.

Hi again

I've had a look into this (and written a detailed explanation of why this happens below), but my tldr answer is that I probably can't fix this.

If anyone more knowledgeable on anomaly modding reads this and knows a solution, please correct me.

For an explanation, the issue is that some guns in anomaly have grenade launchers configured in their ltx definitions, but then disable them with grenade_launcher_status = 0. I don't know why this is the case. The VEPR 12 falls into this category. The same applies to silencers and scopes. For some guns this makes sense as you need to buy the under-barrel attachment as an upgrade (but the VEPR 12 doesn't have this)

Normally in anomaly when you hover over an item, it knows to highlight attachments because it calls the function weapon_grenadelauncher_status() on the object instance in your inventory, which checks both the ltx definitions *and* whether the gun instance has an attachment upgrade brought.

The issue is that this mod tracks on the name rather than an object instance. This is what allows the trackers to persist without the original item. I cannot call this function without an object instance.

If I change the addon to require grenade_launcher_status = 2 in the ltx definition (meaning it supports grenade launchers) it will then break highlighting possible attachments for weapons like the AKMN (with or without the under-barrel upgrade brought) as the default ltx definition has the status as disabled (0).

I think the better solution is to leave the logic as-is so that everything is highlighted as expected, with some invalid highlights sometimes, as opposed to some guns not working with the tracker at all.

Thanks for this.

I've fixed this issue in the latest release.

Yep, you need to manually select an item to be tracked using its right-click menu.

The lower index slot takes precedence.

So the ammo would be highlighted for the secondary over main, and pistol over secondary or main.

I guess it would be preferable for the slots to have the same colour if they shared ammo type. Might have a look at it when I have time.

edit: latest version colours slots the same if they share ammo