@ponapalt The github version of taromati2 will check if the ghost exists in the installedghostlist or installedsakuralist on OnInstallRefuse, and because the ssp does not provide a proper event, so installedsakuralist is implemented by taromati2 traverses all ghost installation directories and reads the descript.txt of all the ghosts under them. Today I noticed that some of the sakura names were garbled (being read in the wrong charset because there was no charset in the descript.txt) and although I fixed this at https://github.com/Taromati2/ghost/commit/f5c815256a78cb883aa2b0f4600df2cad1f1bce7 , I was wondering if it would be possible to get ssp to provide a list of sakura names to avoid ghost implementing descript traversal by it self?
@ponapalt Looks good for me, please add installedkerolist along with it if you can Given that a yaya-based ghost might build installedsakuralist and installedkerolist when installingghostname, I think we should probably add a separate event before the installedghostname event to tell ghost not to handle these things on its own.