Closed just-Addict closed 6 years ago
Can't reproduce the error on stable nor canary. Judging by the traceback, something is with the configuration JSON in plugins folder, try deleting or moving it or look what's wrong at position 119, if you could upload it here for me to take a look at that would be great too.
I checked the json file for the collection too, but the thing is, none of the entries even reach position 119, and this error only shows when I move the plugin into the folder, even without a configuration file present -----Original Message----- From: "awaken1ng" [notifications@github.com] Date: 26/11/2017 13:49 To: "awaken1ng/bd-linestickers" bd-linestickers@noreply.github.com CC: "just-Addict" crajware@excite.com, "Author" author@noreply.github.com Subject: Re: [awaken1ng/bd-linestickers] Recent Discord update broke your plugin. (#14)
Can't reproduce the error on stable nor canary. Judging by the traceback, something is with the configuration JSON in plugins folder, try deleting or moving it or look what's wrong at position 119, if you could upload it here for me to take a look at that would be great too.— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
I did notice one thing... none of the entries is getting a closing " after the title. -----Original Message----- From: "awaken1ng" [notifications@github.com] Date: 26/11/2017 13:49 To: "awaken1ng/bd-linestickers" bd-linestickers@noreply.github.com CC: "just-Addict" crajware@excite.com, "Author" author@noreply.github.com Subject: Re: [awaken1ng/bd-linestickers] Recent Discord update broke your plugin. (#14)
Can't reproduce the error on stable nor canary. Judging by the traceback, something is with the configuration JSON in plugins folder, try deleting or moving it or look what's wrong at position 119, if you could upload it here for me to take a look at that would be great too.— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
After some digging I isolated this crash to your plugin.