I don't understand how to make a configuration file, such as using notepad, and how to ATTACH the .broom extension to it. The process is confusing and you could possibly make a video of the step-by-step process.
@mihaifm is there any chance you can give some pointers in how one would actually do this? It would be extremely useful with large modlists to have a way to delete all of the redundant files with vortex - similar to mo2's hiding feature.
- Edit - I suppose one could do this by specifying each texture etc to be deleted with the rule system, but that would be an extremely slow process, Mo2's approach of being able to hide files from the conflict pane is truly something I miss when making/using large modlists with vortex
What? Instead of pointing fingers, you could just report the problem in an informative way, like show the errors that you're getting or maybe describing the "5 ways" you tried to install. It could be that the plugin needs to be updated to the latest version of Vortex
Anyway, comments like these don't really encourage me to fix the issue, if there is one. The code is out there, feel free to modify it at your own will.
The configuration file part got really confusing for me. I need to hide some files in a mod to use it. The mod author only supports MO2 since it has a simple 'hide' button which vortex doesn't have, except for this so it's perfect.
I managed to install it succesfully but now I am kind of confused as to how to find a file and hide the ones I want. I specifically need it for this mod (check the second sticky note and the first few lines)
This is an amazing extension will really help clean up the fomod folders, which seem to frequently be deployed to the Data folder of my Skyrim and/or Fallout 4 games.
Though are wondering whether it is possible please for a setting to be added which allows, for it to be configured to run the operation automatically during deploy?
Also are rules able to specify actions to occur on a per file basis, if not can it please be considered for addition?
Also can folders be considered for use with the rules please as this can allow for aid in cleaning up (brooming) rements of items that aren't covered currently?
You may need to consider switching the rules format to something like xml (preferably), json or toml to give the data a structure to do this. Alternatively having something to symbolise the action in current form would work also.
By rules do you mean something like "copy file from X to Y" or "rename file" ? I certainly thought of it, it would be a great improvement. Indeed it requires a new format as you say. Unfortunately I don't have much time right now to implement it, but the code is up there on Github if anyone wants to improve on it.
By rules I mean allow the user to specify rules to match or not match against and an action to occur assigned to that specific rule, including skip file (exclude). For example something like the following:-
Also may I suggest being able to specify in configuration when these rules are ran such as the following:-
After installation (Before deployment)
During deployment
Basically have the rules file be xml (preferably), json or toml format based as either can have some kind of specification, schema or dtd file custom specified for it. Useful for validation purposes but also for colour highlighting and auto completion hinting.
Several code editors have the validation, colour highlighting and auto-completion hinting, one open source example is Visual Studio Code, or an addon for Notepad++ as well as other code editors or IDE software.
Is it possible even if you don't have much time right now to implement it should I open an issue on GitHub for it or will you like to do it? That way people who are following the GitHub repository will be able to see, then if they are interested they can get started on it.
I have created the issues in GitHub they were split up so that it is easier to discuss them on the GitHub and provide potential pull request options. Giving feedback to each issue on the GitHub repository, see the issues listed below:-
This is great on so many levels-- Can it be used to hide any file type? i.e. plugins, nifs, etc?
EDIT: Amazing! I was able to hide all of my Ghosted plugins that were causing me issues before (turns out Vortex still checks Ghosted plugins for cyclic rule errors, even though they're ghosted and shouldn't be looked at).
I can't wait to use this for all sorts of use-cases! Spectacular extension!!
16 comments
It would be extremely useful with large modlists to have a way to delete all of the redundant files with vortex - similar to mo2's hiding feature.
- Edit -
I suppose one could do this by specifying each texture etc to be deleted with the rule system, but that would be an extremely slow process, Mo2's approach of being able to hide files from the conflict pane is truly something I miss when making/using large modlists with vortex
Thanks!
Instead of pointing fingers, you could just report the problem in an informative way, like show the errors that you're getting or maybe describing the "5 ways" you tried to install. It could be that the plugin needs to be updated to the latest version of Vortex
Anyway, comments like these don't really encourage me to fix the issue, if there is one. The code is out there, feel free to modify it at your own will.
I managed to install it succesfully but now I am kind of confused as to how to find a file and hide the ones I want. I specifically need it for this mod (check the second sticky note and the first few lines)
Though are wondering whether it is possible please for a setting to be added which allows, for it to be configured to run the operation automatically during deploy?
Also are rules able to specify actions to occur on a per file basis, if not can it please be considered for addition?
Also can folders be considered for use with the rules please as this can allow for aid in cleaning up (brooming) rements of items that aren't covered currently?
You may need to consider switching the rules format to something like xml (preferably), json or toml to give the data a structure to do this. Alternatively having something to symbolise the action in current form would work also.
By rules do you mean something like "copy file from X to Y" or "rename file" ? I certainly thought of it, it would be a great improvement. Indeed it requires a new format as you say. Unfortunately I don't have much time right now to implement it, but the code is up there on Github if anyone wants to improve on it.
<broomRulesFile>
<broomrule>
<rule>Meshes\door#.nif</rule>
<action>HideFile</action>
</broomrule>
#<broomrule>
#<rule>fomod\*</rule>
#<action>DeleteFile</action>
#</broomrule>
<broomrule>
<rule>fomod</rule>
<action>DeleteFolder</action>
</broomrule>
<broomrule>
<rule>Readme.txt</rule>
<action>RenameFile</action>
<newName>&ModTitle; &ModVersion; - Readme.txt</newName>
</broomrule>
</broomRulesFile>
Also may I suggest being able to specify in configuration when these rules are ran such as the following:-
Basically have the rules file be xml (preferably), json or toml format based as either can have some kind of specification, schema or dtd file custom specified for it. Useful for validation purposes but also for colour highlighting and auto completion hinting.
Several code editors have the validation, colour highlighting and auto-completion hinting, one open source example is Visual Studio Code, or an addon for Notepad++ as well as other code editors or IDE software.
Is it possible even if you don't have much time right now to implement it should I open an issue on GitHub for it or will you like to do it? That way people who are following the GitHub repository will be able to see, then if they are interested they can get started on it.
Rules based operations for Broom · Issue #3 · mihaifm/broom (github.com)
Automated operations for actions in Broom · Issue #4 · mihaifm/broom (github.com)
EDIT: Amazing! I was able to hide all of my Ghosted plugins that were causing me issues before (turns out Vortex still checks Ghosted plugins for cyclic rule errors, even though they're ghosted and shouldn't be looked at).
I can't wait to use this for all sorts of use-cases! Spectacular extension!!
You've won my vote for the month, good sir!
Yea it should work for any file type and any game (unless the game extension does something funky).