Version 2.4.9
- Updated internal HTTP requests library to try and mitigate API dump fetch errors
- Added a button to clear cached API dump under Settings → Diagnostics
1 Like
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.
2 Likes
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.
1 Like
Version 2.4.10
- Replaced legacy API dump fetcher and parser with a more robust solution.
- Implemented a static API dump. If Codify fails to fetch the latest API dump from the cache or server, it will fall back to the static dump.
- API dump fetch order: cache → static dump (if up-to-date) → server → static dump
- Fixed React generating a props table when there are no props.
1 Like
I just Codified some UI, and it’s adding “Transparency = 1” to my text labels. It’s making my UI look like this:
I removed the “Transparency = 1” from the Exit Button, so it fixed the issue. Is this a bug?
It might be a hidden property Roblox just added, which Codify defaults to being 1.
ah yep, that’s an old property from ≈2009. I recently changed how Codify works internally to stop errors with fetching the API dump, and I must’ve forgotten to filter it out
I’ll push an update today to fix that!
1 Like
Version 2.4.11
- Framework dropdown now remembers its previous state across sessions—If you collapsed it, it’ll stay collapsed next time you launch Studio.
- Removed hidden properties from Instance property getter (pre-2.4.10 behaviour).
- Minor style and layout changes.
1 Like
is it possible to change the codified to something like this
vide.create(“ScreenGui”)({
});
i prefer having everything written out like that and im pretty sure others too
absolutely. I’ll get that pushed out as an optional feature in the next update
1 Like
Version 2.4.12
- Added option to wrap arguments with parentheses in supported frameworks (Fusion, Vide). This can be enabled from Settings → Generation → Wrap Arguments.
- Added option to show all settings.
- Minor style and layout changes.
2 Likes
Thank you so much, your a lifesaver 
1 Like
is there support to select multiple things?
not currently, but I could add the ability to output multiple snippets based on multiple selections. for react and tsx, we could even have fragments
V3 when?
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ
It’s still a work in progress. Overall, I’m not expecting too many user-facing changes to begin with (mostly UI enhancements), but I am currently prototyping some magical new features to upgrade and improve your workflow.
I’m in the process of refreshing my whole plugin suite, starting with the Resurface plugin, most likely followed by a new plugin that should compliment (and possibly even integrate with) Codify, but more on that one later.
1 Like
Version 2.4.13
- Fixed Rojo generator not filtering out Instance-based properties (e.g. “
BillboardGui.Adornee”, “GuiObject.SelectionImageObject”). - Added button to export snippet directly to a ModuleScript.
1 Like
How did you create the “save to device” feature? I’ve searched everywhere and I can’t find a function that does that.
I see your question was already answered, but for anyone else wondering, Codify temporarily creates a ModuleScript containing the component snippet, selects the newly created ModuleScript and then uses the plugin:PromptSaveSelection method to show the native save dialogue.
2 Likes