Title. Currently this isn't possible because there's a couple problems that need to be addressed:
1) Because the generation params are currently dumped into a single string, a parser would need to be written using the on_infotext_pasted callback to retrieve the values. These are intended to be stored under individual keys.
2) Furthermore, because the generation params are added under a single key with a version number that is variable (Vec. CC [{VERSION}]), it would prevent the ability to read params from infotext from a different version of the extension. Ideally this would just be stored under a separate generation params key.
Title. Currently this isn't possible because there's a couple problems that need to be addressed:
1) Because the generation params are currently dumped into a single string, a parser would need to be written using the
on_infotext_pastedcallback to retrieve the values. These are intended to be stored under individual keys. 2) Furthermore, because the generation params are added under a single key with a version number that is variable (Vec. CC [{VERSION}]), it would prevent the ability to read params from infotext from a different version of the extension. Ideally this would just be stored under a separate generation params key.