Fastest way of solving Jigidi puzzles

< Feedback on Automagic Jigidi Solver

change in line 195 and 207 in the code the version number to v3.1806 and solve and it works again

is there a possibility to avoid these changes in the future?

is there a possibility to avoid these changes in the future?

Geeft nog steeds dezelfde fout melding

for me the change of version number to v3.1806 worked for just an hour, but now the solver is down again

I am working on this. Third update this week, and the last one shows how amateur programmers they have. They are testing in production!! First they update the version number to v3.1806 but after that they decide to obfuscate the release script without updating the version number.

They've released v3.1809 now. The simple fix to the script (changing the version numbers) doesn't solve it.

Automagic Jigidi Solver disabled!

Jigidi has updated to v3.1809

but solver supports v3.1806

Try updating the userscript and then try again.

Jigidi has updated to v3.1809

but solver supports v3.1806

Try updating the userscript and then try again.

Problem solved, update or reinstall userscript to version 1.5.7

And now jigidi has updated to v3.1811 and solver supports up to v3.1809

Fixed, again...

Thanks again jtojanen! Let´s hope the new trick helps!

Seems Jigidi updated again to version 3.1813 and solver supports up to v3.1811.

Appreciate all the work that goes in to updating the script all these times!

Appreciate all the work that goes in to updating the script all these times!

Thanks! Update to latest version 1.5.9 that support Jigidi v3.1813.

Automagic Jigidi Solver disabled!

Jigidi has updated to v3.1818

but solver supports v3.1813

Try updating the userscript and then try again.

Jigidi has updated to v3.1818

but solver supports v3.1813

Try updating the userscript and then try again.

Change v3.1813 on line 19 into v3.1818 and it works again.

Forgot to post reply, but I have updated the script.

Jigidi has updated to v3.1806

but solver supports v3.1792

Try updating the userscript and then try again.