[Feature Request] - Alternative Dependency Management

[ondrovic]

Is your feature request related to a problem? Please describe. Trying to manage dependencies is a bit challenging when you have a bunch of mods installed, because of the drag and drop interface, which doesn't always seem to scroll properly

Describe the solution you'd like I would like to manage dependencies from the mod flyout editor (when you double click a mod)

A drop down (or multi select drop down that allow you to select the mods), and the mod type.

Describe alternatives you've considered Currently the only way is to use the drag and drop method

Additional context

[IDCs]

As I mentioned in #16360

I agree that the deploy order dependency system is less than ideal, but I'm not sure if a multi select drop down in the mods panel is the way to go; this feels like it should be its own component. I'll have a think and see what I can come up with.

May steal designs from NMA 😆

[ondrovic]

As I mentioned in #16360

I agree that the deploy order dependency system is less than ideal, but I'm not sure if a multi select drop down in the mods panel is the way to go; this feels like it should be its own component. I'll have a think and see what I can come up with.

May steal designs from NMA 😆

Sounds good, I wrote a go lang scraper that will get and download the mod dependencies to an json file, the goal is to get all the data into a database instead, let me know if this would help

[IDCs]

Hey @ondrovic, given that a scraper can potentially break upon site updates, we can't include it in the core app; but nothing should stop us from running that in a non-bundled extension.

If you share your script, I can have a look at the type of information we can pull and potentially modify my dependency injector extension to organize the deploy order based on what the script gets back.

[ondrovic]

Hey @ondrovic, given that a scraper can potentially break upon site updates, we can't include it in the core app; but nothing should stop us from running that in a non-bundled extension.

If you share your script, I can have a look at the type of information we can pull and potentially modify my dependency injector extension to organize the deploy order based on what the script gets back.

Sure let me get in a repo later today and I will link it here, in the meantime here are a couple of json files I managed so you can see the contents of what I am grabbing.

cyberpunk2077_scraped_json_mods.zip

A couple of notes:

1. it does require the modder uses the requirements properly, it doesn't work properly if they added them to them main description 🤣

2. For adult content you need be logged in and currently I am doing a hacky way by using cookie values 🤣 😢 , still early in the dev, I work on when I have time.

[ondrovic]

@IDCs I haven't forgot about you 😄 I just got busy with some stuff, I also need to clean up the code a bit but will hopefully have it up in the next day or so

[ondrovic]

@IDCs sorry I ended up re-writing most of it but the code is here, at least now it's a little more coherent 🙄

https://github.com/ondrovic/nexus-mods-scraper

[IDCs]

Awesome, thanks @ondrovic, will let you know once I get a chance to look at the code and see if I can merge it into the dependency extension.