Instead of hardcoding the path, I added a small function within the before_download to iterate through the NFBR.a6G.Initializer.* keys to detect which one is the correct one. So that if the JS ever change again, it should not have any problem choosing the correct (encrypted? compiled?) method function.
Instead of hardcoding the path, I added a small function within the before_download to iterate through the
NFBR.a6G.Initializer.*
keys to detect which one is the correct one. So that if the JS ever change again, it should not have any problem choosing the correct (encrypted? compiled?) method function.Tested on BW JP![image](https://user-images.githubusercontent.com/11814787/228018866-03d74272-bb74-47b4-9382-e26f9cbce4b0.png)