Scanner throws an exception in the console when attempting to detect SCP-3114
Opened this issue · 11 comments
On periodic and initial scans, this exception is thrown in the console and the plugin ceases to function as intended (I'm aware the update has only just dropped, just creating this issue to let you know).
In addition, the initial SCP scan now fails, printing {LIST} has breached containment in the chat.
Try the latest build in the Actions tab
Try the latest build in the Actions tab
Tried this the other day when I saw a new build had been generated. Didn't seem to work, but I'll reinstall the plugin and see if I missed something.
Can confirm it still doesn't work when I use the artifact generated from the new build. The same exception is still thrown in console and the initial SCP announcement is bugged:
For me is working but I had to manually edit the translations file and disable that I only have the scanner
For me is working but I had to manually edit the translations file and disable that I only have the scanner
Do you have a working .dll I could use in that case? Or instructions on how to edit the translation file and compile the .dll myself? I'd appreciate it
I don't know how to compile but later I will give you my translation and the dll
Didn't actually realise the translation file existed as a config outside of the packaged .dll. I've added 3114 as a translation which has fixed the periodic scan sending an exception in the console, but I still get the issue of {LIST} has breached containment at the start of every round. Have you managed to find a solution for this?
I don't use that function I recommend you to disable it El vie, 3 nov 2023 18:38, Clark @.> escribió:
…
I don't know how to compile but later I will give you my translation and the dll Didn't actually realise the translation file existed as a config outside of the packaged .dll. I've added 3114 as a translation which has fixed the periodic scan sending an exception in the console, but I still get the issue of {LIST} has breached containment at the start of every round. Have you managed to find a solution for this? — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AURIIFKQVCEVRCKHKL7ZHK3YCUTZLAVCNFSM6AAAAAA6UONEKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJSHA3DOMZQGU . You are receiving this because you commented.Message ID: @.>
That's a shame, that's the main feature I wanted out of this plugin. I'll just wait for the developer to fix it in that case.
The 3114 issue has been fixed but it doesnt scan flamingos properly
