Difficulty Converting Old Picom Configuration to New Syntax Without Mixing Configurations

[raven2cz]

I use picom animations and also the new management of rules through the new syntax { }, see the discussion in animation thread. However, now picom tells me that it's not good to mix old and new configurations. I would like to rewrite the old syntax to the new one, but it might not be entirely simple, right? Here it shows me all these warnings.

https://github.com/raven2cz/dotfiles/blob/main/.config/picom/picom.conf

How can I reasonably convert it to the new configuration and will it be possible? Is there any guide?

[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "inactive-opacity" is set along with "rules". "rules" will take precedence, and "inactive-opacity" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "active-opacity" is set along with "rules". "rules" will take precedence, and "active-opacity" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "inactive-opacity-override" is set along with "rules". "rules" will take precedence, and "inactive-opacity-override" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "inactive-dim" is set along with "rules". "rules" will take precedence, and "inactive-dim" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "mark-wmwin-focused" is set along with "rules". "rules" will take precedence, and "mark-wmwin-focused" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "mark-ovredir-focused" is set along with "rules". "rules" will take precedence, and "mark-ovredir-focused" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "shadow-ignore-shaped" is set along with "rules". "rules" will take precedence, and "shadow-ignore-shaped" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "fade-exclude" is set along with "rules". "rules" will take precedence, and "fade-exclude" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "blur-background-exclude" is set along with "rules". "rules" will take precedence, and "blur-background-exclude" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "opacity-rule" is set along with "rules". "rules" will take precedence, and "opacity-rule" will have no effect.
[ 10/20/2024 09:24:10.954 log_warn_both_style_of_rules WARN ] Option "wintypes" is set along with "rules". "rules" will take precedence, and "wintypes" will have no effect.
[ 10/20/2024 09:24:10.954 report_deprecated_option WARN ] Option "glx-no-stencil" is deprecated, please remove it from your config file and/or command line options.
[ 10/20/2024 09:24:10.954 report_deprecated_option WARN ] Option "glx-no-rebind-pixmap" is deprecated, please remove it from your config file and/or command line options.
[ 10/20/2024 09:24:10.954 sanitize_options WARN ] You have set both "rules", as well as old-style rule options in your configuration. The old-style rule options will have no effect. It is recommended that you remove the old-style rule options, and use only "rules" for all your window rules. If you do genuinely need to use the old-style rule options, you must not set "rules".
[ 10/20/2024 09:38:43.567 sgi_video_sync_scheduler_callback WARN ] Duplicate vblank event found with msc 56417. Possible NVIDIA bug? Number of duplicates so far: 0

[Vortex-Vortex]

I found this guide very useful, it shows how to do everything regarding new rules and old rule migration:
https://picom.app/#_window_rules

Also, for reference here is my picom.conf file if you want to see a example:
https://github.com/Vortex-Vortex/Vortex-Awesome/blob/main/configuration/picom.conf

[Monsterovich]

#1327