09-27-2023, 10:23 AM
Currently, using a custom AI is a very tedious task, it takes around 7-8 clicks to load a custom AI. The irony is that with a previous version of Ludii, it was shorter.
I propose to add an alternative option to "From Jar" when choosing the AI: "Last AI From Jar (AI Name that will be loaded)". The idea would be that this choice automatically loads the last AI loaded by "From Jar" so as not to need to respecify the path to the associated .jar file.
It would also be necessary to decouple the two AIs, because changing one of the AIs requires reloading the other AI (i.e. currently respecifying the path of the .jar file, which still requires additional clicks but also loading time of the AI which with a personalized AI takes a significant amount of time even though there is no point in reloading it.
Note that in older Ludii versions (for example 1.1.15), the choice of the two AIs was decoupled, with these olds versions, we could change AI much more easily and quickly: it was better before!
I propose to add an alternative option to "From Jar" when choosing the AI: "Last AI From Jar (AI Name that will be loaded)". The idea would be that this choice automatically loads the last AI loaded by "From Jar" so as not to need to respecify the path to the associated .jar file.
It would also be necessary to decouple the two AIs, because changing one of the AIs requires reloading the other AI (i.e. currently respecifying the path of the .jar file, which still requires additional clicks but also loading time of the AI which with a personalized AI takes a significant amount of time even though there is no point in reloading it.
Note that in older Ludii versions (for example 1.1.15), the choice of the two AIs was decoupled, with these olds versions, we could change AI much more easily and quickly: it was better before!