Old script won't load

I have been using this script for a long time. Now with the latest beta (I am currently using Opus 13.10.4 Build 9060 ) it doesn't even load anymore.
Does anyone know why? Maybe something has changed inadvertently in the latest beta?
Thanks

Loads OK into 13.10.4 for me:

image

I tried reinstalling it and nothing...

It looks like you've disabled it, try clicking its checkbox to turn it back on aghain.

The one with the red writing (the second from the top) is disabled because it doesn't let me activate it

I get

Cmd.TabDedupe.js:  Script does not implement any known events and was unloaded

and

1 Like

Exactly! It happens the same to me..

Working OK for me on a second machine with 13.10.4, this time Windows 10 (previous was Windows 11, although may not be completely up to date with OS updates).

Which antivirus are you both using? That's something that might change by itself, and could theoretically modify the script file it's extracted to the temp folder, which could in turn explain why it has no methods (maybe no code at all) on your systems but not mine, without the script itself changing.

I installed all Opus versions back to 13.5 (when the script was published) and always got the error message. I guess that points to a Windows problem. I run Win11 24H2, with just the built-in antivirus.

The script runs fine with Win10 and Opus 13.10.4 :slight_smile:


Crash ID 380, 382 :wink:

2 Likes

I have Win11 24H2 and as antivirus I have kaspersky
I checked the files in the installation directory and they have the same hash as those in the archive. So the files should not be corrupted

Moving the three inc*.js files into the main script will make it work.

Same here, Win11 24H2, with just the built-in antivirus.
Scripts with multiples includes won't work.

This does seem to have been broken by 24H2. The script parser seems to stop adding new functions once a duplicate name has been encountered. With two or more include files there are duplicate OnInitIncludeFile functions being parsed and this is what seems to make it stop working.

1 Like

Actually no, it's not the duplicate names - Microsoft simply seem to have broken the ability of the parser for any given script instance to parse more than two separate scripts.

That's actually better as it makes it easier to come up with a workaround - instead of parsing the includes and the main script separately, we should just need to join them altogether in one big string first.

2 Likes