I agree, FOSSIL is an excellent project, MV has accumulated TONS of useful plugins and it would be a shame to lose them just because the RM core scripts were refactored and updated.
Also, I think it is too early to judge this project dead, the last meaningful commit to the project was 3 month ago.
If it is indeed dead, the community can indeed pick this up, FOSSIL license permits it (https://tldrlegal.com/license/creative-commons-attribution-4.0-international-(cc-by-4))
I for one would happily participate in such an effort if it takes place, though unfortunately I am too much of a noob in RM core scripts to even think of leading such effort.
That said, guys, do you think it is possible to get from Kadokawa an official list of changes (refactorings) between RMMV and RMMZ core scripts? This would definitely make life easier for whoever maintains FOSSIL project
Indeed. If I have time I will try looking at least on *some* issues the project has, for example I think I traced the exact reason why Yanfly Core fails with FOSSIL (or at least one of the reasons)Well, 4 month without any news it's a bit worrying xD There are only problem posts and, although Restart said that this started as an open project, no one skilled is really participating in its improvement. It's a shame....
Indeed. If I have time I will try looking at least on *some* issues the project has, for example I think I traced the exact reason why Yanfly Core fails with FOSSIL (or at least one of the reasons)
But so far I didn't discover what would be the best way to fix this. I guess the best way in this case would be to compare relevant core script areas beween MV and MZ, because there is zero documentation I could find about those areas of code
Did you follow the advice in the original post?Has anyone had success with deploying their game to mobile/web well using the Fossil plugin? For whatever reason my game does not work when I deploy it for mobile/web when using the fossil plugin.
Thanks in advance!
Mobile and Web Deployment Note
FOSSIL creates a 'FOSSILindex.html' file at runtime, and switches to use it instead of the original 'index.html'. This works seamlessly in both playtest and deploy on my computer. However, it is possible this might not be possible in web or mobile environments (I can't test them). However, if you just rename an existing FOSSILindex.html to index.html, you will bypass the html creation step, and proceed with the rest of the plugin. (Basically I need to replace 'main.js' in index.html with 'FOSSIL.js' so I can control when plugins are added).
if it works in MV but not in MZ, then it may be that the plugin is doing something that FOSSIL doesn't currently 'translate' to MZ - or it could just be a missing image. Without knowing what plugin you mean and what the error message/console error output is, I'm not sure beyond that.Ummm... I heard that this one allows several MV plugins to work on MZ, so I decided to give it a try by bringing some really nice plugins from MV to MZ. I already have a really nice plugin that allows Undertale-styled bullet hell to occur inside battles, but when I slide the plugin into MZ, below the FOSSIL layer, but nothing happens. Battles don't start and instead it throws an error. Is that the plugin's fault, or is it RMMZ's code base's fault?