It seems to be have been moderated. I’m not sure why as it’s almost exactly the same as the paid version, but I’ve appealed it. Will update the thread when it’s available again.
The free version is also available via Itch (under the demo link) if you’re happy manually installing it.
Ah, I didn’t scroll down entirely that page. My bad!
Hello, I have been using this plugin for a while and it seems like it’s not working right now. When I tried to generate snippet into Fusion, it was stuck in the “working on it” message. I don’t see any errors in the output and I am on version 2.4.5. Is there any way to fix it?
I’m not entirely sure what causes this bug, but there will be a different backend implementation in the v3 update, which is currently being worked on, that should fix this and be capable of logging errors.
In the meantime, could you try restarting the plugin by disabling and re-enabling it?
I have tried to use it on 2.4.2 and 2.4.5. None of it worked.
Do you think it would be possible to add Aegis to the conversion list? It’s a new UI library created by our team and for a few of our tests it beat out any other library with correlation to speed.
I’m exploring ways that would allow users to define and share their own custom generators in Codify v3. If Aegis is popular enough by time I release Codify3 (no timeframe yet), I’ll ensure to include it as an officially supported framework.
Having looked deeper into this it looks like the API requests are timing out, but for unknown reasons™ it’s only with Fusion specifically (in my case, where I was able to reproduce).
I’ll extend the timeout in the 2.4.6 update and have it log to the output if something goes wrong (there’s some other goodies coming too!).
For now, try generating with React (or another framework) and then switch to Fusion and regenerate. This seemed to work for me. Once you’ve done this once you shouldn’t need to do it again until the next Studio update.
Added support for Rojo JSON models (always implicit where possible)I’ve pushed out the v2.4.6 update which should now properly inform you if fetching the API dump is taking a long time. It will also now actually timeout after 60 seconds, giving you the opportunity to retry.
cc. @FunnyWailord25 @thenitropl
v2.4.6 includes support for Rojo JSON models. There aren’t really any configuration options in this version, but expect the ability to tweak Rojo outputs in v3.
This release features a slight visual overhaul:
Forgot to bump the version number in v2.4.7, oops!
this looks like a great product, but I realized that you’re selling it under the MIT License, you should probably change that, because your source code is public, meaning I could clone the repo and sell your plugin and you cannot do anything about it. So unless you meant it to be that way, I’d change the License, or you may not get much sales 
Hopefully this helps!
The source code on GitHub is massively outdated. The v3 update that is in the works is in a new separate private repo and will not be public.
I’m sure that you’re fine with it being used, though I’d maybe create a new Liscense.md and edit the fine print a bit to only include use and distribution, and not sale, because really someone could just sell it even if it was outdated, or they could just build on top of it and create a product using your code and then sell it.
But if that’s fine by you that’s alright, I was just making sure you were aware, as someone whose been programming for about 5 years now I’ve had plenty of run ins where people disrespect my code or fraudulently use it, so I just like to make people aware. Have a great day!
HI @cxmeels, i am attempted to purchase Codify v2 but as your last comments indicate, you are about to release v3?
Do old user from v2 have free upgrade to plugin v3?
v3 will be a free update to the existing plugin.
It’s still a work in progress, but aims to improve the quality and performance of the plugin overall.
I had planned on stopping updates to v2, but there were some issues that were affecting multiple users that warranted further updates. I am unlikely to add any additional features beyond patches and bug fixes in the current version, however.
Some feedback, since you use AWS for fetching API dump, i already had a few times i couldn’t reach the API dump, leaving me stranded. If that fails you should have a fallback like storing the returned json in the plugin rblx itself in a module or something. although the plugin stored version will not be guaranteed up to date, it will likely will contain almost all property data that will be needed at any given time, preventing us from getting stranded.
I considered this but was worried it might bloat out the file size a lot?
Remember that you would then have the static dump and the cached fetched dump on your system if the request succeeded.
I’m happy to add a static dump as a fallback if people are okay with this though.
